ABIQUO

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options
    • Planning Board
    • Task Board
    • Chart Board
    • Released Board
    • Rapid Board
    • Manage Rapid Boards
    • Getting Started
  • Abiquo
  • ABICLOUD-501

Too many connexions to database

  • Rapid Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: abicloud-1.5.0-PR
  • Fix Version/s: Abiquo 1.6.8
  • Component/s: Server
  • Labels:
    None
  • Affect Build:
    2255

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.
  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. File
    number of connections reached log
    06/May/10 9:43 AM
    14 kB
    Valerie Kalusinski

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
Hide
Permalink
Valerie Kalusinski added a comment - 10/May/10 9:27 AM
This problem appears provoking other traces:

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.
Show
Valerie Kalusinski added a comment - 10/May/10 9:27 AM This problem appears provoking other traces: 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.
Hide
Permalink
David Calavera added a comment - 31/May/10 3:01 PM
I've changed the database configuration to keep it saved from abandoned connections. It will also keep logged those connections so we can detect where we had these kind of bottlenecks.
Show
David Calavera added a comment - 31/May/10 3:01 PM I've changed the database configuration to keep it saved from abandoned connections. It will also keep logged those connections so we can detect where we had these kind of bottlenecks.
Hide
Permalink
Ferran Ferri added a comment - 08/Jul/10 5:46 PM
Configuration changed to solve error. Closing
Show
Ferran Ferri added a comment - 08/Jul/10 5:46 PM Configuration changed to solve error. Closing
Hide
Permalink
Valerie Kalusinski added a comment - 16/Jul/10 9:44 AM - edited
Sometimes, the same message is displayed in log but it seems not to avoid any action in application and do not come with an outofmemory.
Reopened on build 3053.
Show
Valerie Kalusinski added a comment - 16/Jul/10 9:44 AM - edited Sometimes, the same message is displayed in log but it seems not to avoid any action in application and do not come with an outofmemory. Reopened on build 3053.
Hide
Permalink
Valerie Kalusinski added a comment - 16/Jul/10 9:44 AM
Modified priority: Critical -> Minor
Show
Valerie Kalusinski added a comment - 16/Jul/10 9:44 AM Modified priority: Critical -> Minor
Hide
Permalink
David Calavera added a comment - 16/Jul/10 10:25 AM
the api connection was not properly configured, I've fixed it.
Show
David Calavera added a comment - 16/Jul/10 10:25 AM the api connection was not properly configured, I've fixed it.
Hide
Permalink
Valerie Kalusinski added a comment - 01/Sep/10 12:20 PM
This issue appears again in release 1.6.5 build 3369
Show
Valerie Kalusinski added a comment - 01/Sep/10 12:20 PM This issue appears again in release 1.6.5 build 3369
Hide
Permalink
Valerie Kalusinski added a comment - 04/Oct/10 12:20 PM
happened too in BPM server in distributed architecture. build 3480.
Show
Valerie Kalusinski added a comment - 04/Oct/10 12:20 PM happened too in BPM server in distributed architecture. build 3480.
Hide
Permalink
David Calavera added a comment - 06/Oct/10 10:38 AM
the bpm service doesn't need a db connection evermore, so this should be fixed.
Show
David Calavera added a comment - 06/Oct/10 10:38 AM the bpm service doesn't need a db connection evermore, so this should be fixed.
Hide
Permalink
Valerie Kalusinski added a comment - 22/Oct/10 3:29 PM
This issue has not appeared already.
closed in 1.6.8 build 3374-2224.
Show
Valerie Kalusinski added a comment - 22/Oct/10 3:29 PM This issue has not appeared already. closed in 1.6.8 build 3374-2224.

People

  • Assignee:
    David Calavera
    Reporter:
    Valerie Kalusinski
Vote (0)
Watch (0)

Dates

  • Created:
    06/May/10 9:43 AM
    Updated:
    22/Oct/10 3:29 PM
    Resolved:
    06/Oct/10 10:38 AM

Time Tracking

Estimated:
2h
Original Estimate - 2 hours
Remaining:
2h
Remaining Estimate - 2 hours
Logged:
Not Specified
Time Spent - Not Specified
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for abiquo. Try JIRA - bug tracking software for your team.