[jbossts-issues] [JBoss JIRA] Assigned: (JBTM-572) WARN message about completed transaction (Could not find new XAResource..)

[Mark Little (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBTM-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Little reassigned JBTM-572:
--------------------------------

    Assignee: Mark Little


> WARN message about completed transaction (Could not find new XAResource..)
> --------------------------------------------------------------------------
>
>                 Key: JBTM-572
>                 URL: https://jira.jboss.org/jira/browse/JBTM-572
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Recovery
>    Affects Versions: 4.2.3.SP5
>         Environment: JBoss SOA-P 4.3.0
>            Reporter: Tomohisa igarashi
>            Assignee: Mark Little
>
> If JBoss node is down when TransactionManager is at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore#remove_state():652( before deleting Tx log after RM's commit is completed ), the following WARN message is output for a long time.
> ----
>   15:03:44,952 WARN  [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa]Could not find new XAResource to use for recovering non-serializable XAResource< 131075, 31, 29, 1--53e1e740:1064:4a40cd21:2460b-53e1e740:1064:4a40cd21:2460c
> ----
> Removing this log automatically might not be the best way when thinking the case where RM lost the ?ransaction. Manual recovering is needed.
> So, JBossTM must have the way of deleting Tx log manually.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira