bogus "maximum execution time exceeded" errors?

[sossity]

I am seeing the maximum execution time exceeded message, but it seems to be coming from something in the background. We are moving though screens and the error appears randomly without any noticible hesitation in the app. We have increased the time in the php.ini file from 30 to 600, but it still shows up. I am trying to find out if there is anything tat can spin off in the background and timeout while normal app navigation is occurring.

Any clues?

[mmilano]

perhaps something a global timeout feature such as something in Apache or IIS ?

[sossity]

Well, the interesting thing is that the users are entering data on the client side when these errors show up. It is like the server generated the html , kicked off some background thing, then served the page to the client all as part of one session. I am a bit new at this stuff, so am not sure if this is possible and could result in the errors we are seeing.

[dannys]

You can set the time limit to 0 to disable timeouts - this'll get rid of the error messages, but I would prefer to get rid of the problem (no idea what that could be, unless you've got some slow query running or have some other file/db/network connection open - though PHP should clean all of that up at the end of a script)