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:

innodb_lock_wait_timeout=120

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 :(

TIA!
arndale65Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

GaryCommented:
Have you looked at Magmi - may not solve the timeout but it is sure damn faster than using native Magento import.
Ess KayEntrapenuerCommented:
htaccess?
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
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

GaryCommented:
This related issue
https://forums.aws.amazon.com/thread.jspa?threadID=33427

with a 'solution' but not a proper solution

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
MySQL Server

From novice to tech pro — start learning today.