May 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2154) QA suite failure with db2 in jobs 71 and 72

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2154?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2154: ----------------------------------- Attachment: JTSRemote_TimeoutTest.tar log output for job 74 > QA suite failure with db2 in jobs 71 and 72 > ------------------------------------------- > > Key: JBTM-2154 > URL: https://issues.jboss.org/browse/JBTM-2154 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.0.2 > > Attachments: JTSRemote_TimeoutTest.tar > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2167) QA suite fialure with MySQL: CrashRecovery08_Test32, LockRecord_Thread_Test048a, CrashRecovery08_Test04

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2167: ------------------------------------- Summary: QA suite fialure with MySQL: CrashRecovery08_Test32, LockRecord_Thread_Test048a, CrashRecovery08_Test04 Key: JBTM-2167 URL: https://issues.jboss.org/browse/JBTM-2167 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Minor Fix For: 5.0.2 http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2166) narayana-jts-all is not stored in .m2 repository, when built with narayana.sh

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2166?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2166: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/509/ > narayana-jts-all is not stored in .m2 repository, when built with narayana.sh > ----------------------------------------------------------------------------- > > Key: JBTM-2166 > URL: https://issues.jboss.org/browse/JBTM-2166 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/508/ > My assumption is that it was caused by this commit, since it is the last one which modified narayana.sh: https://github.com/jbosstm/narayana/commit/947f384645151d5b9b0d9985aebc2d... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2154) QA suite failure with db2 in jobs 71 and 72

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2154?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2154: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... > QA suite failure with db2 in jobs 71 and 72 > ------------------------------------------- > > Key: JBTM-2154 > URL: https://issues.jboss.org/browse/JBTM-2154 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2166) narayana-jts-all is not stored in .m2 repository, when built with narayana.sh

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2166: ------------------------------------- Summary: narayana-jts-all is not stored in .m2 repository, when built with narayana.sh Key: JBTM-2166 URL: https://issues.jboss.org/browse/JBTM-2166 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Blocker Fix For: 5.0.2 http://172.17.131.2/view/Narayana+BlackTie/job/narayana/508/ My assumption is that it was caused by this commit, since it is the last one which modified narayana.sh: https://github.com/jbosstm/narayana/commit/947f384645151d5b9b0d9985aebc2d... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-2121: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1027126 > Add a jdbc object store implementation for later revisions of MySQL driver > -------------------------------------------------------------------------- > > Key: JBTM-2121 > URL: https://issues.jboss.org/browse/JBTM-2121 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.17.17, 5.0.1 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.20, 5.0.2 > > > commit 44553931 updated the MySQl driver to 5.1.28. > In this revision of the driver, it is reporting as mysql, not mysql_ab. It should be possible to duplicate our mysql_ab_driver to mysql_driver in order to catch both cases. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2121: -------------------------------- Fix Version/s: 4.17.20 > Add a jdbc object store implementation for later revisions of MySQL driver > -------------------------------------------------------------------------- > > Key: JBTM-2121 > URL: https://issues.jboss.org/browse/JBTM-2121 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.17.17, 5.0.1 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.20, 5.0.2 > > > commit 44553931 updated the MySQl driver to 5.1.28. > In this revision of the driver, it is reporting as mysql, not mysql_ab. It should be possible to duplicate our mysql_ab_driver to mysql_driver in order to catch both cases. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2159) It is possible for the CommitMarkableResource recovery manager to attempt to activate an AtomicAction while it is being committed which can cause filenotfoundstacktrace and NullPointerException

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2159?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2159. --------------------------------- Fix Version/s: 4.17.20 5.0.2 Resolution: Done > It is possible for the CommitMarkableResource recovery manager to attempt to activate an AtomicAction while it is being committed which can cause filenotfoundstacktrace and NullPointerException > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2159 > URL: https://issues.jboss.org/browse/JBTM-2159 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.20, 5.0.2 > > > Basically: > 1. App thread creates AA > 2. AA UID is seen in phase1 recovery thread by CommitMarkableResourceRecoveryModule > 3. App thread commits AA > 4. App thread deletes AA UID > 5. Recovery thread tries to activate AA with UID in CommitMarkableResourceRecoveryModule but it gets exceptions as shown here: > 12:23:07 [0m[33m12:23:07,915 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Could not query objectstore: : java.io.IOException: java.lang.NullPointerException > 12:23:07 at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:732) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 at com.arjuna.ats.internal.jta.recovery.arjunacore.RecoverConnectableAtomicAction.<init>(RecoverConnectableAtomicAction.java:52) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:379) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 Caused by: java.lang.NullPointerException > 12:23:07 at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:697) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 12:23:07 ... 4 more > 12:23:07 > 15:16:36 [0m[33m15:16:36,247 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Could not query objectstore: : com.arjuna.ats.arjuna.exceptions.ObjectStoreException: ShadowingStore::read_state error: java.io.FileNotFoundException: /tmp/activemq-soak/ibm-mq-testsuite/src/test/config/activemq/install/target/jboss-eap/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/0_ffff0a106418_-2b02421b_534ffd61_4c1764 (No such file or directory) > 15:16:36 at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore.read_state(ShadowingStore.java:412) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_committed(FileSystemStore.java:98) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.jta.recovery.arjunacore.RecoverConnectableAtomicAction.<init>(RecoverConnectableAtomicAction.java:48) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkFirstPass(CommitMarkableResourceRecordRecoveryModule.java:379) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 Caused by: java.io.FileNotFoundException: /tmp/activemq-soak/ibm-mq-testsuite/src/test/config/activemq/install/target/jboss-eap/standalone/data/tx-object-store/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/0_ffff0a106418_-2b02421b_534ffd61_4c1764 (No such file or directory) > 15:16:36 at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_51] > 15:16:36 at java.io.FileInputStream.<init>(FileInputStream.java:146) [rt.jar:1.7.0_51] > 15:16:36 at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore.read_state(ShadowingStore.java:406) [jbossjts-jacorb-4.17.18.Final-redhat-1.jar:4.17.18.Final-redhat-1] > 15:16:36 ... 5 more > 15:16:36 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2161) Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2161?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2161: -------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: (was: 5.0.2) (was: 4.17.20) Resolution: Migrated to another ITS Going a different route, we are making the app server wait for the CMR to be configured before starting the recovery manager. Details in the BZ, fix is to the app server only. > Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added > ------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2161 > URL: https://issues.jboss.org/browse/JBTM-2161 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Currently the list is fixed at startup time as it is stored in a list, as there is no real performance impact of checking the list once every 120 seconds and it will allow resources to be more dynamically added (at least for recovery). > It would assist with: https://bugzilla.redhat.com/show_bug.cgi?id=1091308 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2143) Backport "JBTM-1621. Failed to create service in XTS interop and recovery tests"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2143?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2143: ----------------------------------------------- Gytis Trikleris <gtrikler(a)redhat.com> changed the Status of [bug 1077183|https://bugzilla.redhat.com/show_bug.cgi?id=1077183] from NEW to MODIFIED > Backport "JBTM-1621. Failed to create service in XTS interop and recovery tests" > -------------------------------------------------------------------------------- > > Key: JBTM-2143 > URL: https://issues.jboss.org/browse/JBTM-2143 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.19 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2014