[JBoss JIRA] (JBTM-1717) Compensations API tests hit by ParticipantCompletion Race condition
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1717?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1717:
--------------------------------
Description:
This issue is documented here: JBTM-1429
This issue is to fix the tests so they tollerate this issue. This can be solved easily using Byteman, in the same way as we solve it for other tests.
In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. See JBTM-1718 for the real fix to this issue.
was:
This issue is documented here: JBTM-1429
This issue is to fix the tests so they tollerate this issue. This can be solved easily using Byteman, in the same way as we solve it for other tests.
In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. See here for the real fix to this issue.
> Compensations API tests hit by ParticipantCompletion Race condition
> -------------------------------------------------------------------
>
> Key: JBTM-1717
> URL: https://issues.jboss.org/browse/JBTM-1717
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
>
> This issue is documented here: JBTM-1429
> This issue is to fix the tests so they tollerate this issue. This can be solved easily using Byteman, in the same way as we solve it for other tests.
> In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. See JBTM-1718 for the real fix to this issue.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1717) Compensations API tests hit by ParticipantCompletion Race condition
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1717:
-----------------------------------
Summary: Compensations API tests hit by ParticipantCompletion Race condition
Key: JBTM-1717
URL: https://issues.jboss.org/browse/JBTM-1717
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: TXFramework
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M3
This issue is documented here: JBTM-1429
This issue is to fix the tests so they tollerate this issue. This can be solved easily using Byteman, in the same way as we solve it for other tests.
In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. See here for the real fix to this issue.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1147) Refactor ParticipantCompletion recovery tests to remove duplicate rules
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/JBTM-1147?page=com.atlassian.jira.plugin.... ]
Work on JBTM-1147 stopped by Ondřej Chaloupka.
> Refactor ParticipantCompletion recovery tests to remove duplicate rules
> -----------------------------------------------------------------------
>
> Key: JBTM-1147
> URL: https://issues.jboss.org/browse/JBTM-1147
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Affects Versions: 4.16.4, 5.0.0.M1
> Reporter: Paul Robinson
> Assignee: Ondřej Chaloupka
> Priority: Minor
> Fix For: 5.0.0.M4
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> The Byteman rules for the participant completion XTS recovery tests have many rules that are almost duplicates of each other. For example:
> The following rules in BACrashDuringCommit could be refactored into a single rule
> {code}
> #####################################################################
> # Setup counter MultiParticipantParticipantCompletionParticipantCloseTest
> #
> RULE setup counter MultiParticipantParticipantCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseTest
> METHOD run()
> AT ENTRY
> IF TRUE
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> #####################################################################
> # Setup counter MultiParticipantCoordinatorCompletionParticipantCloseTest
> #
> RULE setup counter MultiParticipantCoordinatorCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseAndExitTest
> METHOD run()
> AT ENTRY
> IF TRUE
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> #####################################################################
> # Setup counter MultiServiceParticipantCompletionParticipantCloseTest
> #
> RULE setup counter MultiServiceParticipantCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseTest
> METHOD run()
> AT ENTRY
> IF TRUE
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> #####################################################################
> # Setup counter MultiServiceParticipantCompletionParticipantCloseAndExitTest
> #
> RULE setup counter MultiServiceParticipantCompletionParticipantCloseAndExitTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseAndExitTest
> METHOD run()
> AT ENTRY
> IF TRUE
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> {code}
> These can be re-factored in to a rule like this:
> {code}
> RULE setup counter
> INTERFACE org.jboss.jbossts.xts.servicetests.test.XTSServiceTest
> METHOD run()
> AT ENTRY
> IF $0.getClass().getName().contains("ParticipantCompletionParticipant")
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> {code}
> This assumes that we have the same numbers for each use of:
> {code}
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> {code}
> Which is *usually* the case:
> {code}
> grep -r createCounter\(\"closes\" .
> ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BACrashDuringOnePhaseCommit.txt: createCounter("closes", 1),
> ./src/test/resources/scripts/BASubordinateCrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BASubordinateCrashDuringComplete.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringOnePhaseCommit.txt: createCounter("closes", 1),
> ./target/test-classes/scripts/BASubordinateCrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BASubordinateCrashDuringComplete.txt: createCounter("closes", 3),
> {code}
> Maybe we just override the rule for the one exception. Ideas for what to do here are to be investigated.
> Also, the following similar rules are also present in this file:
> {code}
> #####################################################################
> # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseTest
> #
> RULE wait for closes MultiParticipantParticipantCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF TRUE
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> #####################################################################
> # Wait on Rendezvous before calling uba.close() on MultiParticipantParticipantCompletionParticipantCloseAndExitTest
> #
> RULE wait for closes MultiParticipantParticipantCompletionParticipantCloseAndExitTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseAndExitTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF TRUE
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> #####################################################################
> # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseTest
> #
> RULE wait for closes MultiServiceParticipantCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF TRUE
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> #####################################################################
> # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseAndExitTest
> #
> RULE wait for closes MultiServiceParticipantCompletionParticipantCloseAndExitTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseAndExitTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF TRUE
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> {code}
> Which could be replaced with something like this:
> {code}
> RULE wait for closes
> INTERFACE org.jboss.jbossts.xts.servicetests.test.XTSServiceTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF $0.getClass().getName().contains("ParticipantCompletionParticipant")
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> {code}
> We could also re-factor these two rules out into a separate Byteman script and add it to all tests that need it.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1563) TestTransactions::test_recovery (F) line: 520 /home/hudson/workspace/blacktie-linux64/tx/src/test/cpp/TestTransactions.cxx
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1563?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1563:
---------------------------------
I created http://172.17.131.2/view/Narayana+BlacktTie-JBTM/job/blacktie-JBTM1563/ to test this issue.
> TestTransactions::test_recovery (F) line: 520 /home/hudson/workspace/blacktie-linux64/tx/src/test/cpp/TestTransactions.cxx
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1563
> URL: https://issues.jboss.org/browse/JBTM-1563
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie, Testing
> Affects Versions: 5.0.0.M1
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.Final
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1423/...
> {noformat}
> [exec] 2013-01-20 03:10:13,131 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed
> [exec] 2013-01-20 03:10:13,133 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records
> [exec] 2013-01-20 03:10:13,139 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,141 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,143 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,146 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,148 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,149 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 139 seconds
> [exec] 2013-01-20 03:10:23,150 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 129 seconds
> [exec] 2013-01-20 03:10:33,152 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 119 seconds
> [exec] 2013-01-20 03:10:43,153 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 109 seconds
> [exec] 2013-01-20 03:10:53,155 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 99 seconds
> [exec] 2013-01-20 03:11:03,156 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 89 seconds
> [exec] 2013-01-20 03:11:13,158 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 79 seconds
> [exec] 2013-01-20 03:11:23,160 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 69 seconds
> [exec] 2013-01-20 03:11:33,161 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 59 seconds
> [exec] 2013-01-20 03:11:43,163 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 49 seconds
> [exec] 2013-01-20 03:11:53,164 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 39 seconds
> [exec] 2013-01-20 03:12:03,166 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 29 seconds
> [exec] 2013-01-20 03:12:13,167 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 19 seconds
> [exec] 2013-01-20 03:12:23,169 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 9 seconds
> [exec] 2013-01-20 03:12:33,172 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery
> [exec] F2013-01-20 03:12:33,174 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec] 2013-01-20 03:12:33,174 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec] 2013-01-20 03:12:33,174 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec] 2013-01-20 03:12:33,175 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec] 2013-01-20 03:12:33,176 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec]
> [exec]
> [exec]
> [exec] !!!FAILURES!!!
> [exec] Test Results:
> [exec] Run: 13 Failures: 1 Errors: 0
> [exec]
> [exec]
> [exec] 1) test: TestTransactions::test_recovery (F) line: 520 /home/hudson/workspace/blacktie-linux64/tx/src/test/cpp/TestTransactions.cxx
> [exec] assertion failed
> [exec] - Expression: _w12pq_u
> [exec]
> {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
10 years, 11 months
[JBoss JIRA] (JBTM-1563) TestTransactions::test_recovery (F) line: 520 /home/hudson/workspace/blacktie-linux64/tx/src/test/cpp/TestTransactions.cxx
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1563?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-1563:
----------------------------
Description:
http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1423/...
{noformat}
[exec] 2013-01-20 03:10:13,131 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed
[exec] 2013-01-20 03:10:13,133 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records
[exec] 2013-01-20 03:10:13,139 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
[exec] 2013-01-20 03:10:13,141 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
[exec] 2013-01-20 03:10:13,143 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
[exec] 2013-01-20 03:10:13,146 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
[exec] 2013-01-20 03:10:13,148 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
[exec] 2013-01-20 03:10:13,149 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 139 seconds
[exec] 2013-01-20 03:10:23,150 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 129 seconds
[exec] 2013-01-20 03:10:33,152 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 119 seconds
[exec] 2013-01-20 03:10:43,153 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 109 seconds
[exec] 2013-01-20 03:10:53,155 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 99 seconds
[exec] 2013-01-20 03:11:03,156 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 89 seconds
[exec] 2013-01-20 03:11:13,158 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 79 seconds
[exec] 2013-01-20 03:11:23,160 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 69 seconds
[exec] 2013-01-20 03:11:33,161 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 59 seconds
[exec] 2013-01-20 03:11:43,163 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 49 seconds
[exec] 2013-01-20 03:11:53,164 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 39 seconds
[exec] 2013-01-20 03:12:03,166 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 29 seconds
[exec] 2013-01-20 03:12:13,167 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 19 seconds
[exec] 2013-01-20 03:12:23,169 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 9 seconds
[exec] 2013-01-20 03:12:33,172 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery
[exec] F2013-01-20 03:12:33,174 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
[exec] 2013-01-20 03:12:33,174 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
[exec] 2013-01-20 03:12:33,174 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
[exec] 2013-01-20 03:12:33,175 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
[exec] 2013-01-20 03:12:33,176 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
[exec]
[exec]
[exec]
[exec] !!!FAILURES!!!
[exec] Test Results:
[exec] Run: 13 Failures: 1 Errors: 0
[exec]
[exec]
[exec] 1) test: TestTransactions::test_recovery (F) line: 520 /home/hudson/workspace/blacktie-linux64/tx/src/test/cpp/TestTransactions.cxx
[exec] assertion failed
[exec] - Expression: _w12pq_u
[exec]
{noformat}
was:http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1423/console
> TestTransactions::test_recovery (F) line: 520 /home/hudson/workspace/blacktie-linux64/tx/src/test/cpp/TestTransactions.cxx
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1563
> URL: https://issues.jboss.org/browse/JBTM-1563
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie, Testing
> Affects Versions: 5.0.0.M1
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.Final
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1423/...
> {noformat}
> [exec] 2013-01-20 03:10:13,131 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_recovery passed
> [exec] 2013-01-20 03:10:13,133 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery begin 1 records
> [exec] 2013-01-20 03:10:13,139 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,141 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,143 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,146 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,148 [0x7f5ce0ace760] INFO (XAResourceManager :320 ) - Recovery: replaying transaction (TM reports prepared/preparing or completing)
> [exec] 2013-01-20 03:10:13,149 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 139 seconds
> [exec] 2013-01-20 03:10:23,150 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 129 seconds
> [exec] 2013-01-20 03:10:33,152 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 119 seconds
> [exec] 2013-01-20 03:10:43,153 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 109 seconds
> [exec] 2013-01-20 03:10:53,155 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 99 seconds
> [exec] 2013-01-20 03:11:03,156 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 89 seconds
> [exec] 2013-01-20 03:11:13,158 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 79 seconds
> [exec] 2013-01-20 03:11:23,160 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 69 seconds
> [exec] 2013-01-20 03:11:33,161 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 59 seconds
> [exec] 2013-01-20 03:11:43,163 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 49 seconds
> [exec] 2013-01-20 03:11:53,164 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 39 seconds
> [exec] 2013-01-20 03:12:03,166 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 29 seconds
> [exec] 2013-01-20 03:12:13,167 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 19 seconds
> [exec] 2013-01-20 03:12:23,169 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery sleeping for not more than 9 seconds
> [exec] 2013-01-20 03:12:33,172 [0x7f5ce0ace760] INFO (AtmiBrokerLogc :66 ) - TestTransactions::test_run_recovery 1 recs after recovery
> [exec] F2013-01-20 03:12:33,174 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec] 2013-01-20 03:12:33,174 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec] 2013-01-20 03:12:33,174 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec] 2013-01-20 03:12:33,175 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec] 2013-01-20 03:12:33,176 [0x7f5ce0ace760] WARN (XAResourceManager :125 ) - There are still incomplete branches
> [exec]
> [exec]
> [exec]
> [exec] !!!FAILURES!!!
> [exec] Test Results:
> [exec] Run: 13 Failures: 1 Errors: 0
> [exec]
> [exec]
> [exec] 1) test: TestTransactions::test_recovery (F) line: 520 /home/hudson/workspace/blacktie-linux64/tx/src/test/cpp/TestTransactions.cxx
> [exec] assertion failed
> [exec] - Expression: _w12pq_u
> [exec]
> {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
10 years, 11 months
[JBoss JIRA] (JBTM-1147) Refactor ParticipantCompletion recovery tests to remove duplicate rules
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1147?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1147:
--------------------------------
Fix Version/s: 5.0.0.M4
(was: 5.0.0.M3)
> Refactor ParticipantCompletion recovery tests to remove duplicate rules
> -----------------------------------------------------------------------
>
> Key: JBTM-1147
> URL: https://issues.jboss.org/browse/JBTM-1147
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Affects Versions: 4.16.4, 5.0.0.M1
> Reporter: Paul Robinson
> Assignee: Ondřej Chaloupka
> Priority: Minor
> Fix For: 5.0.0.M4
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> The Byteman rules for the participant completion XTS recovery tests have many rules that are almost duplicates of each other. For example:
> The following rules in BACrashDuringCommit could be refactored into a single rule
> {code}
> #####################################################################
> # Setup counter MultiParticipantParticipantCompletionParticipantCloseTest
> #
> RULE setup counter MultiParticipantParticipantCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseTest
> METHOD run()
> AT ENTRY
> IF TRUE
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> #####################################################################
> # Setup counter MultiParticipantCoordinatorCompletionParticipantCloseTest
> #
> RULE setup counter MultiParticipantCoordinatorCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseAndExitTest
> METHOD run()
> AT ENTRY
> IF TRUE
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> #####################################################################
> # Setup counter MultiServiceParticipantCompletionParticipantCloseTest
> #
> RULE setup counter MultiServiceParticipantCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseTest
> METHOD run()
> AT ENTRY
> IF TRUE
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> #####################################################################
> # Setup counter MultiServiceParticipantCompletionParticipantCloseAndExitTest
> #
> RULE setup counter MultiServiceParticipantCompletionParticipantCloseAndExitTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseAndExitTest
> METHOD run()
> AT ENTRY
> IF TRUE
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> {code}
> These can be re-factored in to a rule like this:
> {code}
> RULE setup counter
> INTERFACE org.jboss.jbossts.xts.servicetests.test.XTSServiceTest
> METHOD run()
> AT ENTRY
> IF $0.getClass().getName().contains("ParticipantCompletionParticipant")
> DO debug("creating counter and rendezvous"),
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> ENDRULE
> {code}
> This assumes that we have the same numbers for each use of:
> {code}
> createCounter("closes", 3),
> createRendezvous("closes-complete", 2)
> {code}
> Which is *usually* the case:
> {code}
> grep -r createCounter\(\"closes\" .
> ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BACrashDuringOnePhaseCommit.txt: createCounter("closes", 1),
> ./src/test/resources/scripts/BASubordinateCrashDuringCommit.txt: createCounter("closes", 3),
> ./src/test/resources/scripts/BASubordinateCrashDuringComplete.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BACrashDuringOnePhaseCommit.txt: createCounter("closes", 1),
> ./target/test-classes/scripts/BASubordinateCrashDuringCommit.txt: createCounter("closes", 3),
> ./target/test-classes/scripts/BASubordinateCrashDuringComplete.txt: createCounter("closes", 3),
> {code}
> Maybe we just override the rule for the one exception. Ideas for what to do here are to be investigated.
> Also, the following similar rules are also present in this file:
> {code}
> #####################################################################
> # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseTest
> #
> RULE wait for closes MultiParticipantParticipantCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF TRUE
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> #####################################################################
> # Wait on Rendezvous before calling uba.close() on MultiParticipantParticipantCompletionParticipantCloseAndExitTest
> #
> RULE wait for closes MultiParticipantParticipantCompletionParticipantCloseAndExitTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseAndExitTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF TRUE
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> #####################################################################
> # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseTest
> #
> RULE wait for closes MultiServiceParticipantCompletionParticipantCloseTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF TRUE
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> #####################################################################
> # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseAndExitTest
> #
> RULE wait for closes MultiServiceParticipantCompletionParticipantCloseAndExitTest
> CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseAndExitTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF TRUE
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> {code}
> Which could be replaced with something like this:
> {code}
> RULE wait for closes
> INTERFACE org.jboss.jbossts.xts.servicetests.test.XTSServiceTest
> METHOD run()
> AT CALL UserBusinessActivity.close()
> IF $0.getClass().getName().contains("ParticipantCompletionParticipant")
> DO debug("waiting to call close"),
> rendezvous("closes-complete"),
> debug("rendezvous complete, calling close")
> ENDRULE
> {code}
> We could also re-factor these two rules out into a separate Byteman script and add it to all tests that need it.
--
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
10 years, 11 months
[JBoss JIRA] (JBTM-1715) NPE when using CompensationManager within an in-flowed WS-BA transaction
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1715?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1715:
--------------------------------
Fix Version/s: 5.0.0.M4
(was: 5.0.0.M3)
> NPE when using CompensationManager within an in-flowed WS-BA transaction
> ------------------------------------------------------------------------
>
> Key: JBTM-1715
> URL: https://issues.jboss.org/browse/JBTM-1715
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M4
>
>
> The following error occurs if an injected CompensationManager is invoked within the scope of a compensation-based transaction that was in-flowed via a WS-BA transaction.
> {quote}
> 16:17:09,879 ERROR [org.jboss.as.ejb3.invocation] (default task-18) JBAS014134: EJB Invocation failed on component TestServiceService for method public void org.jboss.narayana.compensations.functiona[617/9100]
> ted.TestServiceService.saveDataCancelOnFailure(java.lang.Boolean): javax.ejb.EJBException: java.lang.NullPointerException
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:251) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:215) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPS
> HOT]
> {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
10 years, 11 months