Email this issue
Send issue summary in email
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
2 hours
|
|
|
Remaining Estimate:
|
2 hours
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
|
Sometimes, the maximum number of database sessions is reached and user receive an error in session.
This provoke the system does not respond and you need to reboot system.
log:
ERROR - JDBCExceptionReporter.logExceptions(78) | The last packet successfully received from the server was 54,205,656 milliseconds ago. The last packet sent successfully to the server was 54,205,656 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
09:18:31.486 ERROR com.abiquo.util.AbiCloudError - Operation cannot be performed [Error code:ABI-S001 Timestamp:1273130311]. Operation cannot be performed
The maximum number of sessions has been reached..
Error Code: ABI-S001
Error ID: 1273130311.
org.hibernate.exception.JDBCConnectionException: could not execute query
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:74) [hibernate-3.2.5.ga.jar:3.2.5.ga]
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) [hibernate-3.2.5.ga.jar:3.2.5.ga]
at org.hibernate.loader.Loader.doList(Loader.java:2223) [hibernate-3.2.5.ga.jar:3.2.5.ga]
View entire log in attachment.
|
|
Description
|
Sometimes, the maximum number of database sessions is reached and user receive an error in session.
This provoke the system does not respond and you need to reboot system.
log:
ERROR - JDBCExceptionReporter.logExceptions(78) | The last packet successfully received from the server was 54,205,656 milliseconds ago. The last packet sent successfully to the server was 54,205,656 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
09:18:31.486 ERROR com.abiquo.util.AbiCloudError - Operation cannot be performed [Error code:ABI-S001 Timestamp:1273130311]. Operation cannot be performed
The maximum number of sessions has been reached..
Error Code: ABI-S001
Error ID: 1273130311.
org.hibernate.exception.JDBCConnectionException: could not execute query
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:74) [hibernate-3.2.5.ga.jar:3.2.5.ga]
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) [hibernate-3.2.5.ga.jar:3.2.5.ga]
at org.hibernate.loader.Loader.doList(Loader.java:2223) [hibernate-3.2.5.ga.jar:3.2.5.ga]
View entire log in attachment. |
Show » |
Sort Order:
|
Bug
Closed
Minor
Too many connexions to database
WARNING: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
ERROR - JDBCTransaction.begin(67) | JDBC begin failed
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 233,110,727 milliseconds ago. The last packet sent successfully to the server was 233,110,727 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.