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

Wed Aug 11 03:28:49 EDT 2010

    [ https://jira.jboss.org/browse/JBAS-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12544184#action_12544184 ] 

Thomas Saxtoft commented on JBAS-1636:
--------------------------------------

Well I just found that the server reports 4.3.0.GA_CP07_EAP, that's why I thought it was the version number.
Then I downloaded the source code for that version and verified that it has not been fixed.

You have to be aware that the noise in the log, raises questions to our support from our customers. So I still think it would be good to weed out this sort of log statements.

> Don't try to delist a track-connection-by-tx connection that is already broken and has been closed.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-1636
>                 URL: https://jira.jboss.org/browse/JBAS-1636
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1,  JBossAS-4.0.2RC1
>            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: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira