scripts are being killed of by litespeed after 60 seconds

Hi!
We have several Magento installations on a cPanel-Server using Cloudlinux and Litespeed. When we want to make a new attribute-set in magento or run a backup, reindex or want to use the api processes are being killed of by litespeed after 60 seconds, but I don't actually think that it is a timeout in litespeed configuration that is doing that, because with apache those are killed of as well, however not after 60 seconds but almost immediately, litespeed only actually allows the process about 60 seconds until it kills it off.
Also this is happening without cagefs enabled on the account as well and with cloudlinux LVE limits bumped up to max for the account. We increased all php-values for timeout dramaticly they are all set far above 60 seconds.

So basically it is quite wide explanation as whenever we try to narrow it down to a certain service by disabling that service we only get wider as even without it, it is getting killed of, and the only difference is the time that it is running (without litespeed maybe 2 seconds, and with litespeed about 60 seconds).

PHP License
This program is free software; you can redistribute it and/or modify
it under the terms of the PHP License as published by the PHP Group
and included in the distribution in the file: LICENSE

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

If you did not receive a copy of the PHP license, or have any
questions about PHP licensing, please contact license@

@NiteWave I just wanted to send the PN but I am told that you account-limit does not allow any more additional PNs you should delete some please let me know where I can send you the PN or an email. Thanks

nnpro has switched back to lsws 4.1.13 but issue still exist -- this has eliminated the possibility which the issue may due to new features from 4.2+

2nd, it's been hard to capture reproduce the issue.
finally, nnpro's observation is php script running over 60 seconds will cause trouble; within 60 seconds looks fine. so he created a simple scripts which last 70 seconds to let me test:

here's my test results:
1)in my chrome, 100% fail!
No data received
Unable to load the webpage because the server sent no data.
Here are some suggestions:
Reload this webpage later.
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.

google above error message, too many too many results and can't find out a close one.

if 30 seconds, that's ok, chrome see the result returned by php correctly.

2)in firefox, most time it succeeded, some time it failed.

3)strace the backend php process, not killed, completed normally

4)asked nnpro to put time.php under a https://, he said it succeeded in chrome. then he tried to http:// again. guess what ? succeeded as well!

so far the observation is:
it looks dangerous for a http request which will be idle over 60 seconds.
either the client(especially chrome) or the server may think(wrongly) the connection has been closed by the peer, but actually not, due to unstable network status by various unknown reasons.
in contrast, https is more stable and reliable.

not sure any web server have been aware of such issue and give any workaround or solution. so in user's experience, the web server is much stable and predictable.

in application's standpoint, any action is known to take long time, need display a "progress bar" alike to user. otherwise, user may have bad experience to the application.