[JBoss JIRA] (JBTM-1412) testRecoverInflightTransaction failure (and others)
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1412?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1412:
-------------------------------------
That test is only ran during a JTS build.
> testRecoverInflightTransaction failure (and others)
> ---------------------------------------------------
>
> Key: JBTM-1412
> URL: https://issues.jboss.org/browse/JBTM-1412
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M2
> Environment: Raspberry Pi.
> java version "1.7.0_10"
> Java(TM) SE Runtime Environment (build 1.7.0_10-b18)
> Java HotSpot(TM) Client VM (build 23.6-b04, mixed mode)
> Latest "head" from repo.
> Reporter: Mark Little
> Assignee: Tom Jenkinson
>
> At least three failures, but due to the verbosity of the build at this point it is hard for me to say the cause of the other two failures.
> [main] TestResource (1000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >] Flags=0
> [main] TestResource (2000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >] Flags=0
> [main] ProxyXAResource (1000:2000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (1000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >] Flags=67108864
> [main] TestResource (1000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] ProxyXAResource (1000:2000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (2000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >] Flags=67108864
> [main] TestResource (2000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_PREPARED
> [main] TestResource (1000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (2000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_COMMITED
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Tests run: 16, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4,065.677 sec <<< FAILURE!
> Results :
> Failed tests: testRecoverInflightTransaction(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): Servers were not aborted
> testRecovery(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): Servers were not aborted
> testOnePhaseCommit(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): 3
--
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, 3 months
[JBoss JIRA] (JBTM-1414) Facilitate TM record removal by adding record's file name to the warning message
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1414?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1414:
-----------------------------------
Arbitrary removal of files, especially those related to the transaction log and recovery, is not recommended, especially via the OS file system commands, e.g., rm. The transaction tooling available for browsing the object store and manipulating the records directly is meant to be the safer substitute for this in the cases where manual (sys admin) editing of the log data structures is needed.
> 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
> Affects Versions: later
> Environment: JBoss EAP 6.x
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
>
> 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, 3 months
[JBoss JIRA] (JBTM-1414) Facilitate TM record removal by adding record's file name to the warning message
by Tom Ross (JIRA)
[ https://issues.jboss.org/browse/JBTM-1414?page=com.atlassian.jira.plugin.... ]
Tom Ross updated JBTM-1414:
---------------------------
Environment: JBoss EAP 6.x (was: JBOss EAP 6.x)
> 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
> Affects Versions: later
> Environment: JBoss EAP 6.x
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
>
> 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, 3 months
[JBoss JIRA] (JBTM-1414) Facilitate TM record removal by adding record's file name to the warning message
by Tom Ross (JIRA)
[ https://issues.jboss.org/browse/JBTM-1414?page=com.atlassian.jira.plugin.... ]
Tom Ross updated JBTM-1414:
---------------------------
Summary: Facilitate TM record removal by adding record's file name to the warning message (was: Facilitate TM record removal by adding record file name to the warning message )
> 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
> Affects Versions: later
> Environment: JBOss EAP 6.x
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
>
> 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, 3 months
[JBoss JIRA] (JBTM-1414) Facilitate TM record removal by adding record file name to the warning message
by Tom Ross (JIRA)
[ https://issues.jboss.org/browse/JBTM-1414?page=com.atlassian.jira.plugin.... ]
Tom Ross updated JBTM-1414:
---------------------------
Description:
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}
was:
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.
{quote}
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 >
{quote}
> Facilitate TM record removal by adding record 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
> Affects Versions: later
> Environment: JBOss EAP 6.x
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
>
> 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, 3 months
[JBoss JIRA] (JBTM-1414) Facilitate TM record removal by adding record file name to the warning message
by Tom Ross (JIRA)
[ https://issues.jboss.org/browse/JBTM-1414?page=com.atlassian.jira.plugin.... ]
Tom Ross updated JBTM-1414:
---------------------------
Description:
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.
{quote}
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 >
{quote}
was:
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.
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 >
> Facilitate TM record removal by adding record 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
> Affects Versions: later
> Environment: JBOss EAP 6.x
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
>
> 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.
> {quote}
> 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 >
> {quote}
--
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, 3 months
[JBoss JIRA] (JBTM-1414) Facilitate TM record removal by adding record file name to the warning message
by Tom Ross (JIRA)
Tom Ross created JBTM-1414:
------------------------------
Summary: Facilitate TM record removal by adding record 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
Affects Versions: later
Environment: JBOss EAP 6.x
Reporter: Tom Ross
Assignee: Tom Jenkinson
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.
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 >
--
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, 3 months
[JBoss JIRA] (JBTM-1408) TXFramework: XTS Handler not added to HandlerChain
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1408?page=com.atlassian.jira.plugin.... ]
Paul Robinson logged work on JBTM-1408:
---------------------------------------
Author: Paul Robinson
Created on: 04/Jan/13 3:32 AM
Start Date: 04/Jan/13 3:32 AM
Worklog Time Spent: 6 hours
Issue Time Tracking
-------------------
Remaining Estimate: 1 day (was: 1 day, 6 hours)
Time Spent: 1 day (was: 2 hours)
Worklog Id: (was: 12428306)
> TXFramework: XTS Handler not added to HandlerChain
> --------------------------------------------------
>
> Key: JBTM-1408
> URL: https://issues.jboss.org/browse/JBTM-1408
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Affects Versions: 5.0.0.M1
> Reporter: Amos Feng
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 1 day
> Remaining Estimate: 1 day
>
> Tests in error:
> testSimple(org.jboss.narayana.txframework.functional.ATBridgeTest): Could not serialize object: TestResult[status=FAILED,time=1212ms]
> testClientDrivenRollback(org.jboss.narayana.txframework.functional.ATBridgeTest): Could not serialize object: TestResult[status=FAILED,time=331ms]
> testSimple(org.jboss.narayana.txframework.functional.ATTest): Could not serialize object: TestResult[status=FAILED,time=1735ms]
> testMultiInvoke(org.jboss.narayana.txframework.functional.ATTest): Could not serialize object: TestResult[status=FAILED,time=431ms]
> testClientDrivenRollback(org.jboss.narayana.txframework.functional.ATTest)
> testParticipantDrivenRollback(org.jboss.narayana.txframework.functional.ATTest): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.Exception>
> testApplicationException(org.jboss.narayana.txframework.functional.ATTest)
> testSimple(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest): Could not serialize object: TestResult[status=FAILED,time=1050ms]
> testMultiInvoke(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest): Could not serialize object: TestResult[status=FAILED,time=449ms]
> testClientDrivenCancel(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest)
> testApplicationException(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest)
> testCannotComplete(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.Exception>
> testAutoComplete(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest): Could not serialize object: TestResult[status=FAILED,time=2534ms]
> testManualComplete(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest): Could not serialize object: TestResult[status=FAILED,time=501ms]
> testMultiInvoke(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest)
> testClientDrivenCompensate(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest)
> testApplicationException(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest)
> testCannotComplete(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.RuntimeException>
--
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, 3 months
[JBoss JIRA] (JBTM-1408) TXFramework: XTS Handler not added to HandlerChain
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1408?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1408:
--------------------------------
Summary: TXFramework: XTS Handler not added to HandlerChain (was: TXFramework: XTS Handler not added to HandlerChain)
> TXFramework: XTS Handler not added to HandlerChain
> --------------------------------------------------
>
> Key: JBTM-1408
> URL: https://issues.jboss.org/browse/JBTM-1408
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Affects Versions: 5.0.0.M1
> Reporter: Amos Feng
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 2 hours
> Remaining Estimate: 1 day, 6 hours
>
> Tests in error:
> testSimple(org.jboss.narayana.txframework.functional.ATBridgeTest): Could not serialize object: TestResult[status=FAILED,time=1212ms]
> testClientDrivenRollback(org.jboss.narayana.txframework.functional.ATBridgeTest): Could not serialize object: TestResult[status=FAILED,time=331ms]
> testSimple(org.jboss.narayana.txframework.functional.ATTest): Could not serialize object: TestResult[status=FAILED,time=1735ms]
> testMultiInvoke(org.jboss.narayana.txframework.functional.ATTest): Could not serialize object: TestResult[status=FAILED,time=431ms]
> testClientDrivenRollback(org.jboss.narayana.txframework.functional.ATTest)
> testParticipantDrivenRollback(org.jboss.narayana.txframework.functional.ATTest): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.Exception>
> testApplicationException(org.jboss.narayana.txframework.functional.ATTest)
> testSimple(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest): Could not serialize object: TestResult[status=FAILED,time=1050ms]
> testMultiInvoke(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest): Could not serialize object: TestResult[status=FAILED,time=449ms]
> testClientDrivenCancel(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest)
> testApplicationException(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest)
> testCannotComplete(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.Exception>
> testAutoComplete(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest): Could not serialize object: TestResult[status=FAILED,time=2534ms]
> testManualComplete(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest): Could not serialize object: TestResult[status=FAILED,time=501ms]
> testMultiInvoke(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest)
> testClientDrivenCompensate(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest)
> testApplicationException(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest)
> testCannotComplete(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.RuntimeException>
--
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, 3 months
[JBoss JIRA] (JBTM-1408) TXFramework: XTS Handler not added to HandlerChain
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1408?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1408:
--------------------------------
Summary: TXFramework: XTS Handler not added to HandlerChain (was: TXFramework tests error: Could not serialize object)
> TXFramework: XTS Handler not added to HandlerChain
> -------------------------------------------------------
>
> Key: JBTM-1408
> URL: https://issues.jboss.org/browse/JBTM-1408
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Affects Versions: 5.0.0.M1
> Reporter: Amos Feng
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 2 hours
> Remaining Estimate: 1 day, 6 hours
>
> Tests in error:
> testSimple(org.jboss.narayana.txframework.functional.ATBridgeTest): Could not serialize object: TestResult[status=FAILED,time=1212ms]
> testClientDrivenRollback(org.jboss.narayana.txframework.functional.ATBridgeTest): Could not serialize object: TestResult[status=FAILED,time=331ms]
> testSimple(org.jboss.narayana.txframework.functional.ATTest): Could not serialize object: TestResult[status=FAILED,time=1735ms]
> testMultiInvoke(org.jboss.narayana.txframework.functional.ATTest): Could not serialize object: TestResult[status=FAILED,time=431ms]
> testClientDrivenRollback(org.jboss.narayana.txframework.functional.ATTest)
> testParticipantDrivenRollback(org.jboss.narayana.txframework.functional.ATTest): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.Exception>
> testApplicationException(org.jboss.narayana.txframework.functional.ATTest)
> testSimple(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest): Could not serialize object: TestResult[status=FAILED,time=1050ms]
> testMultiInvoke(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest): Could not serialize object: TestResult[status=FAILED,time=449ms]
> testClientDrivenCancel(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest)
> testApplicationException(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest)
> testCannotComplete(org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.Exception>
> testAutoComplete(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest): Could not serialize object: TestResult[status=FAILED,time=2534ms]
> testManualComplete(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest): Could not serialize object: TestResult[status=FAILED,time=501ms]
> testMultiInvoke(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest)
> testClientDrivenCompensate(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest)
> testApplicationException(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest)
> testCannotComplete(org.jboss.narayana.txframework.functional.BAParticipantCompletionTest): Unexpected exception, expected<com.arjuna.wst.TransactionRolledBackException> but was<java.lang.RuntimeException>
--
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, 3 months