[JBoss JIRA] (JBTM-622) Support for crash recovery of tx-inflow with multiple resource managers
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-622?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated JBTM-622:
-------------------------------
Assignee: (was: Tom Jenkinson)
> Support for crash recovery of tx-inflow with multiple resource managers
> -----------------------------------------------------------------------
>
> Key: JBTM-622
> URL: https://issues.jboss.org/browse/JBTM-622
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JCA, Recovery, Transaction Core
> Affects Versions: 4.2.3.CP06
> Reporter: Toshiya Kobayashi
> Priority: Minor
>
> JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs.
> In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1414) Facilitate TM record removal by adding record's file name to the warning message
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1414?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1414:
--------------------------------
Assignee: (was: Tom Jenkinson)
> Facilitate TM record removal by adding record's file name to the warning message
> ---------------------------------------------------------------------------------
>
> Key: JBTM-1414
> URL: https://issues.jboss.org/browse/JBTM-1414
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Recovery
> Environment: JBoss EAP 6.x
> Reporter: Tom Ross
>
> When printing warnings about none recoverable transaction manager records in the object store it would help if the warning message included the record's physical file name as well. It would made the manual removal of those records much easier.
> {noformat}
> 15:19:51,003 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord < resource:null, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2c0a0d:-140df526:50d1ddd3:ac883, node_name=1, branch_uid=0:ffff0a2c0a0d:-140df526:50d1ddd3:ac95c, subordinatenodename=null, eis_name=java:jboss/eis/Connection >, heuristic: TwoPhaseOutcome.FINISH_OK, product: ActiveMQ/5.7.0, jndiName: java:jboss/eis/Connection com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@5e124b >
> 15:19:51,008 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016038: No XAResource to recover < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2c0a0d:-140df526:50d1ddd3:ac883, node_name=1, branch_uid=0:ffff0a2c0a0d:-140df526:50d1ddd3:ac95c, subordinatenodename=null, eis_name=java:jboss/eis/Connection >
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months