Could you please help me on the below issue?
Event: While doing AP → DB process, there is a process which run SQL for long time, when passing 3600 seconds（60 minutes） then the session was disconnected and an error occurred in Jboss side then after that it became the status which the process was not running normally unless rebooting the instance of Jboss. No issues if it is processing within 3600 seconds.
In the jboss-4.0.5 environment, Normal result is the output to the screen after a lapse of more than 3600 seconds. But In the jboss-5.1 environment, an error will occur when 3600 seconds have elapsed.
Error in Jboss Log:
Attached with this discussion. Please find it.
We are using the below ,
Redhat Linux 5.7
I am thinking that the root cause is the connection error that is occurring at the mysql driver level and there is an external change that is causing the communication link failure and this is not originating from the application server. It is manifesting at the driver level. Please confirm?
Could you please let me know the following,
1) Countermeasure to avoid the session disconnection at 3600 seconds in jboss-5.1 environment?
2) Cause for not performing normally if it takes 3600 seconds in jboss-5.1 environment?
3) Long SQL query(3600 seconds) is processing normally in jboss-4.0.5 environment but not in the jboss-5.1 environment. What could be reason for this issue?
4) How to solve this issue in jboss-5.1 environment? Please let me know if you need more information
Please let me know if you need more information.
Thanks in advance for you suggestions and solutions.