So we have a script(s) that runs in succession. Randomly this task would halt/freeze and error out simply because it did not see a returned response from the MySQL server saying the statement ran fine breaking the entire procedure. However when manually checking against the DB, the statements all ran fine it's just the script (using JBDC) aborted since it didn't see a response.
Nothing in the error logs, etc.
Is there a setting or reason why MySQL would be doing this? This is version 5.1 .
I thought of network issues causing this but this seems to happen in 2 different environments, both through a WAN and local LAN .