[JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2554.
-------------------------------
> CrashRecovery05_2 failures on JacORB
> ------------------------------------
>
> Key: JBTM-2554
> URL: https://issues.jboss.org/browse/JBTM-2554
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Reporter: Gytis Trikleris
> Assignee: Michael Musgrove
> Fix For: 5.2.8.Final
>
>
> crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s)
> crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s)
> crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s)
> crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s)
> crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s)
> crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s)
> crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s)
> crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBTM-2549) CrashRecovery05_2_Test002 failure
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2549?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2549.
-------------------------------
> CrashRecovery05_2_Test002 failure
> ---------------------------------
>
> Key: JBTM-2549
> URL: https://issues.jboss.org/browse/JBTM-2549
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Affects Versions: 5.2.7.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.2.8.Final
>
>
> There are a number of failures in the CrashRecovery05_1 and CrashRecovery05_2 test groups with a similar root cause:
> Tests that use AfterCrashServiceImpl01#check_oper and AfterCrashServiceImpl02#check_oper with JdkORB fail because they make invalid assumptions about the return value of RecoveryCoordinator#replay_completion. The OTS spec says "This (replay_completion) non-blocking operation returns the current status of the transaction" but the check_oper() test assumes that the return value represents the transaction status after all resources have been replayed and therefore returns the wrong result to the requesting client. The fix is to ask the resources for their status after the replay_completion attempt (but also waiting for the resource to have been replayed). I tested the hypothesis by forcing a 200ms wait after issuing replay_completion on the RecoveryCoordinator object (but I will use a rendezvous for the actual fix).
> There is a second problem with the way these tests are coded since they ignore the fact that replay_completion reruns phase 2 on all resources whereas the test relies on it being done on only the requested resource). A test sequence is as follows:
> # client starts a transaction
> # asks service1 to create a resource1
> # asks service2 to create a resource2
> # client commits the transaction (one of which crashes during 2PC)
> # restart the server (hosting the services)
> # client asks service1 for the status of the first resource
> # service1 invokes replay_completion on the RecoveryCoordinator for resource1
> # this causes a recovery attempt on both resources
> # client asks service2 for the status of the second resource
> # service2 invokes replay_completion on the RecoveryCoordinator for resource2
> # but this will fail because the transaction was completed during steps 7 and 8 so the
> # transaction log no longer exists and the recovery attempt calls rollback on resource2
> The fix is to store the transaction Status with the resources and have the service ask the resources for the state (rather than the return value of the replay_completion request).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBTM-2534) HQStore crashrec failures on QA_JTS_JDKORB
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2534?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2534.
-------------------------------
> HQStore crashrec failures on QA_JTS_JDKORB
> ------------------------------------------
>
> Key: JBTM-2534
> URL: https://issues.jboss.org/browse/JBTM-2534
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Michael Musgrove
> Priority: Critical
> Fix For: 5.2.8.Final
>
>
> Killed this one: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/...
> Normally run to completion but lots of crash rec failures:
> {quote}
> Total time: 525 minutes 19 seconds
> Test Failures:
> crashrecovery02_2 CrashRecovery02_2_Test01 Fail (0m50.031s)
> crashrecovery02_2 CrashRecovery02_2_Test06 Fail (0m43.914s)
> crashrecovery02_2 CrashRecovery02_2_Test07 Fail (0m48.270s)
> crashrecovery02_2 CrashRecovery02_2_Test08 Fail (0m48.340s)
> crashrecovery02_2 CrashRecovery02_2_Test09 Fail (0m48.014s)
> crashrecovery02_2 CrashRecovery02_2_Test10 Fail (0m47.865s)
> crashrecovery02_2 CrashRecovery02_2_Test11 Fail (0m48.756s)
> crashrecovery02_2 CrashRecovery02_2_Test12 Fail (0m47.992s)
> crashrecovery02_2 CrashRecovery02_2_Test13 Fail (0m47.840s)
> crashrecovery02_2 CrashRecovery02_2_Test14 Fail (0m47.948s)
> crashrecovery02_2 CrashRecovery02_2_Test15 Fail (0m47.742s)
> crashrecovery02_2 CrashRecovery02_2_Test16 Fail (0m48.953s)
> crashrecovery02_2 CrashRecovery02_2_Test02 Fail (0m48.202s)
> crashrecovery02_2 CrashRecovery02_2_Test03 Fail (2m3.776s)
> crashrecovery02_2 CrashRecovery02_2_Test04 Fail (0m47.686s)
> crashrecovery02_2 CrashRecovery02_2_Test05 Fail (0m47.859s)
> crashrecovery02_2 CrashRecovery02_2_Test17 Fail (0m48.029s)
> crashrecovery02_2 CrashRecovery02_2_Test18 Fail (0m47.658s)
> crashrecovery02_2 CrashRecovery02_2_Test19 Fail (0m47.775s)
> crashrecovery02_2 CrashRecovery02_2_Test20 Fail (0m48.086s)
> crashrecovery02_2 CrashRecovery02_2_Test21 Fail (0m47.979s)
> crashrecovery02_2 CrashRecovery02_2_Test22 Fail (0m48.137s)
> crashrecovery02_2 CrashRecovery02_2_Test23 Fail (0m48.267s)
> crashrecovery02_2 CrashRecovery02_2_Test24 Fail (0m48.100s)
> crashrecovery02_2 CrashRecovery02_2_Test25 Fail (0m47.787s)
> crashrecovery05_1 CrashRecovery05_1_Test01 Fail (1m17.781s)
> crashrecovery05_1 CrashRecovery05_1_Test10 Fail (1m18.510s)
> crashrecovery05_1 CrashRecovery05_1_Test06 Fail (1m17.647s)
> crashrecovery05_1 CrashRecovery05_1_Test07 Fail (1m17.572s)
> crashrecovery05_1 CrashRecovery05_1_Test08 Fail (1m17.365s)
> crashrecovery05_1 CrashRecovery05_1_Test09 Fail (1m17.263s)
> crashrecovery05_2 CrashRecovery05_2_Test051 Fail (2m3.491s)
> crashrecovery05_2 CrashRecovery05_2_Test052 Fail (0m48.481s)
> crashrecovery05_2 CrashRecovery05_2_Test053 Fail (2m3.698s)
> crashrecovery05_2 CrashRecovery05_2_Test054 Fail (0m47.293s)
> crashrecovery05_2 CrashRecovery05_2_Test055 Fail (0m48.382s)
> crashrecovery05_2 CrashRecovery05_2_Test056 Fail (0m43.458s)
> crashrecovery05_2 CrashRecovery05_2_Test057 Fail (0m49.076s)
> crashrecovery05_2 CrashRecovery05_2_Test058 Fail (0m43.988s)
> crashrecovery05_2 CrashRecovery05_2_Test059 Fail (0m48.177s)
> crashrecovery05_2 CrashRecovery05_2_Test060 Fail (0m47.995s)
> crashrecovery05_2 CrashRecovery05_2_Test061 Fail (0m48.266s)
> crashrecovery05_2 CrashRecovery05_2_Test062 Fail (0m47.852s)
> crashrecovery05_2 CrashRecovery05_2_Test063 Fail (2m3.059s)
> crashrecovery05_2 CrashRecovery05_2_Test064 Fail (0m47.332s)
> crashrecovery05_2 CrashRecovery05_2_Test065 Fail (0m47.226s)
> crashrecovery05_2 CrashRecovery05_2_Test066 Fail (0m47.141s)
> crashrecovery05_2 CrashRecovery05_2_Test067 Fail (0m47.195s)
> crashrecovery05_2 CrashRecovery05_2_Test068 Fail (0m47.464s)
> crashrecovery05_2 CrashRecovery05_2_Test069 Fail (0m49.360s)
> crashrecovery05_2 CrashRecovery05_2_Test070 Fail (0m47.700s)
> crashrecovery05_2 CrashRecovery05_2_Test071 Fail (0m47.782s)
> crashrecovery05_2 CrashRecovery05_2_Test072 Fail (0m47.736s)
> crashrecovery05_2 CrashRecovery05_2_Test073 Fail (0m47.438s)
> crashrecovery05_2 CrashRecovery05_2_Test074 Fail (0m47.701s)
> crashrecovery05_2 CrashRecovery05_2_Test075 Fail (0m47.385s)
> crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m10.036s)
> crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m54.372s)
> crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m10.928s)
> crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m55.124s)
> crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m54.970s)
> crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m50.656s)
> crashrecovery05_2 CrashRecovery05_2_Test082 Fail (0m54.356s)
> crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m50.052s)
> crashrecovery05_2 CrashRecovery05_2_Test084 Fail (0m53.605s)
> crashrecovery05_2 CrashRecovery05_2_Test085 Fail (0m54.694s)
> crashrecovery05_2 CrashRecovery05_2_Test086 Fail (0m54.147s)
> crashrecovery05_2 CrashRecovery05_2_Test087 Fail (0m54.397s)
> crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m11.261s)
> crashrecovery05_2 CrashRecovery05_2_Test089 Fail (0m54.332s)
> crashrecovery05_2 CrashRecovery05_2_Test090 Fail (0m55.264s)
> crashrecovery05_2 CrashRecovery05_2_Test091 Fail (0m54.471s)
> crashrecovery05_2 CrashRecovery05_2_Test092 Fail (0m54.046s)
> crashrecovery05_2 CrashRecovery05_2_Test093 Fail (0m54.249s)
> crashrecovery05_2 CrashRecovery05_2_Test094 Fail (0m54.388s)
> crashrecovery05_2 CrashRecovery05_2_Test095 Fail (0m53.763s)
> crashrecovery05_2 CrashRecovery05_2_Test096 Fail (0m54.313s)
> crashrecovery05_2 CrashRecovery05_2_Test097 Fail (0m54.069s)
> crashrecovery05_2 CrashRecovery05_2_Test098 Fail (0m54.290s)
> crashrecovery05_2 CrashRecovery05_2_Test099 Fail (0m55.164s)
> crashrecovery05_2 CrashRecovery05_2_Test100 Fail (0m54.189s)
> crashrecovery05_2 CrashRecovery05_2_Test002 Fail (0m46.793s)
> crashrecovery05_2 CrashRecovery05_2_Test003 Fail (2m2.944s)
> crashrecovery05_2 CrashRecovery05_2_Test005 Fail (0m46.742s)
> crashrecovery05_2 CrashRecovery05_2_Test006 Fail (0m42.978s)
> crashrecovery05_2 CrashRecovery05_2_Test028 Fail (2m9.683s)
> crashrecovery05_2 CrashRecovery05_2_Test031 Fail (0m49.745s)
> crashrecovery12 CrashRecovery12_Test03 Fail (0m15.884s)
> Buildfile: /home/hudson/workspace/narayana-hqstore/PROFILE/QA_JTS_JDKORB/jdk/jdk8.latest/label/linux/qa/run-tests.xml
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBTM-2558) CI report generator error while getting issue info
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2558?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2558.
-------------------------------
> CI report generator error while getting issue info
> --------------------------------------------------
>
> Key: JBTM-2558
> URL: https://issues.jboss.org/browse/JBTM-2558
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: CI Report Generator
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.2.8.Final
>
>
> {code}
> Aggregating narayana build 979
> Aggregating narayana build 978
> Aggregating narayana build 863
> Aggregating narayana build 858
> Aggregating narayana build 830
> Aggregating narayana build 779
> Aggregating narayana build 638
> Aggregating narayana build 550
> Aggregating narayana-benchmarks build 56
> [31mGot an error while getting issue info: [object Object]
> [39m[31m
> [39m[31mTypeError: Uncaught, unspecified "error" event.
> at TypeError (<anonymous>)
> at DestroyableTransform.emit (events.js:74:15)
> at DestroyableTransform.onerror (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:604:12)
> at DestroyableTransform.emit (events.js:95:17)
> at onwriteError (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:345:10)
> at onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:363:5)
> at WritableState.onwrite (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:123:5)
> at afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:84:5)
> at TransformState.afterTransform (/home/hudson/workspace/ci-report-generator/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:59:12)
> at /home/hudson/workspace/ci-report-generator/streams/jiraInfoStream.js:23:17
> [39m[33mWarning: [36m-> [39m[31merror [39m[31m8[39m [36m/home/hudson/workspace/ci-report-generator/index.js[39m (8883ms) Use --force to continue.[39m
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBTM-2556) Improve OSGi integration
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2556?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2556.
-------------------------------
> Improve OSGi integration
> ------------------------
>
> Key: JBTM-2556
> URL: https://issues.jboss.org/browse/JBTM-2556
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: JTA
> Reporter: Amos Feng
> Assignee: Guillaume Nodet
> Fix For: 5.2.8.Final
>
>
> support configuration using ConfigAdmin
> track org.jboss.tm.XAResourceRecovery services for recovery
> In order to support correctly stopping / restarting / reconfiguring the transaction manager, we build our own class loader to load the core jars.
> This ensure that all static fields will be correctly reloaded when starting again after configuration change.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (JBTM-2565) ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2565?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2565.
-------------------------------
> ConnectableResourceRecordRecoveryModule uses tooling iterator which does not report errors and can fail in WildFly
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-2565
> URL: https://issues.jboss.org/browse/JBTM-2565
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.2.8.Final
>
>
> It happens to me that when using jdbc object store for transactions with driver loaded as a module then if I start server and stopped it right after the start is finished I can see error [1] and server stay stuck. I need to run {{kill -9}} to server finish.
> This seems to be connected with recovery processing. If I start server and not stopping it immediately after it was started then I do not experience this problem.
> But if leave server to run for some time and I decide to stop server at time when periodic recovery is in process (e.g. checking {{server.log}} activity by {{tail -F standalone/log/server.log}} then I experience the same problem.
> [1]
> {code}
> WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012251: allObjUids caught exception: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.naming.service.DefaultNamespaceContextSelectorService$1.getContext(DefaultNamespaceContextSelectorService.java:56)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:233)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess.getConnection(DataSourceJDBCAccess.java:53)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver.allObjUids(JDBCImple_driver.java:345)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:166)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:122)
> at com.arjuna.ats.arjuna.objectstore.ObjectStoreIterator.<init>(ObjectStoreIterator.java:53)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:390)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375)
> ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" java.lang.NullPointerException
> ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.arjuna.recovery.TransactionStatusConnectionManager.getTransactionStatus(TransactionStatusConnectionManager.java:92)
> ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:399)
> ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747)
> ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month