Reserved connections are not validated by JBoss EAP

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7
    • 6
    • 5
    • 4

Issue

1

See fault tolerance in EAP 4/5 for older releases

Resolution

  • Application code must handle exceptions that arise while a connection is held (InUse) by the application component
  • Upon completion of connection usage (even if the connection has failed), the application code must explicitly call Content from docs.oracle.com is not included.Connection.close() to return the connection to the pool in order to prevent a connection leak.
  • The application may need to perform other cleanup activity associated with any in-progress work.
    • This may include explicit rollback if using bean managed transactions (BMT) or allowing methods to exit if using CMT since in-flight transactions cannot proceed after a connection failure.
  • The application would need to retry work (if appropriate) after requesting another connection (and potentially starting a new transaction).

Root Cause

Components
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.