I have an app that loads quite a few records into a mysql table. Then it calls a mysql procedure to take it from there. Somewhere in the midst of all this I get a small box with error 127.0.0.1:8091. Nothing else. If I click it, it goes away and the program proceeds as it should. Is this a time-out of some sort?
Pretty sure that is a lost connection to Server error.
Check your mysql timeout settings.
what do u consider quite a few records?
I’ve received it doing 35K and I’ve received it going over a million. Trying to figure out where I can set this. Don’t see anything in my.ini that would relate. Added connect_timeout=100 to my.ini and will give it a try.
EDITED TO ADD: I think that did it!
1 Like
have you tried it with just a handful toes if it is a volume thing?
It is volume. 5-6K records it flies right though. I think it was a timeout. Running some further tests with that ini change now.
Spoke too soon. With 13K rows it just errored.
There are other timeout settings you should check and increase as well.
Also your Apache settings has timeouts as well.
Will check all. What seems odd is that the program finishes correctly whether I click “ok” or not!
I set every single time out to the max and still get it, but the program still runs.
Here is a screenshot of what I get.
That error, is weird.
Search your code for “error,” and see what comes up… may be a stray piece of code somewhere…
youll have to check your functions pages separately.
I found it. The grid in the dashboard had a refresh interval on it of 10 seconds. It acts like it is reloading, but doesn’t. It gives the error. When I remove the refresh interval the error message goes away. I assumed the refresh would reload the grid but it does not. Any way to reload a grid within a dashboard without an error message?
Have you turned Debug On ?
Oh yeah. I’ve discovered it is not the dashboard. I tried setting up the grid as a separate menu item. Every application is unresponsive while these stored procs are running. I’m looking into some additional indexing now to speed it up, but have to admit I’ve never had this happen in any other interface!