You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2010/01/29 16:54:32 UTC

[jira] Commented: (SM-1930) Upgrade geronimo jars to 2.1.1+

    [ https://issues.apache.org/activemq/browse/SM-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57259#action_57259 ] 

Jean-Baptiste Onofré commented on SM-1930:
------------------------------------------

As geronimo-connector and geronimo-transaction 2.1.x now use slf4j for logging, I need to add slf4j dependency and include it in the distribution assembly.

> Upgrade geronimo jars to 2.1.1+
> -------------------------------
>
>                 Key: SM-1930
>                 URL: https://issues.apache.org/activemq/browse/SM-1930
>             Project: ServiceMix
>          Issue Type: Task
>         Environment: AIX, IBM JDK 1.6
>            Reporter: Hadrian Zbarcea
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 3.4
>
>
> I experienced IllegalStateExceptions in ESB with jca flows with a stack trace lie:
> {code}
> 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]
> {code}
> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.