Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
AIX, IBM JDK 1.6
Description
I experienced IllegalStateExceptions in ESB with jca flows with a stack trace lie:
1 Jan 2010 13:55:26,537 | WARN | pool-flow.jca.org.apache.servicemix.jca.{http://servicemix.apache.org/sample}SampleJMSService:SampleServiceImplPort-thread-31 | Transaction | action.manager.TransactionImpl 536 | Unexpected exception from afterCompletion; continuing
java.lang.IllegalStateException: deque is full: contents:
[org.apache.geronimo.connector.outbound.ManagedConnectionInfo@7bd67bd6,
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@296b296b,
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@3c883c88,
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@5f865f86,
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@64866486,
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@59e259e2,
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@65ae65ae,
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@4fc24fc2,
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@1e0c1e0c,
org.apache.geronimo.connector.outbound.ManagedConnectionInfo@1e3e1e3e]
The only reference I found to this issue is at:
http://old.nabble.com/Getting-%22Deque-Full%22-error-on-Connection.close()-td18723438s134.html
The recommendation was to upgrading the following two geronimo jars to at least ver 2.1.1. They actually upgraded to the latest on that branch and it solved their problem. I am not sure if upgrading to 2.2 is a better option.
http://repo1.maven.org/maven2/org/apache/geronimo/components/geronimo-connector/2.1.3/geronimo-connector-2.1.3.jar
http://repo1.maven.org/maven2/org/apache/geronimo/components/geronimo-transaction/2.1.3/geronimo-transaction-2.1.3.jar