Magento and Amazon RDS - timeouts

I have a Magento CE 1.7 installation on an Amazon EC2 instance with the Magento database on an Amazon RDS Large database instance. Generally things seems to be configured ok.

However, when performing bulk import operations I am hitting some sort of 120 second failure. I kick off the import process and exactly 120 seconds in Chrome tells me:

Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data

Open in new window

Sure enough the import has failed.

I have tried the often given advice of the php.ini settings:
memory_limit = 256M

max_execution_time = 1800

Open in new window

But they don't fix it. I have tuned a number of RDS Parameter Group settings as well:


Open in new window

for example - but again no success.

It is clear that there is some hard-coded 120 second limit somewhere (i've timed it many times!) but i cannot work out what parameter is causing the issue.

I have tried cutting up the import file into small sections and it runs just fine when i do that. So its not input data related either

Any help much appreciated - have pushed 2 days into this issue already :(

Who is Participating?
This related issue

with a 'solution' but not a proper solution
Have you looked at Magmi - may not solve the timeout but it is sure damn faster than using native Magento import.
Ess KayEntrapenuerCommented:
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

arndale65Author Commented:
GaryC123 -
I have tried an alternative to Magmi (another bulk import module) and that also hits to 120 second limit - thanks for the suggestion though

esskayb2d -
Yes i have tried the htaccess and php.ini for the parameters i mention in the post - same result - but thanks for the suggestion
Ess KayEntrapenuerCommented:
try switching the php version
arndale65Author Commented:
Yes the issue was around the related issue. Work around i have put in place is for back end access (i.e. for large batch jobs of any flavour) to be on a separate, directly addressable via  EIP sub-domain. Thanks a million for the pointer.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.