[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1636) Don't try to delist a track-connection-by-tx connection that is already broken and has been closed.

[Adrian B. (JIRA) <jir...@jb...>]

     [ http://jira.jboss.com/jira/browse/JBAS-1636?page=history ]
     
Adrian Brock closed JBAS-1636:
------------------------------

    Resolution: Done

Fixed. Also added a warning log of all connectionErrorOccurred events
seen by the ConnectionManager(s).

> Don't try to delist a track-connection-by-tx connection that is already broken and has been closed.
> ---------------------------------------------------------------------------------------------------
>
>          Key: JBAS-1636
>          URL: http://jira.jboss.com/jira/browse/JBAS-1636
>      Project: JBoss Application Server
>         Type: Bug
>     Versions:  JBossAS-4.0.2RC1,  JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final
>     Reporter: Adrian Brock
>     Assignee: Adrian Brock
>      Fix For: JBossAS-4.0.2 Final

>
>
> The transaction synchronization that returns track-connection-by-tx
> should not try to process connections that are broken and have already been
> closed.
> This leads to a spurious error message:
> org.jboss.resource.connectionmanager.TxConnectionManager - The re is something wrong with the pooling?
> java.lang.IllegalStateException: afterCompletion called with wrong tx!
> Expected: null, actual: TransactionImpl:XidImpl [...]
> at
> org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventLi
> stener$TxRemover.afterCompletion(TxConnectio
> nManager.java:588)
> The error message does not cause problems but it can be noisy/disconcerting in the logs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira