From issues at jboss.org Thu May 1 07:33:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 1 May 2014 07:33:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2162) Change CMR commit failure message In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2162: -------------------------------------- Summary: Change CMR commit failure message Key: JBTM-2162 URL: https://issues.jboss.org/browse/JBTM-2162 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.17.19 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Trivial Fix For: 4.17.20 If a transaction containing an XA and a CMR resource is committed and the CMR resource fails the commit then the warning message mentions onePhaseCommit. Even though the CMR is in reality a one phase resource the message can be confusing. Please change the message to something more generic. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 1 07:33:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 1 May 2014 07:33:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2162) Change CMR commit failure message In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2162: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1087726 > Change CMR commit failure message > --------------------------------- > > Key: JBTM-2162 > URL: https://issues.jboss.org/browse/JBTM-2162 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 4.17.20 > > > If a transaction containing an XA and a CMR resource is committed and the CMR resource fails the commit then the warning message mentions onePhaseCommit. Even though the CMR is in reality a one phase resource the message can be confusing. > Please change the message to something more generic. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 1 09:31:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 1 May 2014 09:31:56 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2161: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1091308 > 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 > Fix For: 4.17.20, 5.0.2 > > > 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) From issues at jboss.org Thu May 1 15:45:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 1 May 2014 15:45:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2162) Change CMR commit failure message In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2162: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/647, https://github.com/jbosstm/narayana/pull/648 > Change CMR commit failure message > --------------------------------- > > Key: JBTM-2162 > URL: https://issues.jboss.org/browse/JBTM-2162 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 4.17.20 > > > If a transaction containing an XA and a CMR resource is committed and the CMR resource fails the commit then the warning message mentions onePhaseCommit. Even though the CMR is in reality a one phase resource the message can be confusing. > Please change the message to something more generic. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 1 15:45:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 1 May 2014 15:45:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2162) Change CMR commit failure message In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2162: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Change CMR commit failure message > --------------------------------- > > Key: JBTM-2162 > URL: https://issues.jboss.org/browse/JBTM-2162 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 4.17.20 > > > If a transaction containing an XA and a CMR resource is committed and the CMR resource fails the commit then the warning message mentions onePhaseCommit. Even though the CMR is in reality a one phase resource the message can be confusing. > Please change the message to something more generic. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 05:41:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 May 2014 05:41:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2153) QA suite failure with oracle in job 71 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965051#comment-12965051 ] Tom Jenkinson commented on JBTM-2153: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/ > QA suite failure with oracle in job 71 > -------------------------------------- > > Key: JBTM-2153 > URL: https://issues.jboss.org/browse/JBTM-2153 > 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/71/DB_TYPE=oracle,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 05:41:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 May 2014 05:41:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2153) QA suite failure with oracle in job 71 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2153: -------------------------------- Priority: Major (was: Minor) > QA suite failure with oracle in job 71 > -------------------------------------- > > Key: JBTM-2153 > URL: https://issues.jboss.org/browse/JBTM-2153 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/71/DB_TYPE=oracle,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 05:41:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 May 2014 05:41:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2154) QA suite failure with db2 in jobs 71 and 72 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965052#comment-12965052 ] Tom Jenkinson commented on JBTM-2154: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/73/ > 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/71/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 05:41:58 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 May 2014 05:41:58 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2153) QA suite failure with oracle in job 71 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965051#comment-12965051 ] Tom Jenkinson edited comment on JBTM-2153 at 5/2/14 5:41 AM: ------------------------------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/73/ was (Author: tomjenkinson): http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/ > QA suite failure with oracle in job 71 > -------------------------------------- > > Key: JBTM-2153 > URL: https://issues.jboss.org/browse/JBTM-2153 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/71/DB_TYPE=oracle,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 07:05:57 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 2 May 2014 07:05:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2153) QA suite failure with oracle in job 71 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965073#comment-12965073 ] Michael Musgrove commented on JBTM-2153: ---------------------------------------- The oracle issue is caused by too many db connectons: bq. 2014-04-24 19:55:59,962 out: java.sql.SQLException: Listener refused the connection with the following error: bq. 2014-04-24 19:55:59,962 out: ORA-12519, TNS:no appropriate service handler found Rather than find out which test(s) are opening too many I propose to just increase the number of allowed connections. I am not sure whether the issue with DB2 is similar in nature so I will need to keep looking into those. > QA suite failure with oracle in job 71 > -------------------------------------- > > Key: JBTM-2153 > URL: https://issues.jboss.org/browse/JBTM-2153 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/71/DB_TYPE=oracle,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 08:35:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 2 May 2014 08:35:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2134) ArjunaCore Performance3 test failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2134. ------------------------------------ Resolution: Done Last time I looked the issue was caused by to many connections to the oracle db. Doubling the number "alter system set processes=300 scope=spfile" in the oracle config should resolve the issue. > ArjunaCore Performance3 test failed > ----------------------------------- > > Key: JBTM-2134 > URL: https://issues.jboss.org/browse/JBTM-2134 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/67/DB_TYPE=oracle,jdk=jdk7.latest,slave=linux/console > {code} > test(com.hp.mwtests.ts.arjuna.performance.Performance3) Time elapsed: 0.241 sec <<< ERROR! > java.lang.ExceptionInInitializerError: null > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:158) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:110) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:67) > at com.arjuna.ats.arjuna.recovery.ActionStatusService.(ActionStatusService.java:64) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at com.arjuna.ats.internal.arjuna.common.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:137) > at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start(TransactionStatusManager.java:126) > at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.(TransactionStatusManager.java:58) > at com.arjuna.ats.arjuna.coordinator.TxControl.createTransactionStatusManager(TxControl.java:188) > at com.arjuna.ats.arjuna.coordinator.TxControl.(TxControl.java:264) > at com.arjuna.ats.arjuna.coordinator.BasicAction.Begin(BasicAction.java:1391) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.start(TwoPhaseCoordinator.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.start(TwoPhaseCoordinator.java:65) > at com.hp.mwtests.ts.arjuna.performance.Performance3.test(Performance3.java:49) > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 10:51:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 May 2014 10:51:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2163) Produce an OSGi wrapper In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2163: ----------------------------------- Summary: Produce an OSGi wrapper Key: JBTM-2163 URL: https://issues.jboss.org/browse/JBTM-2163 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Gytis Trikleris Fix For: 5.0.2 JBTM-669 has a draft implementation you can look at. Try to get the service running in Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 10:53:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 May 2014 10:53:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2163) Create an OSGi bundle activator In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2163: -------------------------------- Summary: Create an OSGi bundle activator (was: Produce an OSGi wrapper) > Create an OSGi bundle activator > ------------------------------- > > Key: JBTM-2163 > URL: https://issues.jboss.org/browse/JBTM-2163 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.2 > > > JBTM-669 has a draft implementation you can look at. Try to get the service running in Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 10:55:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 2 May 2014 10:55:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2163) Create an OSGi bundle activator In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2163: -------------------------------- Description: JBTM-669 has a draft implementation you can look at. (was: JBTM-669 has a draft implementation you can look at. Try to get the service running in Karaf.) > Create an OSGi bundle activator > ------------------------------- > > Key: JBTM-2163 > URL: https://issues.jboss.org/browse/JBTM-2163 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.2 > > > JBTM-669 has a draft implementation you can look at. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 12:17:56 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 2 May 2014 12:17:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2101) Blacktie integration CSTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965191#comment-12965191 ] Amos Feng commented on JBTM-2101: --------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/504/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el6/ > Blacktie integration CSTest hang > -------------------------------- > > Key: JBTM-2101 > URL: https://issues.jboss.org/browse/JBTM-2101 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/427/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el5 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 2 12:55:56 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 2 May 2014 12:55:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2101) Blacktie integration CSTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2101: ---------------------------- Priority: Major (was: Minor) > Blacktie integration CSTest hang > -------------------------------- > > Key: JBTM-2101 > URL: https://issues.jboss.org/browse/JBTM-2101 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/427/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el5 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 5 04:38:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 5 May 2014 04:38:56 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2159: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1089251 > 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 > > 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 12: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.(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 15: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.(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.(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) From issues at jboss.org Tue May 6 16:08:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 May 2014 16:08:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2164) CI app server rebase not working on Mac in narayana.sh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965961#comment-12965961 ] Tom Jenkinson commented on JBTM-2164: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/505/ http://172.17.131.2/view/Narayana+BlackTie/job/narayana/506/ http://172.17.131.2/view/Narayana+BlackTie/job/narayana/507/ > CI app server rebase not working on Mac in narayana.sh > ------------------------------------------------------ > > Key: JBTM-2164 > URL: https://issues.jboss.org/browse/JBTM-2164 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > > Seems to be occurring since the app server updated to 8.1.0.Final-SNAPSHOT. It could be an issue with the grep/sed for the app server version. > {quote} > Building AS > First time checkout of AS7 > Cloning into jboss-as... > From https://github.com/wildfly/wildfly > * [new branch] 7.1 -> upstream/7.1 > * [new branch] 7.1-ignore -> upstream/7.1-ignore > * [new branch] master -> upstream/master > * [new branch] master-ignore -> upstream/master-ignore > * [new tag] 7.1.2-prerelease -> 7.1.2-prerelease > * [new tag] 7.1.2.Final -> 7.1.2.Final > * [new tag] 7.1.3.Beta1 -> 7.1.3.Beta1 > * [new tag] 7.2.0.Final -> 7.2.0.Final > * [new tag] 7.2.0.Final-prerelease1 -> 7.2.0.Final-prerelease1 > * [new tag] 8.0.0.Alpha1 -> 8.0.0.Alpha1 > * [new tag] 8.0.0.Alpha2 -> 8.0.0.Alpha2 > * [new tag] 8.0.0.Alpha3 -> 8.0.0.Alpha3 > * [new tag] 8.0.0.Alpha4 -> 8.0.0.Alpha4 > * [new tag] 8.0.0.Beta1 -> 8.0.0.Beta1 > * [new tag] 8.0.0.CR1 -> 8.0.0.CR1 > * [new tag] 8.0.0.Final -> 8.0.0.Final > * [new tag] 8.1.0.CR1 -> 8.1.0.CR1 > This is the JBoss-AS commit > 4e5271d07ace06e19745b933f9141f718bdce1b5 > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > Current branch 5_BRANCH is up to date. > AS version is 8.1.0.Final-SNAPSHOT > Need to upgrade the jboss-as.version in the narayana pom.xml to > Build step 'Execute shell' marked build as failure > Archiving artifacts > Sending e-mails to: ***** > Finished: FAILURE > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 6 16:08:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 6 May 2014 16:08:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2164) CI app server rebase not working on Mac in narayana.sh In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2164: ----------------------------------- Summary: CI app server rebase not working on Mac in narayana.sh Key: JBTM-2164 URL: https://issues.jboss.org/browse/JBTM-2164 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: BlackTie, Build System Reporter: Tom Jenkinson Assignee: Amos Feng Priority: Critical Seems to be occurring since the app server updated to 8.1.0.Final-SNAPSHOT. It could be an issue with the grep/sed for the app server version. {quote} Building AS First time checkout of AS7 Cloning into jboss-as... >From https://github.com/wildfly/wildfly * [new branch] 7.1 -> upstream/7.1 * [new branch] 7.1-ignore -> upstream/7.1-ignore * [new branch] master -> upstream/master * [new branch] master-ignore -> upstream/master-ignore * [new tag] 7.1.2-prerelease -> 7.1.2-prerelease * [new tag] 7.1.2.Final -> 7.1.2.Final * [new tag] 7.1.3.Beta1 -> 7.1.3.Beta1 * [new tag] 7.2.0.Final -> 7.2.0.Final * [new tag] 7.2.0.Final-prerelease1 -> 7.2.0.Final-prerelease1 * [new tag] 8.0.0.Alpha1 -> 8.0.0.Alpha1 * [new tag] 8.0.0.Alpha2 -> 8.0.0.Alpha2 * [new tag] 8.0.0.Alpha3 -> 8.0.0.Alpha3 * [new tag] 8.0.0.Alpha4 -> 8.0.0.Alpha4 * [new tag] 8.0.0.Beta1 -> 8.0.0.Beta1 * [new tag] 8.0.0.CR1 -> 8.0.0.CR1 * [new tag] 8.0.0.Final -> 8.0.0.Final * [new tag] 8.1.0.CR1 -> 8.1.0.CR1 This is the JBoss-AS commit 4e5271d07ace06e19745b933f9141f718bdce1b5 >From https://github.com/wildfly/wildfly * branch master -> FETCH_HEAD Current branch 5_BRANCH is up to date. AS version is 8.1.0.Final-SNAPSHOT Need to upgrade the jboss-as.version in the narayana pom.xml to Build step 'Execute shell' marked build as failure Archiving artifacts Sending e-mails to: ***** Finished: FAILURE {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 7 05:46:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 7 May 2014 05:46:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966062#comment-12966062 ] Michael Musgrove commented on JBTM-2110: ---------------------------------------- PR (http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-narayana/506/) adds support without recovery > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.jboss.org/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 7 11:10:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 7 May 2014 11:10:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966207#comment-12966207 ] RH Bugzilla Integration commented on JBTM-2124: ----------------------------------------------- Ondrej Chaloupka changed the Status of [bug 1064170|https://bugzilla.redhat.com/show_bug.cgi?id=1064170] from NEW to CLOSED > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ond?ej Chaloupka > Assignee: Tom Jenkinson > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 06:45:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 8 May 2014 06:45:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2165: -------------------------------------- Summary: CMR synchronisations should be interposed Key: JBTM-2165 URL: https://issues.jboss.org/browse/JBTM-2165 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 5.0.1, 4.17.19 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.20, 5.0.2 A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 06:45:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 8 May 2014 06:45:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2165: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1095413 > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 08:59:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 8 May 2014 08:59:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2076) Add security manager's permission checking in com.arjuna.webservices11.ServiceRegistry#getRegistry In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966431#comment-12966431 ] RH Bugzilla Integration commented on JBTM-2076: ----------------------------------------------- Gytis Trikleris changed the Status of [bug 1054888|https://bugzilla.redhat.com/show_bug.cgi?id=1054888] from NEW to MODIFIED > Add security manager's permission checking in com.arjuna.webservices11.ServiceRegistry#getRegistry > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2076 > URL: https://issues.jboss.org/browse/JBTM-2076 > 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, 5.0.2 > > > Permissions checking in public static methods is needed for Common Criteria certification. > Add something similar to this at the beginning of the method: > {code} > public static ServiceRegistry getRegistry() > { > SecurityManager sm = System.getSecurityManager(); > if (sm != null) { > sm.checkPermission(new RuntimePermission(ServiceRegistry.class.getName() + ".getRegistry")); > } > return REGISTRY ; > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 09:01:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 8 May 2014 09:01:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2143) Backport "JBTM-1621. Failed to create service in XTS interop and recovery tests" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966432#comment-12966432 ] RH Bugzilla Integration commented on JBTM-2143: ----------------------------------------------- Gytis Trikleris 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) From issues at jboss.org Thu May 8 10:31:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 8 May 2014 10:31:57 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Thu May 8 10:41:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 8 May 2014 10:41:56 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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 12: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.(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 15: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.(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.(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) From issues at jboss.org Thu May 8 10:53:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 8 May 2014 10:53:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Thu May 8 10:53:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 8 May 2014 10:53:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Thu May 8 14:13:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 8 May 2014 14:13:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2166) narayana-jts-all is not stored in .m2 repository, when built with narayana.sh In-Reply-To: References: Message-ID: 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/947f384645151d5b9b0d9985aebc2d96ef555a7a -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 14:19:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 8 May 2014 14:19:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2154) QA suite failure with db2 in jobs 71 and 72 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966567#comment-12966567 ] Gytis Trikleris commented on JBTM-2154: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/74/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/ > 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/71/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 14:21:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 8 May 2014 14:21:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2166) narayana-jts-all is not stored in .m2 repository, when built with narayana.sh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966571#comment-12966571 ] 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/947f384645151d5b9b0d9985aebc2d96ef555a7a -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 14:23:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 8 May 2014 14:23:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2167) QA suite fialure with MySQL: CrashRecovery08_Test32, LockRecord_Thread_Test048a, CrashRecovery08_Test04 In-Reply-To: References: Message-ID: 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/74/DB_TYPE=mysql,jdk=jdk7.latest,slave=linux -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 15:35:57 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 8 May 2014 15:35:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2154) QA suite failure with db2 in jobs 71 and 72 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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/71/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 8 18:25:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 8 May 2014 18:25:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2154) QA suite failure with db2 in jobs 71 and 72 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966611#comment-12966611 ] Michael Musgrove commented on JBTM-2154: ---------------------------------------- We also had issues with the oracle instance due to insufficient connections. I increased the number of db2 connections from 200 to 1000 (db2 update dbm cfg using max_connections 1000 automatic) to see if it fixes the issue (the db2diag.log is 4GB so I didn't check to see if we had any connection errors there): > 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/71/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 07:59:56 2014 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Fri, 9 May 2014 07:59:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1702) one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian von Kutzleben reopened JBTM-1702: ------------------------------------------- Sorry, that I need to reopen this issue again: We're testing against EAP 6.1.1, where JBTM-1702 is partially fixed (if an XA_RB* error is thrown, then it works) However our client intends to use the JTS implementation rather than the JTA implementation of the Arjuna TM, and when we enabled jts (by adding in the configuration) we encountered the original error (even with an XA_RB* error), even worse, the exception is not even logged (unlike with JTA mode)! (I added some System.out logging into our XAResource to verify, that indeed the very same exception is thrown). So I guess, the original mistake made it via cut'n'paste into both implementations and needs to be (fully) fixed for the respective JTS class as well. Thank you! Christian > one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1702 > URL: https://issues.jboss.org/browse/JBTM-1702 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M2 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.18, 5.0.2 > > > We provide our own XAResource implementation for our database product, > in our unit testsuite we do also test common error conditions. > The error condition we test here is, that XAResource.end() throws an XAException with an XA_RBCOMMFAIL error code, this error code (by definition and also in our implementation) indicates an unilateral transaction rollback. > The expected behavior is, that when the TransactionManager invokes end() during it's commit procedure and sees an exception, that the transaction is considered as rolled-back and the bean client receives an exception, indicating the transaction failure. > The observed behavior is, that the bean client completes the bean method invocation successfully. Of course the transaction was rolled back by the database server and the subsequent bean invocations don't work correctly, because data assumed to be stored was actually not stored. > This error occurs if and only if the one-phase optimization is used, i.e. if > exactly one XAResource instance is enlisted with the TransactionManager. > If we enlist 2+ XAResource instances, then the one-phase optimization can't be used and the observed behavior is as expected, i.e. the bean client gets an exception, that the transaction could not be completed successfully. > The broken logic is contained in here (also see a complete stack trace below): > com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > Here the outcome was TwoPhaseOutcome.FINISH_ERROR but is mapped to ActionStatus.COMMITTED, this is clearly wrong for all XA_RB* error codes. > FIX suggestion: If there are cases, where this mapping is required, then instead of one FINISH_ERROR return value, two return values should be introduced, so that at least all XA_RB* error codes can be mapped properly to a transaction failure. > This is the complete stacktrace of our exception (logged immediately prior before it was thrown): > About to throw 1: com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > at com.versant.odbms.XAResourceImpl.getResult(XAResourceImpl.java:553) > at com.versant.odbms.XAResourceBase.detach(XAResourceBase.java:54) > at com.versant.odbms.XAResourceImpl.end(XAResourceImpl.java:278) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:597) --> returns TwoPhaseOutcome.FINISH_ERROR (l.734) > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1475) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:98) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165) --> l.1169 break, no exception > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 10:19:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 9 May 2014 10:19:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2166) narayana-jts-all is not stored in .m2 repository, when built with narayana.sh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2166: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/651 > 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/947f384645151d5b9b0d9985aebc2d96ef555a7a -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 11:51:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 May 2014 11:51:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1702) one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1702: -------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/300/files, https://github.com/jbosstm/narayana/pull/606, https://github.com/jbosstm/narayana/pull/652, https://github.com/jbosstm/narayana/pull/653 (was: https://github.com/jbosstm/narayana/pull/300/files, https://github.com/jbosstm/narayana/pull/606) Hi, I have pulled the required changes into the JTS variants. CI is running on this now. Please may I ask you to verify you are getting the behaviour you are expecting also. (its #653 for the 4.17 version) Many thanks, Tom > one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1702 > URL: https://issues.jboss.org/browse/JBTM-1702 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M2 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.18, 5.0.2 > > > We provide our own XAResource implementation for our database product, > in our unit testsuite we do also test common error conditions. > The error condition we test here is, that XAResource.end() throws an XAException with an XA_RBCOMMFAIL error code, this error code (by definition and also in our implementation) indicates an unilateral transaction rollback. > The expected behavior is, that when the TransactionManager invokes end() during it's commit procedure and sees an exception, that the transaction is considered as rolled-back and the bean client receives an exception, indicating the transaction failure. > The observed behavior is, that the bean client completes the bean method invocation successfully. Of course the transaction was rolled back by the database server and the subsequent bean invocations don't work correctly, because data assumed to be stored was actually not stored. > This error occurs if and only if the one-phase optimization is used, i.e. if > exactly one XAResource instance is enlisted with the TransactionManager. > If we enlist 2+ XAResource instances, then the one-phase optimization can't be used and the observed behavior is as expected, i.e. the bean client gets an exception, that the transaction could not be completed successfully. > The broken logic is contained in here (also see a complete stack trace below): > com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > Here the outcome was TwoPhaseOutcome.FINISH_ERROR but is mapped to ActionStatus.COMMITTED, this is clearly wrong for all XA_RB* error codes. > FIX suggestion: If there are cases, where this mapping is required, then instead of one FINISH_ERROR return value, two return values should be introduced, so that at least all XA_RB* error codes can be mapped properly to a transaction failure. > This is the complete stacktrace of our exception (logged immediately prior before it was thrown): > About to throw 1: com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > at com.versant.odbms.XAResourceImpl.getResult(XAResourceImpl.java:553) > at com.versant.odbms.XAResourceBase.detach(XAResourceBase.java:54) > at com.versant.odbms.XAResourceImpl.end(XAResourceImpl.java:278) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:597) --> returns TwoPhaseOutcome.FINISH_ERROR (l.734) > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1475) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:98) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165) --> l.1169 break, no exception > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 9 13:37:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 9 May 2014 13:37:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2166) narayana-jts-all is not stored in .m2 repository, when built with narayana.sh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2166: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done I had renamed one of the profiles. I have reverted that change. > 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/947f384645151d5b9b0d9985aebc2d96ef555a7a -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 10 17:05:57 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sat, 10 May 2014 17:05:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2168) Consider changing some TXOJ warning messages to info or debug In-Reply-To: References: Message-ID: Mark Little created JBTM-2168: --------------------------------- Summary: Consider changing some TXOJ warning messages to info or debug Key: JBTM-2168 URL: https://issues.jboss.org/browse/JBTM-2168 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: STM, Transaction Core Affects Versions: 5.0.1 Reporter: Mark Little Assignee: Mark Little Priority: Minor Some warning messages in, say, LockManager for when lock conflicts occur should probably be reassigned as info, since we a) always fail safe, and b) return a status that indicates a lock conflict has happened. Hasn't been much of an issue to date, but the increase of multicore and Vert.x use could show these up a lot more. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sat May 10 17:17:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sat, 10 May 2014 17:17:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2169) Create some STM docs In-Reply-To: References: Message-ID: Mark Little created JBTM-2169: --------------------------------- Summary: Create some STM docs Key: JBTM-2169 URL: https://issues.jboss.org/browse/JBTM-2169 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, STM Affects Versions: 5.0.1 Reporter: Mark Little Assignee: Mark Little We don't have anything beyond some comments and readme files. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 03:31:56 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 12 May 2014 03:31:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2164) CI app server rebase not working on Mac in narayana.sh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2164: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/655 > CI app server rebase not working on Mac in narayana.sh > ------------------------------------------------------ > > Key: JBTM-2164 > URL: https://issues.jboss.org/browse/JBTM-2164 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > > Seems to be occurring since the app server updated to 8.1.0.Final-SNAPSHOT. It could be an issue with the grep/sed for the app server version. > {quote} > Building AS > First time checkout of AS7 > Cloning into jboss-as... > From https://github.com/wildfly/wildfly > * [new branch] 7.1 -> upstream/7.1 > * [new branch] 7.1-ignore -> upstream/7.1-ignore > * [new branch] master -> upstream/master > * [new branch] master-ignore -> upstream/master-ignore > * [new tag] 7.1.2-prerelease -> 7.1.2-prerelease > * [new tag] 7.1.2.Final -> 7.1.2.Final > * [new tag] 7.1.3.Beta1 -> 7.1.3.Beta1 > * [new tag] 7.2.0.Final -> 7.2.0.Final > * [new tag] 7.2.0.Final-prerelease1 -> 7.2.0.Final-prerelease1 > * [new tag] 8.0.0.Alpha1 -> 8.0.0.Alpha1 > * [new tag] 8.0.0.Alpha2 -> 8.0.0.Alpha2 > * [new tag] 8.0.0.Alpha3 -> 8.0.0.Alpha3 > * [new tag] 8.0.0.Alpha4 -> 8.0.0.Alpha4 > * [new tag] 8.0.0.Beta1 -> 8.0.0.Beta1 > * [new tag] 8.0.0.CR1 -> 8.0.0.CR1 > * [new tag] 8.0.0.Final -> 8.0.0.Final > * [new tag] 8.1.0.CR1 -> 8.1.0.CR1 > This is the JBoss-AS commit > 4e5271d07ace06e19745b933f9141f718bdce1b5 > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > Current branch 5_BRANCH is up to date. > AS version is 8.1.0.Final-SNAPSHOT > Need to upgrade the jboss-as.version in the narayana pom.xml to > Build step 'Execute shell' marked build as failure > Archiving artifacts > Sending e-mails to: ***** > Finished: FAILURE > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 04:27:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 12 May 2014 04:27:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2169) Create some STM docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966993#comment-12966993 ] Michael Musgrove commented on JBTM-2169: ---------------------------------------- We already have JBTM-2088 - I assume these two duplicate each other > Create some STM docs > -------------------- > > Key: JBTM-2169 > URL: https://issues.jboss.org/browse/JBTM-2169 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > > We don't have anything beyond some comments and readme files. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 05:47:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 12 May 2014 05:47:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2170) Jacoco failed to create QA code coverage report In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2170: ------------------------------------- Summary: Jacoco failed to create QA code coverage report Key: JBTM-2170 URL: https://issues.jboss.org/browse/JBTM-2170 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-codeCoverage/118 {code} BUILD SUCCESSFUL Total time: 510 minutes 46 seconds generating test coverage report Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml jacoco-report: [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec BUILD FAILED /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:540: Error while creating report Total time: 8 seconds Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml has-testoutput-output: testoutput.zip: [echo] archiving testoutput to testoutput-jacorb.zip [zip] Building zip: /home/hudson/workspace/narayana-codeCoverage/qa/testoutput-jacorb.zip BUILD SUCCESSFUL Total time: 9 seconds + rm -rf /home/hudson/.m2/repository/org/jboss/narayana + cd qa + ant -f run-tests.xml jacoco-report Buildfile: /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml jacoco-report: [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec BUILD FAILED /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:540: Error while creating report Total time: 9 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending e-mails to: gtrikler at redhat.com Finished: FAILURE {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 05:51:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 12 May 2014 05:51:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2156) InboundBridgeTestCase#testRollbackWithTwoParticipants test failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967017#comment-12967017 ] Gytis Trikleris commented on JBTM-2156: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/511/PROFILE=MAIN,jdk=jdk7.latest,label=linux > InboundBridgeTestCase#testRollbackWithTwoParticipants test failed > ----------------------------------------------------------------- > > Key: JBTM-2156 > URL: https://issues.jboss.org/browse/JBTM-2156 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/PROFILE=MAIN,jdk=jdk7.latest,label=linux/498 > {code} > java.lang.AssertionError: expected:<1> but was:<2> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase.testRollbackWithTwoParticipants(InboundBridgeTestCase.java:130) > {code} > {code} > log4j:WARN No appenders could be found for logger (org.jboss.logging). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > Apr 21, 2014 7:11:09 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance > Apr 21, 2014 7:11:09 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.7.0_51/bin/java, -server, -Xms64m, -Xmx1024m, -XX:MaxPermSize=512m, -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -Djboss.bundles.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/bundles, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -server-config, standalone-rts.xml] > Listening for transport dt_socket at address: 8787 > 19:11:10,874 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final > 19:11:11,750 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final > 19:11:11,963 WARN [org.jboss.as.warn.fd-limit] (main) JBAS015972: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended > 19:11:12,034 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.1.0.Final-SNAPSHOT "Kenny" starting > 19:11:15,195 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) > 19:11:15,222 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.2.2.Final > 19:11:15,233 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.2.2.Final > 19:11:15,274 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.3.Final > 19:11:15,428 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) JBAS010280: Activating Infinispan subsystem. > 19:11:15,432 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 37) JBAS016300: Activating JacORB Subsystem > 19:11:15,588 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem > 19:11:15,645 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 55) JBAS015537: Activating WebServices Extension > 19:11:15,515 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012615: Activated the following JSF Implementations: [main] > 19:11:15,633 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem > 19:11:15,633 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 53) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique. > 19:11:15,975 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 54) JBAS017502: Undertow 1.0.5.Final starting > 19:11:15,993 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017502: Undertow 1.0.5.Final starting > 19:11:15,993 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service > 19:11:16,033 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:11:16,410 INFO [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016330: CORBA ORB Service started > 19:11:16,494 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 54) JBAS017527: Creating file handler for path /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/welcome-content > 19:11:16,845 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.21.Beta1 > 19:11:16,889 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default] > 19:11:17,101 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server default-server. > 19:11:17,112 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017531: Host default-host starting > 19:11:17,173 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 > 19:11:17,593 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,654 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,619 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,655 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,654 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,655 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,656 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,657 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,657 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,658 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,658 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,659 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,660 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,660 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,661 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,663 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,670 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,671 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,673 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,673 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,674 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,675 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,675 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,676 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,683 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,683 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,684 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,688 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,688 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,689 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,689 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,697 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,698 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,698 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:17,776 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,776 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,776 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,776 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,777 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,777 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,777 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,777 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,777 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,777 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,778 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,778 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,778 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,779 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,779 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,779 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,779 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,779 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,780 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,780 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,780 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,780 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,780 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,781 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,781 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,781 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,781 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,781 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,782 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,782 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,782 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,782 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:17,782 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:18,074 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: rest-at-participant > 19:11:18,080 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,080 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,081 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,081 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,081 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,081 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,082 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,082 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,082 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,082 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,082 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,083 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,083 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,083 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,083 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,094 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,094 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,094 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,094 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,094 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,095 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,095 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,095 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,095 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,095 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,096 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,096 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,096 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,096 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,097 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,097 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:18,179 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: volatile-rest-at-participant > 19:11:18,290 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /rest-at-coordinator > 19:11:18,623 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.5.Final) > 19:11:19,164 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2 > 19:11:19,373 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started > 19:11:19,421 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] > 19:11:19,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingpaging) > 19:11:19,445 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221006: Waiting to obtain live lock > 19:11:19,458 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/deployments > 19:11:20,117 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final > 19:11:20,125 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221012: Using AIO Journal > 19:11:20,363 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 58) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability. > 19:11:20,394 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support CORE > 19:11:20,448 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support AMQP > 19:11:20,452 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support STOMP > 19:11:20,534 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221034: Waiting to obtain live lock > 19:11:20,535 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221035: Live Server Obtained live lock > 19:11:21,013 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 19:11:21,014 INFO [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 19:11:21,136 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221007: Server is now live > 19:11:21,136 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [1dd22e9a-c97f-11e3-9af7-478b05d1c264] > 19:11:21,235 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory > 19:11:21,278 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:11:21,284 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA > 19:11:21,300 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:11:21,316 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue > 19:11:21,316 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DLQ > 19:11:21,317 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ > 19:11:21,349 INFO [org.hornetq.ra] (MSC service thread 1-1) HornetQ resource adaptor started > 19:11:21,350 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra > 19:11:21,352 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] > 19:11:21,352 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:11:21,554 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 19:11:21,554 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 19:11:21,555 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final-SNAPSHOT "Kenny" started in 11420ms - Started 222 of 270 services (91 services are lazy, passive or on-demand) > 19:11:22,237 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/content/04/b08ef21ce1a3327050cb27cefd4fb42b030864/content > 19:11:22,273 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "rest-tx-bridge-test.war" (runtime-name: "rest-tx-bridge-test.war") > 19:11:22,650 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.rest-tx-bridge-test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 19:11:22,655 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.rest-tx-bridge-test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:11:23,082 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /rest-tx-bridge-test > 19:11:23,305 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "rest-tx-bridge-test.war" (runtime-name : "rest-tx-bridge-test.war") > 19:11:29,047 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://localhost:8080/rest-tx-bridge-test/logging-participant-resource/terminator > 19:11:29,047 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffffac118321:97a9:53555ec7:17 > 19:11:29,642 INFO [org.hibernate.validator.internal.util.Version] (default task-1) HV000001: Hibernate Validator 5.1.0.Final > 19:11:29,875 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-3) LoggingRestATResource.resetInvocations() > 19:11:29,931 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-6) LoggingRestATResource.terminateParticipant(txstatus=TransactionCommitted) > 19:11:30,490 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-8) LoggingXAResource.start > 19:11:30,506 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-12) LoggingXAResource.end > 19:11:30,511 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-12) LoggingXAResource.rollback > 19:11:30,515 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-13) LoggingRestATResource.terminateParticipant(txstatus=TransactionRolledBack) > 19:11:30,555 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-14) LoggingRestATResource.getInvocations() > 19:11:30,631 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /rest-tx-bridge-test > 19:11:30,654 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment rest-tx-bridge-test.war (runtime-name: rest-tx-bridge-test.war) in 31ms > Apr 21, 2014 7:11:30 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 19:11:30,774 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/content/04/b08ef21ce1a3327050cb27cefd4fb42b030864/content > 19:11:30,774 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018558: Undeployed "rest-tx-bridge-test.war" (runtime-name: "rest-tx-bridge-test.war") > 19:11:30,820 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:11:30,821 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA] > 19:11:30,840 INFO [org.hornetq.ra] (ServerService Thread Pool -- 53) HQ151003: HornetQ resource adaptor stopped > 19:11:30,843 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: rest-at-participant > 19:11:30,844 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: volatile-rest-at-participant > 19:11:30,844 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /rest-at-coordinator > 19:11:30,847 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 25) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/DLQ > 19:11:30,848 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory > 19:11:30,849 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 24) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:11:30,850 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 29) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/ExpiryQueue > 19:11:30,871 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] > 19:11:30,880 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017532: Host default-host stopping > 19:11:30,973 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010418: Stopped Driver service with driver-name = h2 > 19:11:31,021 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 29) HQ221002: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [1dd22e9a-c97f-11e3-9af7-478b05d1c264] stopped > 19:11:31,026 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017521: Undertow HTTP listener default suspending > 19:11:31,027 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017520: Undertow HTTP listener default stopped, was bound to localhost.localdomain/127.0.0.1:8080 > 19:11:31,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017506: Undertow 1.0.5.Final stopping > 19:11:31,045 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: WildFly 8.1.0.Final-SNAPSHOT "Kenny" stopped in 114ms > Apr 21, 2014 7:11:31 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > Apr 21, 2014 7:11:31 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance > Apr 21, 2014 7:11:31 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.7.0_51/bin/java, -server, -Xms64m, -Xmx1024m, -XX:MaxPermSize=512m, -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -Djboss.bundles.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/bundles, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -server-config, standalone-rts.xml] > Listening for transport dt_socket at address: 8787 > 19:11:32,341 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final > 19:11:33,387 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final > 19:11:33,483 WARN [org.jboss.as.warn.fd-limit] (main) JBAS015972: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended > 19:11:33,561 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.1.0.Final-SNAPSHOT "Kenny" starting > 19:11:36,705 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) > 19:11:36,737 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.2.2.Final > 19:11:36,749 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.2.2.Final > 19:11:36,807 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.3.Final > 19:11:36,990 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) JBAS010280: Activating Infinispan subsystem. > 19:11:36,994 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 37) JBAS016300: Activating JacORB Subsystem > 19:11:37,123 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem > 19:11:37,065 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012615: Activated the following JSF Implementations: [main] > 19:11:37,184 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 53) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique. > 19:11:37,184 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem > 19:11:38,123 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service > 19:11:38,124 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.21.Beta1 > 19:11:38,319 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017502: Undertow 1.0.5.Final starting > 19:11:38,340 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:11:38,558 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 54) JBAS017502: Undertow 1.0.5.Final starting > 19:11:38,818 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.5.Final) > 19:11:38,857 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 54) JBAS017527: Creating file handler for path /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/welcome-content > 19:11:39,462 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = h2 > 19:11:39,846 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started > 19:11:39,850 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default] > 19:11:39,921 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017525: Started server default-server. > 19:11:39,938 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting > 19:11:40,065 INFO [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016328: CORBA Naming Service started > 19:11:40,215 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] > 19:11:40,219 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 > 19:11:40,284 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingpaging) > 19:11:40,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221006: Waiting to obtain live lock > 19:11:40,301 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension > 19:11:40,345 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221012: Using AIO Journal > 19:11:41,290 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final > 19:11:41,298 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 55) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability. > 19:11:41,328 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221043: Adding protocol support CORE > 19:11:41,366 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221043: Adding protocol support AMQP > 19:11:41,370 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221043: Adding protocol support STOMP > 19:11:41,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221034: Waiting to obtain live lock > 19:11:41,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221035: Live Server Obtained live lock > 19:11:41,670 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,687 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,687 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,688 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,688 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,689 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,691 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,691 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,691 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,693 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,694 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,694 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,696 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,701 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,702 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,703 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,703 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,704 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,705 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,705 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,706 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,712 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,713 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,713 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,714 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,715 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,715 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,715 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,716 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,716 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,716 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,717 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,717 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,717 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:41,718 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:42,192 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /rest-at-coordinator > 19:11:42,478 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,480 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,480 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,480 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,481 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,481 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,481 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,481 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,481 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,481 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,482 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,482 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,482 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,482 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,482 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,483 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,483 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,483 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,483 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,483 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,484 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,484 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,484 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,484 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,484 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,485 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,485 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,485 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,485 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,485 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,485 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,486 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:11:42,538 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: rest-at-participant > 19:11:42,556 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,557 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,557 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,557 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,558 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,558 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,558 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,558 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,558 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,558 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,559 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,559 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,559 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,559 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,559 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,560 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,560 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,560 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,560 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,564 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,565 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,565 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,565 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,565 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,565 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,566 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,566 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,566 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,566 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,566 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,566 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:11:42,626 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: volatile-rest-at-participant > 19:11:42,951 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 19:11:42,954 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/deployments > 19:11:42,954 INFO [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 19:11:43,144 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221007: Server is now live > 19:11:43,144 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [1dd22e9a-c97f-11e3-9af7-478b05d1c264] > 19:11:43,251 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 59) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:11:43,314 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue > 19:11:43,334 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA > 19:11:43,334 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DLQ > 19:11:43,335 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ > 19:11:43,371 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:11:43,372 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory > 19:11:43,486 INFO [org.hornetq.ra] (MSC service thread 1-1) HornetQ resource adaptor started > 19:11:43,487 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra > 19:11:43,489 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] > 19:11:43,490 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:11:43,640 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 19:11:43,641 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 19:11:43,642 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final-SNAPSHOT "Kenny" started in 12067ms - Started 222 of 270 services (91 services are lazy, passive or on-demand) > 19:11:43,822 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/content/c0/40f57550b8e91f5f90a8cf692adb6db4e43849/content > 19:11:43,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "rest-tx-bridge-test.war" (runtime-name: "rest-tx-bridge-test.war") > 19:11:44,248 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.rest-tx-bridge-test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 19:11:44,248 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.rest-tx-bridge-test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:11:44,703 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /rest-tx-bridge-test > 19:11:44,962 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "rest-tx-bridge-test.war" (runtime-name : "rest-tx-bridge-test.war") > 19:11:50,510 INFO [org.hibernate.validator.internal.util.Version] (default task-1) HV000001: Hibernate Validator 5.1.0.Final > 19:11:50,729 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-2) LoggingRestATResource.resetInvocations() > 19:11:50,849 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-4) LoggingXAResource.start > 19:11:50,867 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-7) LoggingXAResource.end > 19:11:50,867 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-7) LoggingXAResource.rollback > 19:11:50,932 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /rest-tx-bridge-test > 19:11:50,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment rest-tx-bridge-test.war (runtime-name: rest-tx-bridge-test.war) in 28ms > Apr 21, 2014 7:11:51 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 19:11:51,083 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/content/c0/40f57550b8e91f5f90a8cf692adb6db4e43849/content > 19:11:51,084 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "rest-tx-bridge-test.war" (runtime-name: "rest-tx-bridge-test.war") > 19:11:51,115 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:11:51,115 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA] > 19:11:51,133 INFO [org.hornetq.ra] (ServerService Thread Pool -- 26) HQ151003: HornetQ resource adaptor stopped > 19:11:51,141 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: rest-at-participant > 19:11:51,141 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: volatile-rest-at-participant > 19:11:51,141 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /rest-at-coordinator > 19:11:51,144 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 26) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/ExpiryQueue > 19:11:51,144 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 46) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/DLQ > 19:11:51,145 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 28) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory > 19:11:51,146 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 29) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:11:51,158 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] > 19:11:51,166 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017532: Host default-host stopping > 19:11:51,250 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010418: Stopped Driver service with driver-name = h2 > 19:11:51,337 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 28) HQ221002: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [1dd22e9a-c97f-11e3-9af7-478b05d1c264] stopped > 19:11:51,340 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017521: Undertow HTTP listener default suspending > 19:11:51,341 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017520: Undertow HTTP listener default stopped, was bound to localhost.localdomain/127.0.0.1:8080 > 19:11:51,344 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017506: Undertow 1.0.5.Final stopping > 19:11:51,351 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: WildFly 8.1.0.Final-SNAPSHOT "Kenny" stopped in 136ms > Apr 21, 2014 7:11:51 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > Apr 21, 2014 7:11:51 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance > Apr 21, 2014 7:11:51 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.7.0_51/bin/java, -server, -Xms64m, -Xmx1024m, -XX:MaxPermSize=512m, -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -Djboss.bundles.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/bundles, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -server-config, standalone-rts.xml] > Listening for transport dt_socket at address: 8787 > 19:11:52,612 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final > 19:11:53,429 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final > 19:11:53,528 WARN [org.jboss.as.warn.fd-limit] (main) JBAS015972: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended > 19:11:53,774 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.1.0.Final-SNAPSHOT "Kenny" starting > 19:11:56,871 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) > 19:11:56,898 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.2.2.Final > 19:11:56,910 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.2.2.Final > 19:11:56,953 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.3.Final > 19:11:57,112 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) JBAS010280: Activating Infinispan subsystem. > 19:11:57,116 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 37) JBAS016300: Activating JacORB Subsystem > 19:11:57,294 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem > 19:11:57,326 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem > 19:11:57,384 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:11:57,374 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 53) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique. > 19:11:57,423 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012615: Activated the following JSF Implementations: [main] > 19:11:57,709 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.21.Beta1 > 19:11:57,974 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service > 19:11:58,082 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started > 19:11:58,195 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 55) JBAS015537: Activating WebServices Extension > 19:11:58,210 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.5.Final) > 19:11:58,256 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = h2 > 19:11:58,333 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 54) JBAS017502: Undertow 1.0.5.Final starting > 19:11:58,565 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 54) JBAS017527: Creating file handler for path /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/welcome-content > 19:11:58,891 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default] > 19:11:58,655 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017502: Undertow 1.0.5.Final starting > 19:11:59,327 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started > 19:11:59,372 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server default-server. > 19:11:59,392 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017531: Host default-host starting > 19:11:59,602 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 > 19:11:59,971 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,986 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,986 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,987 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,989 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,989 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,990 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,993 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,994 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,994 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:11:59,995 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,174 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,175 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,176 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,176 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,177 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,177 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,177 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,178 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,178 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,178 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,179 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,179 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,181 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,182 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,182 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,183 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,183 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,183 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,193 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,193 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,194 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,194 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,194 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,196 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:00,497 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /rest-at-coordinator > 19:12:01,204 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final > 19:12:01,268 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingpaging) > 19:12:01,270 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221006: Waiting to obtain live lock > 19:12:01,319 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221012: Using AIO Journal > 19:12:01,352 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] > 19:12:01,376 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 58) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability. > 19:12:01,386 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,387 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,387 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,387 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,388 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,388 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,388 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,388 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,388 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,389 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,390 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,390 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,390 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,390 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,390 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,391 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,391 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,391 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,391 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,391 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,392 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,392 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,392 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,392 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,392 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,392 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,393 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:01,432 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: rest-at-participant > 19:12:01,690 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support CORE > 19:12:01,698 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support AMQP > 19:12:01,702 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support STOMP > 19:12:01,735 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,736 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,736 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,736 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,737 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,737 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,737 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,737 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,737 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,738 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,738 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,738 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,738 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,738 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,739 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,739 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,739 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,739 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,739 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,739 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,740 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,740 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,740 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,740 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,740 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,741 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,741 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,741 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,741 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,741 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,741 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:01,791 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: volatile-rest-at-participant > 19:12:01,925 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221034: Waiting to obtain live lock > 19:12:01,925 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221035: Live Server Obtained live lock > 19:12:02,146 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/deployments > 19:12:02,409 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 19:12:02,410 INFO [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 19:12:02,534 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221007: Server is now live > 19:12:02,534 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [1dd22e9a-c97f-11e3-9af7-478b05d1c264] > 19:12:02,716 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA > 19:12:02,738 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory > 19:12:02,760 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221003: trying to deploy queue jms.queue.DLQ > 19:12:02,779 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ > 19:12:02,779 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:12:02,780 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue > 19:12:02,781 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:12:02,788 INFO [org.hornetq.ra] (MSC service thread 1-1) HornetQ resource adaptor started > 19:12:02,789 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornetq-ra > 19:12:02,791 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] > 19:12:02,792 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:12:02,956 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 19:12:02,957 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 19:12:02,957 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final-SNAPSHOT "Kenny" started in 11101ms - Started 222 of 270 services (91 services are lazy, passive or on-demand) > 19:12:03,876 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/content/ef/1211b84d5c882656f6587b304f51a4fb0142a7/content > 19:12:03,911 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "rest-tx-bridge-test.war" (runtime-name: "rest-tx-bridge-test.war") > 19:12:04,327 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.rest-tx-bridge-test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 19:12:04,327 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.rest-tx-bridge-test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:12:04,819 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /rest-tx-bridge-test > 19:12:05,052 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "rest-tx-bridge-test.war" (runtime-name : "rest-tx-bridge-test.war") > 19:12:10,638 INFO [org.hibernate.validator.internal.util.Version] (default task-1) HV000001: Hibernate Validator 5.1.0.Final > 19:12:10,846 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-2) LoggingRestATResource.resetInvocations() > 19:12:10,956 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-4) LoggingXAResource.start > 19:12:10,973 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-7) LoggingXAResource.end > 19:12:10,974 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-7) LoggingXAResource.prepare > 19:12:11,057 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-7) LoggingXAResource.commit > 19:12:11,122 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /rest-tx-bridge-test > 19:12:11,145 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment rest-tx-bridge-test.war (runtime-name: rest-tx-bridge-test.war) in 29ms > Apr 21, 2014 7:12:11 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 19:12:11,270 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/content/ef/1211b84d5c882656f6587b304f51a4fb0142a7/content > 19:12:11,271 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018558: Undeployed "rest-tx-bridge-test.war" (runtime-name: "rest-tx-bridge-test.war") > 19:12:11,302 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011605: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:12:11,302 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA] > 19:12:11,325 INFO [org.hornetq.ra] (ServerService Thread Pool -- 52) HQ151003: HornetQ resource adaptor stopped > 19:12:11,329 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /rest-at-coordinator > 19:12:11,329 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: volatile-rest-at-participant > 19:12:11,383 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: rest-at-participant > 19:12:11,416 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] > 19:12:11,419 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017532: Host default-host stopping > 19:12:11,423 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 25) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:12:11,435 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010418: Stopped Driver service with driver-name = h2 > 19:12:11,495 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 26) HQ221002: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [1dd22e9a-c97f-11e3-9af7-478b05d1c264] stopped > 19:12:11,498 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017521: Undertow HTTP listener default suspending > 19:12:11,499 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017520: Undertow HTTP listener default stopped, was bound to localhost.localdomain/127.0.0.1:8080 > 19:12:11,505 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017506: Undertow 1.0.5.Final stopping > 19:12:11,516 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: WildFly 8.1.0.Final-SNAPSHOT "Kenny" stopped in 137ms > Apr 21, 2014 7:12:11 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > Apr 21, 2014 7:12:11 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance > Apr 21, 2014 7:12:11 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.7.0_51/bin/java, -server, -Xms64m, -Xmx1024m, -XX:MaxPermSize=512m, -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -Djboss.bundles.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/bundles, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -server-config, standalone-rts.xml] > Listening for transport dt_socket at address: 8787 > 19:12:12,749 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final > 19:12:13,653 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final > 19:12:13,901 WARN [org.jboss.as.warn.fd-limit] (main) JBAS015972: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended > 19:12:13,970 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.1.0.Final-SNAPSHOT "Kenny" starting > 19:12:17,023 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) > 19:12:17,050 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.2.2.Final > 19:12:17,061 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.2.2.Final > 19:12:17,104 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.3.Final > 19:12:17,258 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) JBAS010280: Activating Infinispan subsystem. > 19:12:17,262 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 37) JBAS016300: Activating JacORB Subsystem > 19:12:17,332 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012615: Activated the following JSF Implementations: [main] > 19:12:18,008 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:12:18,051 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem > 19:12:17,469 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 53) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique. > 19:12:17,469 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem > 19:12:18,456 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 55) JBAS015537: Activating WebServices Extension > 19:12:18,854 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started > 19:12:19,042 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default] > 19:12:19,047 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service > 19:12:19,051 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017502: Undertow 1.0.5.Final starting > 19:12:19,370 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.21.Beta1 > 19:12:19,762 INFO [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.5.Final) > 19:12:19,817 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 54) JBAS017502: Undertow 1.0.5.Final starting > 19:12:19,880 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = h2 > 19:12:19,991 INFO [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016328: CORBA Naming Service started > 19:12:20,238 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] > 19:12:20,391 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 54) JBAS017527: Creating file handler for path /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/welcome-content > 19:12:20,424 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017525: Started server default-server. > 19:12:20,465 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting > 19:12:20,593 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 > 19:12:21,172 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingjournal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingbindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messaginglargemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/messagingpaging) > 19:12:21,174 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221006: Waiting to obtain live lock > 19:12:21,203 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221012: Using AIO Journal > 19:12:21,236 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 58) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability. > 19:12:21,571 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.4.Final > 19:12:21,602 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support CORE > 19:12:21,636 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support AMQP > 19:12:21,640 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support STOMP > 19:12:21,902 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,917 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,917 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,918 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,918 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,920 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,921 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,921 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,922 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,922 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,923 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,927 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,927 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,928 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,928 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,929 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,930 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,931 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,937 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,937 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,944 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,945 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,945 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,946 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,946 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,947 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,947 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,947 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,947 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,949 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,950 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,950 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,950 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,951 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:21,951 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:12:22,452 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /rest-at-coordinator > 19:12:22,453 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221034: Waiting to obtain live lock > 19:12:22,453 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221035: Live Server Obtained live lock > 19:12:22,456 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,458 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,458 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,458 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,458 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,459 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,459 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,459 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,459 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,459 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,460 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,460 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,460 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,460 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,460 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,461 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,461 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,461 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,461 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,461 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,466 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,467 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,467 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,467 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,467 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,468 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,468 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,468 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,468 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,468 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,468 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,469 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:12:22,512 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: rest-at-participant > 19:12:22,536 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,715 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,715 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,715 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,715 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,716 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,716 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,716 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,716 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,716 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,717 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,717 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,717 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,717 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,717 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,717 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,718 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,718 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,718 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,718 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,718 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,719 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,719 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,719 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,719 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,719 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,721 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,721 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,721 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,721 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,721 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:12:22,761 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: volatile-rest-at-participant > 19:12:22,967 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/deployments > 19:12:23,246 INFO [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 19:12:23,248 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 19:12:23,303 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221007: Server is now live > 19:12:23,303 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [1dd22e9a-c97f-11e3-9af7-478b05d1c264] > 19:12:23,395 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory > 19:12:23,396 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DLQ > 19:12:23,411 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ > 19:12:23,501 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA > 19:12:23,538 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:12:23,539 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:12:23,540 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue > 19:12:23,682 INFO [org.hornetq.ra] (MSC service thread 1-2) HornetQ resource adaptor started > 19:12:23,683 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra > 19:12:23,685 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] > 19:12:23,686 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:12:23,893 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 19:12:23,893 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 19:12:23,894 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final-SNAPSHOT "Kenny" started in 11875ms - Started 222 of 270 services (91 services are lazy, passive or on-demand) > 19:12:24,149 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/content/96/41d4a7d2e16565d9e8ea1bc770138194823bc4/content > 19:12:24,183 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "rest-tx-bridge-test.war" (runtime-name: "rest-tx-bridge-test.war") > 19:12:24,568 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.rest-tx-bridge-test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 19:12:24,568 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.rest-tx-bridge-test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:12:25,001 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /rest-tx-bridge-test > 19:12:25,236 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "rest-tx-bridge-test.war" (runtime-name : "rest-tx-bridge-test.war") > 19:12:31,170 INFO [org.hibernate.validator.internal.util.Version] (default task-1) HV000001: Hibernate Validator 5.1.0.Final > 19:12:31,404 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-2) LoggingRestATResource.resetInvocations() > 19:12:31,523 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-5) LoggingXAResource.start > 19:12:31,534 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-8) LoggingXAResource.end > 19:12:31,535 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-8) LoggingXAResource.prepare > 19:12:31,639 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-9) LoggingRestATResource.terminateParticipant(txstatus=TransactionPrepared) > 19:12:31,691 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-10) LoggingRestATResource.terminateParticipant(txstatus=TransactionCommitted) > 19:12:31,695 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingXAResource] (default task-11) LoggingXAResource.commit > 19:12:31,733 INFO [org.jboss.narayana.rest.bridge.inbound.test.common.LoggingRestATResource] (default task-12) LoggingRestATResource.getInvocations() > 19:12:31,792 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /rest-tx-bridge-test > 19:12:31,815 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment rest-tx-bridge-test.war (runtime-name: rest-tx-bridge-test.war) in 30ms > Apr 21, 2014 7:12:31 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 19:12:31,912 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-8.1.0.Final-SNAPSHOT/standalone/data/content/96/41d4a7d2e16565d9e8ea1bc770138194823bc4/content > 19:12:31,913 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "rest-tx-bridge-test.war" (runtime-name: "rest-tx-bridge-test.war") > 19:12:31,931 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:12:31,932 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA] > 19:12:31,954 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /rest-at-coordinator > 19:12:31,954 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: rest-at-participant > 19:12:31,955 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: volatile-rest-at-participant > 19:12:31,957 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/DLQ > 19:12:31,958 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 28) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory > 19:12:31,959 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 25) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/ExpiryQueue > 19:12:31,978 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 27) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:12:31,983 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] > 19:12:31,984 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017532: Host default-host stopping > 19:12:31,997 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010418: Stopped Driver service with driver-name = h2 > 19:12:32,009 INFO [org.hornetq.ra] (ServerService Thread Pool -- 29) HQ151003: HornetQ resource adaptor stopped > 19:12:32,146 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 29) HQ221002: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [1dd22e9a-c97f-11e3-9af7-478b05d1c264] stopped > 19:12:32,148 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017521: Undertow HTTP listener default suspending > 19:12:32,149 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017520: Undertow HTTP listener default stopped, was bound to localhost.localdomain/127.0.0.1:8080 > 19:12:32,155 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017506: Undertow 1.0.5.Final stopping > 19:12:32,164 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: WildFly 8.1.0.Final-SNAPSHOT "Kenny" stopped in 66ms > Apr 21, 2014 7:12:32 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 06:33:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 May 2014 06:33:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1702) one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1702: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1702 > URL: https://issues.jboss.org/browse/JBTM-1702 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M2 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 5.0.2, 4.17.18 > > > We provide our own XAResource implementation for our database product, > in our unit testsuite we do also test common error conditions. > The error condition we test here is, that XAResource.end() throws an XAException with an XA_RBCOMMFAIL error code, this error code (by definition and also in our implementation) indicates an unilateral transaction rollback. > The expected behavior is, that when the TransactionManager invokes end() during it's commit procedure and sees an exception, that the transaction is considered as rolled-back and the bean client receives an exception, indicating the transaction failure. > The observed behavior is, that the bean client completes the bean method invocation successfully. Of course the transaction was rolled back by the database server and the subsequent bean invocations don't work correctly, because data assumed to be stored was actually not stored. > This error occurs if and only if the one-phase optimization is used, i.e. if > exactly one XAResource instance is enlisted with the TransactionManager. > If we enlist 2+ XAResource instances, then the one-phase optimization can't be used and the observed behavior is as expected, i.e. the bean client gets an exception, that the transaction could not be completed successfully. > The broken logic is contained in here (also see a complete stack trace below): > com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > Here the outcome was TwoPhaseOutcome.FINISH_ERROR but is mapped to ActionStatus.COMMITTED, this is clearly wrong for all XA_RB* error codes. > FIX suggestion: If there are cases, where this mapping is required, then instead of one FINISH_ERROR return value, two return values should be introduced, so that at least all XA_RB* error codes can be mapped properly to a transaction failure. > This is the complete stacktrace of our exception (logged immediately prior before it was thrown): > About to throw 1: com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > at com.versant.odbms.XAResourceImpl.getResult(XAResourceImpl.java:553) > at com.versant.odbms.XAResourceBase.detach(XAResourceBase.java:54) > at com.versant.odbms.XAResourceImpl.end(XAResourceImpl.java:278) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:597) --> returns TwoPhaseOutcome.FINISH_ERROR (l.734) > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1475) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:98) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165) --> l.1169 break, no exception > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 06:35:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 May 2014 06:35:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2171) narayana-rebase doesn't work on mac In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2171: ----------------------------------- Summary: narayana-rebase doesn't work on mac Key: JBTM-2171 URL: https://issues.jboss.org/browse/JBTM-2171 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Reporter: Tom Jenkinson Assignee: Paul Robinson ./scripts/hudson/narayana-rebase.sh: {quote} git log $ancestorMaster..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' ' git log $ancestor417..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' ' {quote} The files from wc are columns wide on Mac rather than 7 on Linux. You could put 1-8 and hope there weren't too many words but its dangerous. Probably an if-then-else required. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 06:53:57 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 12 May 2014 06:53:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967048#comment-12967048 ] Michael Musgrove commented on JBTM-2110: ---------------------------------------- I added a PR to make the QA JTSRemote_PerfTest configurable via system properties (https://github.com/jbosstm/narayana/pull/656) > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.jboss.org/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:45:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 May 2014 07:45:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2164) CI app server rebase not working on Mac in narayana.sh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2164: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.0.2 Resolution: Done > CI app server rebase not working on Mac in narayana.sh > ------------------------------------------------------ > > Key: JBTM-2164 > URL: https://issues.jboss.org/browse/JBTM-2164 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.2 > > > Seems to be occurring since the app server updated to 8.1.0.Final-SNAPSHOT. It could be an issue with the grep/sed for the app server version. > {quote} > Building AS > First time checkout of AS7 > Cloning into jboss-as... > From https://github.com/wildfly/wildfly > * [new branch] 7.1 -> upstream/7.1 > * [new branch] 7.1-ignore -> upstream/7.1-ignore > * [new branch] master -> upstream/master > * [new branch] master-ignore -> upstream/master-ignore > * [new tag] 7.1.2-prerelease -> 7.1.2-prerelease > * [new tag] 7.1.2.Final -> 7.1.2.Final > * [new tag] 7.1.3.Beta1 -> 7.1.3.Beta1 > * [new tag] 7.2.0.Final -> 7.2.0.Final > * [new tag] 7.2.0.Final-prerelease1 -> 7.2.0.Final-prerelease1 > * [new tag] 8.0.0.Alpha1 -> 8.0.0.Alpha1 > * [new tag] 8.0.0.Alpha2 -> 8.0.0.Alpha2 > * [new tag] 8.0.0.Alpha3 -> 8.0.0.Alpha3 > * [new tag] 8.0.0.Alpha4 -> 8.0.0.Alpha4 > * [new tag] 8.0.0.Beta1 -> 8.0.0.Beta1 > * [new tag] 8.0.0.CR1 -> 8.0.0.CR1 > * [new tag] 8.0.0.Final -> 8.0.0.Final > * [new tag] 8.1.0.CR1 -> 8.1.0.CR1 > This is the JBoss-AS commit > 4e5271d07ace06e19745b933f9141f718bdce1b5 > From https://github.com/wildfly/wildfly > * branch master -> FETCH_HEAD > Current branch 5_BRANCH is up to date. > AS version is 8.1.0.Final-SNAPSHOT > Need to upgrade the jboss-as.version in the narayana pom.xml to > Build step 'Execute shell' marked build as failure > Archiving artifacts > Sending e-mails to: ***** > Finished: FAILURE > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:57:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 12 May 2014 07:57:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2169) Create some STM docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967084#comment-12967084 ] Mark Little commented on JBTM-2169: ----------------------------------- Ah yes. I hadn't seen that one (don't recall getting the notification). > Create some STM docs > -------------------- > > Key: JBTM-2169 > URL: https://issues.jboss.org/browse/JBTM-2169 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > > We don't have anything beyond some comments and readme files. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:57:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 12 May 2014 07:57:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2169) Create some STM docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little resolved JBTM-2169. ------------------------------- Resolution: Duplicate Issue > Create some STM docs > -------------------- > > Key: JBTM-2169 > URL: https://issues.jboss.org/browse/JBTM-2169 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > > We don't have anything beyond some comments and readme files. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 07:57:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 12 May 2014 07:57:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2169) Create some STM docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2169. ----------------------------- > Create some STM docs > -------------------- > > Key: JBTM-2169 > URL: https://issues.jboss.org/browse/JBTM-2169 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > > We don't have anything beyond some comments and readme files. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 11:41:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 12 May 2014 11:41:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2088) STM needs documenting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2088 started by Mark Little. > STM needs documenting > --------------------- > > Key: JBTM-2088 > URL: https://issues.jboss.org/browse/JBTM-2088 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.0 > Reporter: Michael Musgrove > Assignee: Mark Little > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon May 12 14:32:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 12 May 2014 14:32:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1702) one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-1702: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=983039, https://bugzilla.redhat.com/show_bug.cgi?id=990503, https://bugzilla.redhat.com/show_bug.cgi?id=1096947 > one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1702 > URL: https://issues.jboss.org/browse/JBTM-1702 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M2 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.18, 5.0.2 > > > We provide our own XAResource implementation for our database product, > in our unit testsuite we do also test common error conditions. > The error condition we test here is, that XAResource.end() throws an XAException with an XA_RBCOMMFAIL error code, this error code (by definition and also in our implementation) indicates an unilateral transaction rollback. > The expected behavior is, that when the TransactionManager invokes end() during it's commit procedure and sees an exception, that the transaction is considered as rolled-back and the bean client receives an exception, indicating the transaction failure. > The observed behavior is, that the bean client completes the bean method invocation successfully. Of course the transaction was rolled back by the database server and the subsequent bean invocations don't work correctly, because data assumed to be stored was actually not stored. > This error occurs if and only if the one-phase optimization is used, i.e. if > exactly one XAResource instance is enlisted with the TransactionManager. > If we enlist 2+ XAResource instances, then the one-phase optimization can't be used and the observed behavior is as expected, i.e. the bean client gets an exception, that the transaction could not be completed successfully. > The broken logic is contained in here (also see a complete stack trace below): > com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > Here the outcome was TwoPhaseOutcome.FINISH_ERROR but is mapped to ActionStatus.COMMITTED, this is clearly wrong for all XA_RB* error codes. > FIX suggestion: If there are cases, where this mapping is required, then instead of one FINISH_ERROR return value, two return values should be introduced, so that at least all XA_RB* error codes can be mapped properly to a transaction failure. > This is the complete stacktrace of our exception (logged immediately prior before it was thrown): > About to throw 1: com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > at com.versant.odbms.XAResourceImpl.getResult(XAResourceImpl.java:553) > at com.versant.odbms.XAResourceBase.detach(XAResourceBase.java:54) > at com.versant.odbms.XAResourceImpl.end(XAResourceImpl.java:278) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:597) --> returns TwoPhaseOutcome.FINISH_ERROR (l.734) > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1475) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:98) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165) --> l.1169 break, no exception > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 03:32:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 03:32:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2172) Annotations on interfaces? In-Reply-To: References: Message-ID: Mark Little created JBTM-2172: --------------------------------- Summary: Annotations on interfaces? Key: JBTM-2172 URL: https://issues.jboss.org/browse/JBTM-2172 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: STM Affects Versions: 5.0.1 Reporter: Mark Little Assignee: Mark Little Priority: Optional Currently we only track annotations on implementing classes not interfaces. Annotating interfaces poses potential issues, e.g., with multiple inheritance, so I'm not even sure if we'd want to support it anyway. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 03:46:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 03:46:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2172) Annotations on interfaces? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967376#comment-12967376 ] Mark Little commented on JBTM-2172: ----------------------------------- Well, with the exception of class specific annotations which are required on the interface so that the Container knows what to do. > Annotations on interfaces? > -------------------------- > > Key: JBTM-2172 > URL: https://issues.jboss.org/browse/JBTM-2172 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > Priority: Optional > > Currently we only track annotations on implementing classes not interfaces. Annotating interfaces poses potential issues, e.g., with multiple inheritance, so I'm not even sure if we'd want to support it anyway. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 03:48:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 03:48:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2172) Annotations on interfaces? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2172 started by Mark Little. > Annotations on interfaces? > -------------------------- > > Key: JBTM-2172 > URL: https://issues.jboss.org/browse/JBTM-2172 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > Priority: Optional > > Currently we only track annotations on implementing classes not interfaces. Annotating interfaces poses potential issues, e.g., with multiple inheritance, so I'm not even sure if we'd want to support it anyway. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 03:48:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 03:48:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2172) Annotations on interfaces? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little resolved JBTM-2172. ------------------------------- Resolution: Won't Fix > Annotations on interfaces? > -------------------------- > > Key: JBTM-2172 > URL: https://issues.jboss.org/browse/JBTM-2172 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > Priority: Optional > > Currently we only track annotations on implementing classes not interfaces. Annotating interfaces poses potential issues, e.g., with multiple inheritance, so I'm not even sure if we'd want to support it anyway. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 03:48:57 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 03:48:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2172) Annotations on interfaces? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2172. ----------------------------- > Annotations on interfaces? > -------------------------- > > Key: JBTM-2172 > URL: https://issues.jboss.org/browse/JBTM-2172 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > Priority: Optional > > Currently we only track annotations on implementing classes not interfaces. Annotating interfaces poses potential issues, e.g., with multiple inheritance, so I'm not even sure if we'd want to support it anyway. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 05:36:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 05:36:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2172) Annotations on interfaces? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967405#comment-12967405 ] Mark Little commented on JBTM-2172: ----------------------------------- I suppose there's an argument to be made that annotations on an interface's methods could be allowed, being overridden in the implementation class(es). This would be a little more symmetric (so you could remove all annotations from the implementation class). I'm not convinced at the moment, so will leave this JIRA closed for now as Won't Fix. > Annotations on interfaces? > -------------------------- > > Key: JBTM-2172 > URL: https://issues.jboss.org/browse/JBTM-2172 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > Priority: Optional > > Currently we only track annotations on implementing classes not interfaces. Annotating interfaces poses potential issues, e.g., with multiple inheritance, so I'm not even sure if we'd want to support it anyway. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 05:40:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 13 May 2014 05:40:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2121: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1027126, https://bugzilla.redhat.com/show_bug.cgi?id=1097166 (was: 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) From issues at jboss.org Tue May 13 05:40:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 13 May 2014 05:40:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967407#comment-12967407 ] RH Bugzilla Integration commented on JBTM-2121: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1027126|https://bugzilla.redhat.com/show_bug.cgi?id=1027126] from NEW to ASSIGNED > 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) From issues at jboss.org Tue May 13 05:48:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 13 May 2014 05:48:56 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967411#comment-12967411 ] RH Bugzilla Integration commented on JBTM-2159: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1089251|https://bugzilla.redhat.com/show_bug.cgi?id=1089251] from NEW to ASSIGNED > 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 12: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.(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 15: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.(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.(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) From issues at jboss.org Tue May 13 05:48:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 05:48:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2173) Inherited annotations In-Reply-To: References: Message-ID: Mark Little created JBTM-2173: --------------------------------- Summary: Inherited annotations Key: JBTM-2173 URL: https://issues.jboss.org/browse/JBTM-2173 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: STM Affects Versions: 5.0.1 Reporter: Mark Little Assignee: Mark Little More of an open question at this point: should the annotations be @Inherited? Needs careful thought and time I don't have at this point ;) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 05:50:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 05:50:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2173) Inherited annotations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967412#comment-12967412 ] Mark Little commented on JBTM-2173: ----------------------------------- Careful thought in that some probably should be but others maybe not so much. > Inherited annotations > --------------------- > > Key: JBTM-2173 > URL: https://issues.jboss.org/browse/JBTM-2173 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > > More of an open question at this point: should the annotations be @Inherited? Needs careful thought and time I don't have at this point ;) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 06:01:03 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 06:01:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2174) Provide LockFree annotation and test In-Reply-To: References: Message-ID: Mark Little created JBTM-2174: --------------------------------- Summary: Provide LockFree annotation and test Key: JBTM-2174 URL: https://issues.jboss.org/browse/JBTM-2174 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: STM Affects Versions: 5.0.1 Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.2 TransactionFree exists but is a superset (disassociates the transaction context too). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 06:02:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 06:02:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2174) Provide LockFree annotation and test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little resolved JBTM-2174. ------------------------------- Resolution: Done > Provide LockFree annotation and test > ------------------------------------ > > Key: JBTM-2174 > URL: https://issues.jboss.org/browse/JBTM-2174 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.2 > > > TransactionFree exists but is a superset (disassociates the transaction context too). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 06:02:57 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 13 May 2014 06:02:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2174) Provide LockFree annotation and test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2174. ----------------------------- > Provide LockFree annotation and test > ------------------------------------ > > Key: JBTM-2174 > URL: https://issues.jboss.org/browse/JBTM-2174 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.2 > > > TransactionFree exists but is a superset (disassociates the transaction context too). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 08:56:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 13 May 2014 08:56:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1702) one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-1702: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=983039, https://bugzilla.redhat.com/show_bug.cgi?id=990503, https://bugzilla.redhat.com/show_bug.cgi?id=1096947, https://bugzilla.redhat.com/show_bug.cgi?id=1097265 (was: https://bugzilla.redhat.com/show_bug.cgi?id=983039, https://bugzilla.redhat.com/show_bug.cgi?id=990503, https://bugzilla.redhat.com/show_bug.cgi?id=1096947) > one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1702 > URL: https://issues.jboss.org/browse/JBTM-1702 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M2 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.18, 5.0.2 > > > We provide our own XAResource implementation for our database product, > in our unit testsuite we do also test common error conditions. > The error condition we test here is, that XAResource.end() throws an XAException with an XA_RBCOMMFAIL error code, this error code (by definition and also in our implementation) indicates an unilateral transaction rollback. > The expected behavior is, that when the TransactionManager invokes end() during it's commit procedure and sees an exception, that the transaction is considered as rolled-back and the bean client receives an exception, indicating the transaction failure. > The observed behavior is, that the bean client completes the bean method invocation successfully. Of course the transaction was rolled back by the database server and the subsequent bean invocations don't work correctly, because data assumed to be stored was actually not stored. > This error occurs if and only if the one-phase optimization is used, i.e. if > exactly one XAResource instance is enlisted with the TransactionManager. > If we enlist 2+ XAResource instances, then the one-phase optimization can't be used and the observed behavior is as expected, i.e. the bean client gets an exception, that the transaction could not be completed successfully. > The broken logic is contained in here (also see a complete stack trace below): > com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > Here the outcome was TwoPhaseOutcome.FINISH_ERROR but is mapped to ActionStatus.COMMITTED, this is clearly wrong for all XA_RB* error codes. > FIX suggestion: If there are cases, where this mapping is required, then instead of one FINISH_ERROR return value, two return values should be introduced, so that at least all XA_RB* error codes can be mapped properly to a transaction failure. > This is the complete stacktrace of our exception (logged immediately prior before it was thrown): > About to throw 1: com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1 at localhost]. > at com.versant.odbms.XAResourceImpl.getResult(XAResourceImpl.java:553) > at com.versant.odbms.XAResourceBase.detach(XAResourceBase.java:54) > at com.versant.odbms.XAResourceImpl.end(XAResourceImpl.java:278) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:597) --> returns TwoPhaseOutcome.FINISH_ERROR (l.734) > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1475) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:98) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165) --> l.1169 break, no exception > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 11:22:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 13 May 2014 11:22:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967559#comment-12967559 ] RH Bugzilla Integration commented on JBTM-2121: ----------------------------------------------- Brian Stansberry changed the Status of [bug 1027126|https://bugzilla.redhat.com/show_bug.cgi?id=1027126] from ASSIGNED to MODIFIED > 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) From issues at jboss.org Tue May 13 18:28:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 13 May 2014 18:28:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2165: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/658, https://github.com/jbosstm/narayana/pull/659 A normal beforeCompletion synchronisation (aka session synch) is allowed to enlist a CMR resource into a transaction which in turn will register its own synch. The latter must be ordered after any synchs that have already ran or are already running. The fix is to register CMR synchs as interposed (see javax.transaction.TransactionSynchronizationRegistry#registerInterposedSynchronization) which are guaranteed to run after all normal session synchs have been called. > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 13 22:48:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 13 May 2014 22:48:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2165: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 04:59:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 14 May 2014 04:59:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2165: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/659, https://github.com/jbosstm/narayana/pull/660 (was: https://github.com/jbosstm/narayana/pull/658, https://github.com/jbosstm/narayana/pull/659) > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 05:01:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 14 May 2014 05:01:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2175: ------------------------------------- Summary: XTS HierarchyTest failure Key: JBTM-2175 URL: https://issues.jboss.org/browse/JBTM-2175 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.0.2 http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux {code} ------------------------------------------------------------------------------- Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest ------------------------------------------------------------------------------- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! java.lang.AssertionError: null at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertFalse(Assert.java:64) at org.junit.Assert.assertFalse(Assert.java:74) at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` {code} {code} 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 18:39:22,978 INFO [stdout] (default task-4) 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 18:39:22,978 INFO [stdout] (default task-4) 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war")  {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 05:03:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 14 May 2014 05:03:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2175: ---------------------------------- Priority: Blocker (was: Minor) > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 05:03:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 14 May 2014 05:03:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967735#comment-12967735 ] Gytis Trikleris commented on JBTM-2175: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/518/PROFILE=XTS,jdk=jdk7.latest,label=linux/ > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 05:03:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 14 May 2014 05:03:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967734#comment-12967734 ] Gytis Trikleris commented on JBTM-2175: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/516/PROFILE=XTS,jdk=jdk7.latest,label=linux/ > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 06:41:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 14 May 2014 06:41:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2137) JDBCStore recovery is too slow In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2137: -------------------------------- Affects Version/s: (was: 5.0.1) (was: 4.17.18) > JDBCStore recovery is too slow > ------------------------------ > > Key: JBTM-2137 > URL: https://issues.jboss.org/browse/JBTM-2137 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.17.20, 5.0.2 > > > The linked CI job failed because the STATESTOREJBOSSTSTXTABLE had too many entries (>600) and this caused the recovery pass to take about 15 minutes which in turn causes subsequent tests to time out. The reason for so many entries is covered by JBTM-2133 but this JIRA is for the poor performance when there are so many entries. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 06:41:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 14 May 2014 06:41:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2137) JDBCStore recovery is too slow In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2137: -------------------------------- Fix Version/s: 4.17.21 (was: 4.17.20) > JDBCStore recovery is too slow > ------------------------------ > > Key: JBTM-2137 > URL: https://issues.jboss.org/browse/JBTM-2137 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.17.21, 5.0.2 > > > The linked CI job failed because the STATESTOREJBOSSTSTXTABLE had too many entries (>600) and this caused the recovery pass to take about 15 minutes which in turn causes subsequent tests to time out. The reason for so many entries is covered by JBTM-2133 but this JIRA is for the poor performance when there are so many entries. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 09:35:56 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 14 May 2014 09:35:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2162) Change CMR commit failure message In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967800#comment-12967800 ] RH Bugzilla Integration commented on JBTM-2162: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1087726|https://bugzilla.redhat.com/show_bug.cgi?id=1087726] from NEW to POST > Change CMR commit failure message > --------------------------------- > > Key: JBTM-2162 > URL: https://issues.jboss.org/browse/JBTM-2162 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 4.17.20 > > > If a transaction containing an XA and a CMR resource is committed and the CMR resource fails the commit then the warning message mentions onePhaseCommit. Even though the CMR is in reality a one phase resource the message can be confusing. > Please change the message to something more generic. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 09:35:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 14 May 2014 09:35:57 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967802#comment-12967802 ] RH Bugzilla Integration commented on JBTM-2159: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1089251|https://bugzilla.redhat.com/show_bug.cgi?id=1089251] from ASSIGNED to POST > 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 12: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.(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 15: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.(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.(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) From issues at jboss.org Wed May 14 09:35:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 14 May 2014 09:35:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967801#comment-12967801 ] RH Bugzilla Integration commented on JBTM-2165: ----------------------------------------------- tom.jenkinson at redhat.com changed the Status of [bug 1095413|https://bugzilla.redhat.com/show_bug.cgi?id=1095413] from NEW to POST > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 13:15:59 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Wed, 14 May 2014 13:15:59 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2176) Consider state override annotation. In-Reply-To: References: Message-ID: Mark Little created JBTM-2176: --------------------------------- Summary: Consider state override annotation. Key: JBTM-2176 URL: https://issues.jboss.org/browse/JBTM-2176 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: STM Affects Versions: 5.0.1 Reporter: Mark Little Assignee: Mark Little Priority: Optional The State annotation is not really needed since only things annotated with the NotState annotation are ignored and everything else will be saved. Maybe we need a class-level annotation that basically says "all member state must have an annotation to indicate State or NotState"? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 14 14:15:57 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Wed, 14 May 2014 14:15:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2177) Improve clone API for mvcc instances In-Reply-To: References: Message-ID: Mark Little created JBTM-2177: --------------------------------- Summary: Improve clone API for mvcc instances Key: JBTM-2177 URL: https://issues.jboss.org/browse/JBTM-2177 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: STM Affects Versions: 5.0.1 Reporter: Mark Little Assignee: Mark Little Currently you need to use the clone method on Container and pass in an "empty" instance of the type to clone into. With Pessimistic cc this instance is ignored, whereas with Optimistic we use it to create a new handle. Maybe use Cloneable instead on the implementation class and simplify the clone operation? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 04:07:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 15 May 2014 04:07:57 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968027#comment-12968027 ] RH Bugzilla Integration commented on JBTM-2159: ----------------------------------------------- Kabir Khan changed the Status of [bug 1089251|https://bugzilla.redhat.com/show_bug.cgi?id=1089251] from POST to MODIFIED > 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 12: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.(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 15: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.(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.(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) From issues at jboss.org Thu May 15 04:07:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 15 May 2014 04:07:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968028#comment-12968028 ] RH Bugzilla Integration commented on JBTM-2165: ----------------------------------------------- Kabir Khan changed the Status of [bug 1095413|https://bugzilla.redhat.com/show_bug.cgi?id=1095413] from POST to MODIFIED > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 04:07:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 15 May 2014 04:07:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2162) Change CMR commit failure message In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968029#comment-12968029 ] RH Bugzilla Integration commented on JBTM-2162: ----------------------------------------------- Kabir Khan changed the Status of [bug 1087726|https://bugzilla.redhat.com/show_bug.cgi?id=1087726] from POST to MODIFIED > Change CMR commit failure message > --------------------------------- > > Key: JBTM-2162 > URL: https://issues.jboss.org/browse/JBTM-2162 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 4.17.20 > > > If a transaction containing an XA and a CMR resource is committed and the CMR resource fails the commit then the warning message mentions onePhaseCommit. Even though the CMR is in reality a one phase resource the message can be confusing. > Please change the message to something more generic. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 06:55:59 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 May 2014 06:55:59 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2101) Blacktie integration CSTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2101: -------------------------------- Fix Version/s: 5.0.3 (was: 5.0.2) > Blacktie integration CSTest hang > -------------------------------- > > Key: JBTM-2101 > URL: https://issues.jboss.org/browse/JBTM-2101 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/427/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el5 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 06:55:59 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 May 2014 06:55:59 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2163) Create an OSGi bundle activator In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2163: -------------------------------- Fix Version/s: 5.0.3 (was: 5.0.2) > Create an OSGi bundle activator > ------------------------------- > > Key: JBTM-2163 > URL: https://issues.jboss.org/browse/JBTM-2163 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.3 > > > JBTM-669 has a draft implementation you can look at. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 06:55:59 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 May 2014 06:55:59 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2153) QA suite failure with oracle in job 71 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2153: -------------------------------- Fix Version/s: 5.0.3 (was: 5.0.2) > QA suite failure with oracle in job 71 > -------------------------------------- > > Key: JBTM-2153 > URL: https://issues.jboss.org/browse/JBTM-2153 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/71/DB_TYPE=oracle,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 06:55:59 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 May 2014 06:55:59 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2154) QA suite failure with db2 in jobs 71 and 72 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2154: -------------------------------- Fix Version/s: 5.0.3 (was: 5.0.2) > 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.3 > > Attachments: JTSRemote_TimeoutTest.tar > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/71/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 06:59:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 15 May 2014 06:59:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968073#comment-12968073 ] Tom Jenkinson commented on JBTM-2151: ------------------------------------- Hi, The QS is merged is this "resolved"? Thanks, Tom > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 07:21:56 2014 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Thu, 15 May 2014 07:21:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968076#comment-12968076 ] Paul Robinson commented on JBTM-2151: ------------------------------------- Yes, Although it's not tested, due to us not having a MongoDB instance running in CI. I left this open for that reason, should have commented. > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 08:55:59 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Thu, 15 May 2014 08:55:59 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2088) STM needs documenting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2088 stopped by Mark Little. > STM needs documenting > --------------------- > > Key: JBTM-2088 > URL: https://issues.jboss.org/browse/JBTM-2088 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.0 > Reporter: Michael Musgrove > Assignee: Mark Little > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 08:57:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Thu, 15 May 2014 08:57:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2088) STM needs documenting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2088. ----------------------------- Fix Version/s: 5.0.2 Resolution: Done Added initial draft. Should be sufficient for now. > STM needs documenting > --------------------- > > Key: JBTM-2088 > URL: https://issues.jboss.org/browse/JBTM-2088 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.0 > Reporter: Michael Musgrove > Assignee: Mark Little > Fix For: 5.0.2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 16:01:57 2014 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Thu, 15 May 2014 16:01:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968267#comment-12968267 ] Paul Robinson commented on JBTM-2175: ------------------------------------- This is a new test I added, that I believe should pass. I had to fix two .equals methods to have it pass. It did pass CI at the time. Not sure why it's failing now. I can try take a look tomorrow, but after that I'm on holiday. https://github.com/jbosstm/narayana/commit/8ac8d1fd036d6921f427dfc2d495156f94abcbf5 > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 16:05:56 2014 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Thu, 15 May 2014 16:05:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2171) narayana-rebase doesn't work on mac In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968268#comment-12968268 ] Paul Robinson commented on JBTM-2171: ------------------------------------- How urgent is this? I'm on holiday next week and have a lot to get finished tomorrow. > narayana-rebase doesn't work on mac > ----------------------------------- > > Key: JBTM-2171 > URL: https://issues.jboss.org/browse/JBTM-2171 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Paul Robinson > > ./scripts/hudson/narayana-rebase.sh: > {quote} > git log $ancestorMaster..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' ' > git log $ancestor417..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' ' > {quote} > The files from wc are columns wide on Mac rather than 7 on Linux. You could put 1-8 and hope there weren't too many words but its dangerous. Probably an if-then-else required. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 15 16:11:56 2014 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Thu, 15 May 2014 16:11:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968270#comment-12968270 ] Paul Robinson commented on JBTM-2175: ------------------------------------- Is it an intermittent failure? > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 04:13:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 04:13:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968335#comment-12968335 ] Gytis Trikleris commented on JBTM-2175: --------------------------------------- No, it's failing constantly. > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 04:21:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 04:21:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968338#comment-12968338 ] Gytis Trikleris commented on JBTM-2175: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/519/PROFILE=XTS,jdk=jdk7.latest,label=linux/ http://172.17.131.2/view/Narayana+BlackTie/job/narayana/520/PROFILE=XTS,jdk=jdk7.latest,label=linux/consoleText > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 04:39:57 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 04:39:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968341#comment-12968341 ] Gytis Trikleris commented on JBTM-2175: --------------------------------------- WildFly in CI server is not rebased to 5_BRANCH and is using Narayana 5.0.1.Final. Thus your equals method is not updated. > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 04:41:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 04:41:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968341#comment-12968341 ] Gytis Trikleris edited comment on JBTM-2175 at 5/16/14 4:40 AM: ---------------------------------------------------------------- [~paul.robinson], WildFly in CI server is not rebased to 5_BRANCH and is using Narayana 5.0.1.Final. Thus your equals method is not updated. was (Author: gytis): WildFly in CI server is not rebased to 5_BRANCH and is using Narayana 5.0.1.Final. Thus your equals method is not updated. > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 04:43:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 04:43:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968341#comment-12968341 ] Gytis Trikleris edited comment on JBTM-2175 at 5/16/14 4:43 AM: ---------------------------------------------------------------- [~paul.robinson], 5_BRANCH was corrupted. It does not have a commit which updates Narayana to 5.0.2.Final-SNAPSHOT. Thus your equals method is not updated. was (Author: gytis): [~paul.robinson], WildFly in CI server is not rebased to 5_BRANCH and is using Narayana 5.0.1.Final. Thus your equals method is not updated. > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 04:53:56 2014 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Fri, 16 May 2014 04:53:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968343#comment-12968343 ] Paul Robinson commented on JBTM-2175: ------------------------------------- That makes sense. So the failed test is valid, as the equals methods were broken. > XTS HierarchyTest failure > ------------------------- > > Key: JBTM-2175 > URL: https://issues.jboss.org/browse/JBTM-2175 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,jdk=jdk7.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! > testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` > {code} > {code} > 18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") > 18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war > 18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war > 18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war > 18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test > 18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 > 18:39:22,978 INFO [stdout] (default task-4) > 18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 > 18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test > 18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war > 18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms > 18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content > 18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 05:17:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 05:17:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2178) AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2178: ------------------------------------- Summary: AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure Key: JBTM-2178 URL: https://issues.jboss.org/browse/JBTM-2178 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Blocker Fix For: 5.0.2 http://172.17.131.2/view/Narayana+BlackTie/job/narayana/519/PROFILE=MAIN,jdk=jdk7.latest,label=linux/consoleText {code} ------------------------------------------------------------------------------- Test set: org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase ------------------------------------------------------------------------------- Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 232.04 sec <<< FAILURE! testTransactionAttributeNeverWithTransaction(org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase) Time elapsed: 24.745 sec <<< FAILURE! java.lang.AssertionError: expected:<412> but was:<500> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.junit.Assert.assertEquals(Assert.java:542) at org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase.testTransactionAttributeNeverWithTransaction(AnnotationsTestCase.java:126) {code} {code} 20:37:46,842 ERROR [org.jboss.as.ejb3.invocation] (default task-2) WFLYEJB0034: EJB Invocation failed on component ResourceWithTransactionAttributeAnnotation for method public javax.ws.rs.core.Response org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation.transactionAttributeNever(): javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] 20:37:46,858 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /rest-tx-bridge-test/resource-with-transaction-attribute-annotation/transaction-attribute-never: javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] 20:37:46,909 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 8 20:37:46,910 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0001: Unable to roll back active transaction: com.arjuna.ats.jta.exceptions.InvalidTerminationStateException at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple.rollbackAndDisassociate(TransactionImple.java:358) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:114) at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137) at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$1$1.tearDown(UndertowDeploymentInfoService.java:335) at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:52) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:291) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 05:19:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 05:19:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2178) AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968348#comment-12968348 ] Gytis Trikleris commented on JBTM-2178: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/520/ > AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure > ----------------------------------------------------------------------------- > > Key: JBTM-2178 > URL: https://issues.jboss.org/browse/JBTM-2178 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/519/PROFILE=MAIN,jdk=jdk7.latest,label=linux/consoleText > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase > ------------------------------------------------------------------------------- > Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 232.04 sec <<< FAILURE! > testTransactionAttributeNeverWithTransaction(org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase) Time elapsed: 24.745 sec <<< FAILURE! > java.lang.AssertionError: expected:<412> but was:<500> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase.testTransactionAttributeNeverWithTransaction(AnnotationsTestCase.java:126) > {code} > {code} > 20:37:46,842 ERROR [org.jboss.as.ejb3.invocation] (default task-2) WFLYEJB0034: EJB Invocation failed on component ResourceWithTransactionAttributeAnnotation for method public javax.ws.rs.core.Response org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation.transactionAttributeNever(): javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,858 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /rest-tx-bridge-test/resource-with-transaction-attribute-annotation/transaction-attribute-never: javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,909 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 8 > 20:37:46,910 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0001: Unable to roll back active transaction: com.arjuna.ats.jta.exceptions.InvalidTerminationStateException > at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple.rollbackAndDisassociate(TransactionImple.java:358) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:114) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$1$1.tearDown(UndertowDeploymentInfoService.java:335) > at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:52) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:291) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 05:19:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 05:19:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2178) AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968349#comment-12968349 ] Gytis Trikleris commented on JBTM-2178: --------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana/521/ > AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure > ----------------------------------------------------------------------------- > > Key: JBTM-2178 > URL: https://issues.jboss.org/browse/JBTM-2178 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/519/PROFILE=MAIN,jdk=jdk7.latest,label=linux/consoleText > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase > ------------------------------------------------------------------------------- > Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 232.04 sec <<< FAILURE! > testTransactionAttributeNeverWithTransaction(org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase) Time elapsed: 24.745 sec <<< FAILURE! > java.lang.AssertionError: expected:<412> but was:<500> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase.testTransactionAttributeNeverWithTransaction(AnnotationsTestCase.java:126) > {code} > {code} > 20:37:46,842 ERROR [org.jboss.as.ejb3.invocation] (default task-2) WFLYEJB0034: EJB Invocation failed on component ResourceWithTransactionAttributeAnnotation for method public javax.ws.rs.core.Response org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation.transactionAttributeNever(): javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,858 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /rest-tx-bridge-test/resource-with-transaction-attribute-annotation/transaction-attribute-never: javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,909 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 8 > 20:37:46,910 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0001: Unable to roll back active transaction: com.arjuna.ats.jta.exceptions.InvalidTerminationStateException > at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple.rollbackAndDisassociate(TransactionImple.java:358) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:114) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$1$1.tearDown(UndertowDeploymentInfoService.java:335) > at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:52) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:291) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 05:35:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 05:35:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2178) AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968351#comment-12968351 ] Gytis Trikleris commented on JBTM-2178: --------------------------------------- It fails because expected error code changed from JBAS014163 to WFLYEJB0063. > AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure > ----------------------------------------------------------------------------- > > Key: JBTM-2178 > URL: https://issues.jboss.org/browse/JBTM-2178 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/519/PROFILE=MAIN,jdk=jdk7.latest,label=linux/consoleText > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase > ------------------------------------------------------------------------------- > Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 232.04 sec <<< FAILURE! > testTransactionAttributeNeverWithTransaction(org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase) Time elapsed: 24.745 sec <<< FAILURE! > java.lang.AssertionError: expected:<412> but was:<500> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase.testTransactionAttributeNeverWithTransaction(AnnotationsTestCase.java:126) > {code} > {code} > 20:37:46,842 ERROR [org.jboss.as.ejb3.invocation] (default task-2) WFLYEJB0034: EJB Invocation failed on component ResourceWithTransactionAttributeAnnotation for method public javax.ws.rs.core.Response org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation.transactionAttributeNever(): javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,858 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /rest-tx-bridge-test/resource-with-transaction-attribute-annotation/transaction-attribute-never: javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,909 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 8 > 20:37:46,910 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0001: Unable to roll back active transaction: com.arjuna.ats.jta.exceptions.InvalidTerminationStateException > at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple.rollbackAndDisassociate(TransactionImple.java:358) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:114) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$1$1.tearDown(UndertowDeploymentInfoService.java:335) > at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:52) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:291) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 05:45:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 16 May 2014 05:45:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2178) AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2178: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/662 > AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure > ----------------------------------------------------------------------------- > > Key: JBTM-2178 > URL: https://issues.jboss.org/browse/JBTM-2178 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/519/PROFILE=MAIN,jdk=jdk7.latest,label=linux/consoleText > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase > ------------------------------------------------------------------------------- > Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 232.04 sec <<< FAILURE! > testTransactionAttributeNeverWithTransaction(org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase) Time elapsed: 24.745 sec <<< FAILURE! > java.lang.AssertionError: expected:<412> but was:<500> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase.testTransactionAttributeNeverWithTransaction(AnnotationsTestCase.java:126) > {code} > {code} > 20:37:46,842 ERROR [org.jboss.as.ejb3.invocation] (default task-2) WFLYEJB0034: EJB Invocation failed on component ResourceWithTransactionAttributeAnnotation for method public javax.ws.rs.core.Response org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation.transactionAttributeNever(): javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,858 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /rest-tx-bridge-test/resource-with-transaction-attribute-annotation/transaction-attribute-never: javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,909 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 8 > 20:37:46,910 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0001: Unable to roll back active transaction: com.arjuna.ats.jta.exceptions.InvalidTerminationStateException > at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple.rollbackAndDisassociate(TransactionImple.java:358) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:114) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$1$1.tearDown(UndertowDeploymentInfoService.java:335) > at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:52) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:291) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 05:47:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 16 May 2014 05:47:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2171) narayana-rebase doesn't work on mac In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968354#comment-12968354 ] Tom Jenkinson commented on JBTM-2171: ------------------------------------- Its not really urgent as I have disabled the rebase on mac, I just added PR checking on Mac hence why it wasn't spotted before. > narayana-rebase doesn't work on mac > ----------------------------------- > > Key: JBTM-2171 > URL: https://issues.jboss.org/browse/JBTM-2171 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Paul Robinson > > ./scripts/hudson/narayana-rebase.sh: > {quote} > git log $ancestorMaster..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' ' > git log $ancestor417..$myRev | grep commit | wc | cut -c 1-7 | tr -d ' ' > {quote} > The files from wc are columns wide on Mac rather than 7 on Linux. You could put 1-8 and hope there weren't too many words but its dangerous. Probably an if-then-else required. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 16 11:27:57 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 16 May 2014 11:27:57 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968463#comment-12968463 ] RH Bugzilla Integration commented on JBTM-2161: ----------------------------------------------- Kabir Khan changed the Status of [bug 1091308|https://bugzilla.redhat.com/show_bug.cgi?id=1091308] from NEW to MODIFIED > 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) From issues at jboss.org Tue May 20 04:52:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 20 May 2014 04:52:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2178) AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2178: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > AnnotationsTestCase#testTransactionAttributeNeverWithTransaction test failure > ----------------------------------------------------------------------------- > > Key: JBTM-2178 > URL: https://issues.jboss.org/browse/JBTM-2178 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/519/PROFILE=MAIN,jdk=jdk7.latest,label=linux/consoleText > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase > ------------------------------------------------------------------------------- > Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 232.04 sec <<< FAILURE! > testTransactionAttributeNeverWithTransaction(org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase) Time elapsed: 24.745 sec <<< FAILURE! > java.lang.AssertionError: expected:<412> but was:<500> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.jboss.narayana.rest.bridge.inbound.test.integration.AnnotationsTestCase.testTransactionAttributeNeverWithTransaction(AnnotationsTestCase.java:126) > {code} > {code} > 20:37:46,842 ERROR [org.jboss.as.ejb3.invocation] (default task-2) WFLYEJB0034: EJB Invocation failed on component ResourceWithTransactionAttributeAnnotation for method public javax.ws.rs.core.Response org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation.transactionAttributeNever(): javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,858 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /rest-tx-bridge-test/resource-with-transaction-attribute-annotation/transaction-attribute-never: javax.ejb.EJBException: WFLYEJB0063: Transaction present on server in Never call (EJB3 13.6.2.6) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:307) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:234) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.rest.bridge.inbound.test.common.ResourceWithTransactionAttributeAnnotation$$$view1.transactionAttributeNever(Unknown Source) [classes:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_51] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_51] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_51] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_51] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:296) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:250) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:237) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.8.Final.jar:] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.8.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > 20:37:46,909 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 8 > 20:37:46,910 ERROR [org.jboss.as.txn] (default task-2) WFLYTX0001: Unable to roll back active transaction: com.arjuna.ats.jta.exceptions.InvalidTerminationStateException > at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple.rollbackAndDisassociate(TransactionImple.java:358) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) [narayana-jts-jacorb-5.0.1.Final.jar:5.0.1.Final (revision: 2a6a44)] > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:114) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$1$1.tearDown(UndertowDeploymentInfoService.java:335) > at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:52) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:291) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.10.Final.jar:1.0.10.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 20 05:00:56 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 20 May 2014 05:00:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2179) ArjunaCore CachedTest failed In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2179: ------------------------------------- Summary: ArjunaCore CachedTest failed Key: JBTM-2179 URL: https://issues.jboss.org/browse/JBTM-2179 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Gytis Trikleris Assignee: Tom Jenkinson Priority: Minor Fix For: 5.0.2 http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/119 {code} ------------------------------------------------------------------------------- Test set: com.hp.mwtests.ts.arjuna.objectstore.CachedTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.495 sec <<< FAILURE! test(com.hp.mwtests.ts.arjuna.objectstore.CachedTest) Time elapsed: 0.378 sec <<< FAILURE! java.lang.AssertionError: null at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertTrue(Assert.java:52) at com.hp.mwtests.ts.arjuna.objectstore.CachedTest.test(CachedTest.java:120) {code} {code} i: 0 i: 1 i: 2 i: 3 i: 4 i: 5 i: 6 i: 7 i: 8 i: 9 i: 10 i: 11 i: 12 Thread for 0:ffffac118321:be80:5376a725:1 succeeded Thread for 0:ffffac118321:be80:5376a725:3 succeeded Thread for 0:ffffac118321:be80:5376a725:5 succeeded Thread for 0:ffffac118321:be80:5376a725:7 succeeded Thread for 0:ffffac118321:be80:5376a725:9 succeeded i: 13 i: 14 i: 15 i: 16 i: 17 i: 18 i: 19 Thread for 0:ffffac118321:be80:5376a725:d succeeded Thread for 0:ffffac118321:be80:5376a725:f succeeded Thread for 0:ffffac118321:be80:5376a725:11 succeeded Thread for 0:ffffac118321:be80:5376a725:13 succeeded Thread for 0:ffffac118321:be80:5376a725:15 succeeded Thread for 0:ffffac118321:be80:5376a725:17 succeeded i: 20 i: 21 i: 22 i: 23 i: 24 i: 25 i: 26 Thread for 0:ffffac118321:be80:5376a725:b succeeded Thread for 0:ffffac118321:be80:5376a725:1b succeeded Thread for 0:ffffac118321:be80:5376a725:1d succeeded i: 27 i: 28 i: 29 i: 30 i: 31 i: 32 i: 33 Thread for 0:ffffac118321:be80:5376a725:19 succeeded i: 34 i: 35 i: 36 i: 37 i: 38 i: 39 i: 40 i: 41 i: 42 i: 43 i: 44 i: 45 i: 46 i: 47 i: 48 i: 49 i: 50 i: 51 i: 52 i: 53 i: 54 i: 55 i: 56 i: 57 i: 58 i: 59 i: 60 i: 61 i: 62 i: 63 i: 64 i: 65 i: 66 i: 67 i: 68 i: 69 i: 70 i: 71 i: 72 i: 73 i: 74 i: 75 i: 76 i: 77 i: 78 i: 79 i: 80 i: 81 i: 82 i: 83 i: 84 i: 85 i: 86 i: 87 i: 88 i: 89 i: 90 i: 91 i: 92 Thread for 0:ffffac118321:be80:5376a725:1f succeeded Thread for 0:ffffac118321:be80:5376a725:21 succeeded Thread for 0:ffffac118321:be80:5376a725:23 succeeded Thread for 0:ffffac118321:be80:5376a725:25 succeeded Thread for 0:ffffac118321:be80:5376a725:27 succeeded Thread for 0:ffffac118321:be80:5376a725:29 succeeded Thread for 0:ffffac118321:be80:5376a725:2d succeeded Thread for 0:ffffac118321:be80:5376a725:2f succeeded Thread for 0:ffffac118321:be80:5376a725:31 succeeded Thread for 0:ffffac118321:be80:5376a725:33 succeeded Thread for 0:ffffac118321:be80:5376a725:35 succeeded Thread for 0:ffffac118321:be80:5376a725:37 succeeded Thread for 0:ffffac118321:be80:5376a725:39 succeeded Thread for 0:ffffac118321:be80:5376a725:3b succeeded Thread for 0:ffffac118321:be80:5376a725:3d succeeded Thread for 0:ffffac118321:be80:5376a725:3f succeeded Thread for 0:ffffac118321:be80:5376a725:41 succeeded Thread for 0:ffffac118321:be80:5376a725:43 succeeded Thread for 0:ffffac118321:be80:5376a725:45 succeeded Thread for 0:ffffac118321:be80:5376a725:47 succeeded Thread for 0:ffffac118321:be80:5376a725:49 succeeded Thread for 0:ffffac118321:be80:5376a725:4b succeeded Thread for 0:ffffac118321:be80:5376a725:4d succeeded Thread for 0:ffffac118321:be80:5376a725:4f succeeded Thread for 0:ffffac118321:be80:5376a725:51 succeeded Thread for 0:ffffac118321:be80:5376a725:53 succeeded Thread for 0:ffffac118321:be80:5376a725:55 succeeded Thread for 0:ffffac118321:be80:5376a725:57 succeeded Thread for 0:ffffac118321:be80:5376a725:59 succeeded Thread for 0:ffffac118321:be80:5376a725:5b succeeded Thread for 0:ffffac118321:be80:5376a725:5d succeeded Thread for 0:ffffac118321:be80:5376a725:5f succeeded Thread for 0:ffffac118321:be80:5376a725:61 succeeded Thread for 0:ffffac118321:be80:5376a725:63 succeeded Thread for 0:ffffac118321:be80:5376a725:65 succeeded Thread for 0:ffffac118321:be80:5376a725:67 succeeded Thread for 0:ffffac118321:be80:5376a725:69 succeeded Thread for 0:ffffac118321:be80:5376a725:6b succeeded Thread for 0:ffffac118321:be80:5376a725:6d succeeded Thread for 0:ffffac118321:be80:5376a725:6f succeeded Thread for 0:ffffac118321:be80:5376a725:71 succeeded Thread for 0:ffffac118321:be80:5376a725:73 succeeded Thread for 0:ffffac118321:be80:5376a725:75 succeeded Thread for 0:ffffac118321:be80:5376a725:77 succeeded Thread for 0:ffffac118321:be80:5376a725:79 succeeded Thread for 0:ffffac118321:be80:5376a725:7b succeeded Thread for 0:ffffac118321:be80:5376a725:7d succeeded Thread for 0:ffffac118321:be80:5376a725:7f succeeded Thread for 0:ffffac118321:be80:5376a725:81 succeeded Thread for 0:ffffac118321:be80:5376a725:83 succeeded Thread for 0:ffffac118321:be80:5376a725:85 succeeded Thread for 0:ffffac118321:be80:5376a725:87 succeeded Thread for 0:ffffac118321:be80:5376a725:8b succeeded Thread for 0:ffffac118321:be80:5376a725:8d succeeded Thread for 0:ffffac118321:be80:5376a725:8f succeeded Thread for 0:ffffac118321:be80:5376a725:91 succeeded Thread for 0:ffffac118321:be80:5376a725:93 succeeded Thread for 0:ffffac118321:be80:5376a725:97 succeeded Thread for 0:ffffac118321:be80:5376a725:99 succeeded Thread for 0:ffffac118321:be80:5376a725:9b succeeded Thread for 0:ffffac118321:be80:5376a725:9d succeeded Thread for 0:ffffac118321:be80:5376a725:9f succeeded Thread for 0:ffffac118321:be80:5376a725:a1 succeeded Thread for 0:ffffac118321:be80:5376a725:a5 succeeded Thread for 0:ffffac118321:be80:5376a725:a7 succeeded Thread for 0:ffffac118321:be80:5376a725:a9 succeeded i: 93 i: 94 i: 95 i: 96 i: 97 i: 98 i: 99 Thread for 0:ffffac118321:be80:5376a725:89 succeeded Thread for 0:ffffac118321:be80:5376a725:95 succeeded Thread for 0:ffffac118321:be80:5376a725:a3 succeeded Thread for 0:ffffac118321:be80:5376a725:ad succeeded Thread for 0:ffffac118321:be80:5376a725:af succeeded Thread for 0:ffffac118321:be80:5376a725:b1 succeeded Thread for 0:ffffac118321:be80:5376a725:b3 succeeded j: 0 j: 1 j: 2 j: 3 j: 4 j: 5 j: 6 j: 7 j: 8 j: 9 j: 10 j: 11 j: 12 j: 13 j: 14 j: 15 Thread for 0:ffffac118321:be80:5376a725:b5 succeeded java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.LinkedList.checkElementIndex(LinkedList.java:553) at java.util.LinkedList.get(LinkedList.java:474) at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.getState(CacheStore.java:564) at com.arjuna.ats.internal.arjuna.objectstore.CacheStore.read_state(CacheStore.java:130) at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_committed(FileSystemStore.java:98) at com.hp.mwtests.ts.arjuna.objectstore.ThreadWriter.run(CachedTest.java:69) Thread for 0:ffffac118321:be80:5376a725:2b failed Thread for 0:ffffac118321:be80:5376a725:ab succeeded j: 16 j: 17 j: 18 j: 19 j: 20 j: 21 j: 22 j: 23 j: 24 j: 25 j: 26 j: 27 j: 28 j: 29 j: 30 j: 31 j: 32 j: 33 j: 34 j: 35 j: 36 j: 37 j: 38 j: 39 j: 40 j: 41 j: 42 j: 43 j: 44 j: 45 j: 46 j: 47 j: 48 j: 49 j: 50 j: 51 j: 52 j: 53 j: 54 j: 55 j: 56 j: 57 j: 58 j: 59 j: 60 j: 61 j: 62 j: 63 j: 64 j: 65 j: 66 j: 67 j: 68 j: 69 j: 70 j: 71 j: 72 j: 73 j: 74 Thread for 0:ffffac118321:be80:5376a725:c5 succeeded Thread for 0:ffffac118321:be80:5376a725:c3 succeeded Thread for 0:ffffac118321:be80:5376a725:c1 succeeded Thread for 0:ffffac118321:be80:5376a725:bf succeeded Thread for 0:ffffac118321:be80:5376a725:bd succeeded Thread for 0:ffffac118321:be80:5376a725:bb succeeded Thread for 0:ffffac118321:be80:5376a725:b9 succeeded Thread for 0:ffffac118321:be80:5376a725:b7 succeeded {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 20 05:52:57 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 20 May 2014 05:52:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework In-Reply-To: References: Message-ID: Mark Little created JBTM-2180: --------------------------------- Summary: Determine whether or not we should use a specific collections framework Key: JBTM-2180 URL: https://issues.jboss.org/browse/JBTM-2180 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA, JTS, Performance Testing, REST, Transaction Core Affects Versions: 5.0.1 Reporter: Mark Little Assignee: Michael Musgrove We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should be use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 20 05:56:57 2014 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 20 May 2014 05:56:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2181) WS-AT performance test does not work with multi-threading In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2181: ------------------------------------- Summary: WS-AT performance test does not work with multi-threading Key: JBTM-2181 URL: https://issues.jboss.org/browse/JBTM-2181 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Performance Testing, XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.2 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 20 06:02:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 20 May 2014 06:02:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968987#comment-12968987 ] Michael Musgrove commented on JBTM-2180: ---------------------------------------- Initially we should profile which collections are suitable candidates to be replaced. My guess is that _transactions ConcurrentHashMap in TransactionImple could benefit from such a change. > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Michael Musgrove > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should be use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 20 08:16:57 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 20 May 2014 08:16:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little updated JBTM-2180: ------------------------------ Description: We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. was: We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should be use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Michael Musgrove > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 20 08:18:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 20 May 2014 08:18:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969025#comment-12969025 ] Mark Little commented on JBTM-2180: ----------------------------------- Yes. I know BasicAction uses Hashtable for maintaining child thread and actions, but since concurrent threads in the same transaction or nested transactions aren't used much, this may not be a problem there. StateManager's use of Hashtable may be a different matter though, since StateManager is used everywhere. However, having a good analysis of the overhead is definitely the right first step. Then at least if we make no changes we can do so based on facts and not supposition. Also precisely which collections framework we might use were it to be necessary, is a job in its own right :-) > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Michael Musgrove > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 04:30:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 23 May 2014 04:30:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2182: ----------------------------------- Summary: [quickstart] NoClassDefFoundError on ArjunaJTA/maven Key: JBTM-2182 URL: https://issues.jboss.org/browse/JBTM-2182 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Demonstrator Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.3 [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71) at TransactionManagerExample.main(TransactionManagerExample.java:39) Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2570) at java.lang.Class.getDeclaredFields(Class.java:1903) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78) ... 4 more Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager at java.net.URLClassLoader$1.run(URLClassLoader.java:372) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:360) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 9 more Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main? [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided Also: NCDFE in javax_transaction/TransactionExample: Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes. >From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top >From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 04:30:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 23 May 2014 04:30:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2182: -------------------------------- Reporter: Andrew Rubinger (was: Tom Jenkinson) > [quickstart] NoClassDefFoundError on ArjunaJTA/maven > ---------------------------------------------------- > > Key: JBTM-2182 > URL: https://issues.jboss.org/browse/JBTM-2182 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > Fix For: 5.0.3 > > > [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- > Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) > at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) > at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71) > at TransactionManagerExample.main(TransactionManagerExample.java:39) > Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2570) > at java.lang.Class.getDeclaredFields(Class.java:1903) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78) > ... 4 more > Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager > at java.net.URLClassLoader$1.run(URLClassLoader.java:372) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 9 more > Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main? > [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided > Also: NCDFE in javax_transaction/TransactionExample: > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes. > From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top > From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 04:48:57 2014 From: issues at jboss.org (Andrew Rubinger (JIRA)) Date: Fri, 23 May 2014 04:48:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970006#comment-12970006 ] Andrew Rubinger commented on JBTM-2182: --------------------------------------- [~mmusgrov] You won't be looking for a failure; you should be looking for this test *passing*. And as I say, it's not implemented as a test, nor is it executed as part of "mvn install" phase. The issue is as I note; the JTA API is in "provided" scope which is not available to the "exec" plugin. So, there are a few issues here: 1) This isn't included in the testsuite 2) The JTA API isn't on the --classpath when running >From what I've seen, this isn't isolated to the Arjuna/maven quickstart. :/ I'd have issued a PR for fixing, but unsure of how you guys would like to proceed. > [quickstart] NoClassDefFoundError on ArjunaJTA/maven > ---------------------------------------------------- > > Key: JBTM-2182 > URL: https://issues.jboss.org/browse/JBTM-2182 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > Fix For: 5.0.3 > > > [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- > Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) > at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) > at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71) > at TransactionManagerExample.main(TransactionManagerExample.java:39) > Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2570) > at java.lang.Class.getDeclaredFields(Class.java:1903) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78) > ... 4 more > Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager > at java.net.URLClassLoader$1.run(URLClassLoader.java:372) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 9 more > Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main? > [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided > Also: NCDFE in javax_transaction/TransactionExample: > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes. > From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top > From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 05:42:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 23 May 2014 05:42:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970023#comment-12970023 ] Tom Jenkinson commented on JBTM-2182: ------------------------------------- If you have a fix locally that is still with the Main approach then please do raise a PR for it - it would be greatly appreciated. I know you work for JBoss but would you mind signing our CLA? (JBoss Transactions - https://cla.jboss.org/index.seam) I will mark you as a Patch contributor and assign the issue to you if would like to go down this route. Thanks! Tom > [quickstart] NoClassDefFoundError on ArjunaJTA/maven > ---------------------------------------------------- > > Key: JBTM-2182 > URL: https://issues.jboss.org/browse/JBTM-2182 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > Fix For: 5.0.3 > > > [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- > Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) > at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) > at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71) > at TransactionManagerExample.main(TransactionManagerExample.java:39) > Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2570) > at java.lang.Class.getDeclaredFields(Class.java:1903) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78) > ... 4 more > Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager > at java.net.URLClassLoader$1.run(URLClassLoader.java:372) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 9 more > Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main? > [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided > Also: NCDFE in javax_transaction/TransactionExample: > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes. > From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top > From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 05:46:57 2014 From: issues at jboss.org (Andrew Rubinger (JIRA)) Date: Fri, 23 May 2014 05:46:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970025#comment-12970025 ] Andrew Rubinger commented on JBTM-2182: --------------------------------------- I don't have a great solution with the Mains approach that fixes point 1) above. I *could* fix 2), but the issue there is in scope=provided in dependencyManagement in a parent POM, and I'm not certain what else this would affect by changing the parent. Conversely, overriding on the child level is likely to not cover all the cases in which a NCDFE my occur; I've run into 3 of these already in various test cases. Honestly sounds like more a task for those guys familiar w/ the layout. :/ And I'd also recommend putting "exec:exec" into your CI jobs so that if you're not tracking proper unit tests, at least you'd get failure notifications in your builds. S, ALR > [quickstart] NoClassDefFoundError on ArjunaJTA/maven > ---------------------------------------------------- > > Key: JBTM-2182 > URL: https://issues.jboss.org/browse/JBTM-2182 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > Fix For: 5.0.3 > > > [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- > Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) > at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) > at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71) > at TransactionManagerExample.main(TransactionManagerExample.java:39) > Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2570) > at java.lang.Class.getDeclaredFields(Class.java:1903) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78) > ... 4 more > Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager > at java.net.URLClassLoader$1.run(URLClassLoader.java:372) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 9 more > Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main? > [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided > Also: NCDFE in javax_transaction/TransactionExample: > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes. > From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top > From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 05:48:56 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 23 May 2014 05:48:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970026#comment-12970026 ] Tom Jenkinson commented on JBTM-2182: ------------------------------------- Thanks Andrew, we can take a look then > [quickstart] NoClassDefFoundError on ArjunaJTA/maven > ---------------------------------------------------- > > Key: JBTM-2182 > URL: https://issues.jboss.org/browse/JBTM-2182 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > Fix For: 5.0.3 > > > [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- > Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) > at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) > at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71) > at TransactionManagerExample.main(TransactionManagerExample.java:39) > Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2570) > at java.lang.Class.getDeclaredFields(Class.java:1903) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78) > ... 4 more > Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager > at java.net.URLClassLoader$1.run(URLClassLoader.java:372) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 9 more > Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main? > [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided > Also: NCDFE in javax_transaction/TransactionExample: > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes. > From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top > From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 08:32:59 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 23 May 2014 08:32:59 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2183: -------------------------------------- Summary: Need finer grained control over which XAResource is used for recovery Key: JBTM-2183 URL: https://issues.jboss.org/browse/JBTM-2183 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 5.0.1, 4.17.20 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.21, 5.0.2 During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 23 08:35:01 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 23 May 2014 08:35:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2183: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1075008 > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.20, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.21, 5.0.2 > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 25 14:13:56 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 25 May 2014 14:13:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970324#comment-12970324 ] Mark Little commented on JBTM-2183: ----------------------------------- Have we seen this behaviour elsewhere in the past? I don't recall it. As to changing the default, we can't do that until the EAP 7 timeframe. > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.20, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.21, 5.0.2 > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Sun May 25 14:15:59 2014 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 25 May 2014 14:15:59 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970324#comment-12970324 ] Mark Little edited comment on JBTM-2183 at 5/25/14 2:15 PM: ------------------------------------------------------------ Have we seen this behaviour elsewhere in the past? I don't recall it. A change in Oracle? Or just lucky for us so far not to have seen it? As to changing the default, we can't do that until the EAP 7 timeframe even if we wanted to. Plus, we'd better be able to show that this has no impact on performance, reliability etc. in environments where the RM doesn't exhibit this behaviour. Otherwise may be best to err on the side of caution and perhaps catch the error in recovery and swap in the alternate behaviour for the next sweep. was (Author: marklittle): Have we seen this behaviour elsewhere in the past? I don't recall it. As to changing the default, we can't do that until the EAP 7 timeframe. > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.20, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.21, 5.0.2 > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 03:43:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 27 May 2014 03:43:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970661#comment-12970661 ] Tom Jenkinson commented on JBTM-2183: ------------------------------------- I think its that the EAP test suite now tests this and didn't before. It does sort of make sense that the user to commit has to have permissions on those tables. Maybe we could say the recovery user needs permissions on all the tables? but then we would need some additional config to indicate a recovery user. I will double check with Ondra that its not a regression. > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.20, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.21, 5.0.2 > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 05:16:00 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 27 May 2014 05:16:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970704#comment-12970704 ] Tom Jenkinson commented on JBTM-2183: ------------------------------------- Ondra has confirmed it is a new test, I have asked for a list of versions of Oracle which it affects. I can accept it as a requirement that the user committing a branch should have write access the tables. To be clear, this affects the scenario where you have multiple data sources accessing the same database with different credentials. > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.20, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.21, 5.0.2 > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 06:31:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 27 May 2014 06:31:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2183: ----------------------------------- Priority: Optional (was: Major) > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.20, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 4.17.21, 5.0.2 > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 06:41:57 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 27 May 2014 06:41:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970728#comment-12970728 ] Michael Musgrove commented on JBTM-2183: ---------------------------------------- After consultation with Jonathan I have downgraded the priority to optional. The recommendation is make sure that the recovery credentials on a connection are configured correctly: - set the recovery-username and recovery-password attributes to have sufficient privileges to access the oracle transaction tables - if multiple datasources are configured against the same database make sure that only one of them is enabled for recovery (by setting the boolean attribute no-recovery="true|false"). > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.20, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 4.17.21, 5.0.2 > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 12:31:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 27 May 2014 12:31:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970946#comment-12970946 ] Tom Jenkinson commented on JBTM-2183: ------------------------------------- Thanks Mike, that makes sense. A good approach. It might be useful still if the user doesn't want such a power user option but we can wait for customer request for that. > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.20, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 4.17.21, 5.0.2 > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 13:39:57 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 27 May 2014 13:39:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970965#comment-12970965 ] Michael Musgrove commented on JBTM-2182: ---------------------------------------- My recommendation is to go through each pom and explicitly add the missing dependencies. This would keep the examples self contained and make it easy for the user to figure out what the dependencies are. > [quickstart] NoClassDefFoundError on ArjunaJTA/maven > ---------------------------------------------------- > > Key: JBTM-2182 > URL: https://issues.jboss.org/browse/JBTM-2182 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > Fix For: 5.0.3 > > > [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- > Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) > at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) > at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71) > at TransactionManagerExample.main(TransactionManagerExample.java:39) > Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2570) > at java.lang.Class.getDeclaredFields(Class.java:1903) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78) > ... 4 more > Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager > at java.net.URLClassLoader$1.run(URLClassLoader.java:372) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 9 more > Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main? > [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided > Also: NCDFE in javax_transaction/TransactionExample: > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes. > From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top > From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 14:51:56 2014 From: issues at jboss.org (Andrew Rubinger (JIRA)) Date: Tue, 27 May 2014 14:51:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: Andrew Rubinger created JBTM-2184: ------------------------------------- Summary: NoClassDefFoundError: Missing Dependency on jboss-transaction-spi Key: JBTM-2184 URL: https://issues.jboss.org/browse/JBTM-2184 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Affects Versions: 5.0.1 Reporter: Andrew Rubinger Assignee: Tom Jenkinson Looks like Narayana is missing a dependency, as this isn't brought in transitively: {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 18:49:56 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 27 May 2014 18:49:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971020#comment-12971020 ] Michael Musgrove commented on JBTM-2184: ---------------------------------------- What's the procedure for ensuring our artifacts make it into maven central? How are you determining our missing dependencies? > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue May 27 19:15:59 2014 From: issues at jboss.org (Andrew Rubinger (JIRA)) Date: Tue, 27 May 2014 19:15:59 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971024#comment-12971024 ] Andrew Rubinger commented on JBTM-2184: --------------------------------------- Well, the missing dependency bit I qualify simply based on importing "org.jboss.narayana.jta:narayana-jta"; if this has classes that call out into jboss-transaction-spi and that's not a transitive dependency of narayana-jta, this is missing, correct? Unless you have some mechanism in place where some code paths have optional dependencies? So: *if* my issue above is valid and jboss-transaction-spi should be a transitive, runtime (or compile-time) dependency of narayana-jta, I'd suggest we add it as Step 1. And regarding Maven Central: again *if* this issue is valid, then any dependencies of a project in Central must also be in Central, as this remote repo is intended to be a complete repository. That's according to Sonatype rules and, if I'm remembering correctly, should be enforced by our Nexus installation when we go to promote/release builds. > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 03:01:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 28 May 2014 03:01:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971060#comment-12971060 ] Tom Jenkinson commented on JBTM-2184: ------------------------------------- Hi Mike, We can ask [~paul.robinson] to get the SPI synced to Maven Central. Once we overhaul the SPI it would be synced automatically because everything under org.jboss.narayana is synced to Maven Central already. Ask Paul to ask the central guys to sync the SPI too. Tom > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 03:01:57 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 28 May 2014 03:01:57 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2184: -------------------------------- Assignee: Paul Robinson (was: Tom Jenkinson) > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Paul Robinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 03:29:56 2014 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Wed, 28 May 2014 03:29:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971066#comment-12971066 ] Paul Robinson commented on JBTM-2184: ------------------------------------- We currently have all "org.jboss.jbossts" and "org.jboss.narayana" artefacts synced. Let me know what additional group ids you want, and I'll contact Sonatype. > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Paul Robinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 05:39:15 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 28 May 2014 05:39:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971121#comment-12971121 ] Michael Musgrove commented on JBTM-2184: ---------------------------------------- So my guess is that we need to add the dependency to ArjunaJTA/narayana-jta/pom.xml - what is the easiest way to test that? > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Paul Robinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 06:05:15 2014 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 28 May 2014 06:05:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971121#comment-12971121 ] Michael Musgrove edited comment on JBTM-2184 at 5/28/14 6:04 AM: ----------------------------------------------------------------- So my guess is that we need to add the dependency to ArjunaJTA/narayana-jta/pom.xml - what is the easiest way to test that? I ran tattletale over narayana-jta and it reports transitive dependencies on other stuff as well (org.hornetq.core and org.jfree). Does that imply we need to add explicit dependencies on those too? was (Author: mmusgrov): So my guess is that we need to add the dependency to ArjunaJTA/narayana-jta/pom.xml - what is the easiest way to test that? > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Paul Robinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 09:51:17 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 28 May 2014 09:51:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2133) Multiple QA test suite failures on Oracle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971251#comment-12971251 ] RH Bugzilla Integration commented on JBTM-2133: ----------------------------------------------- Ondrej Chaloupka changed the Status of [bug 1081448|https://bugzilla.redhat.com/show_bug.cgi?id=1081448] from NEW to VERIFIED > Multiple QA test suite failures on Oracle > ----------------------------------------- > > Key: JBTM-2133 > URL: https://issues.jboss.org/browse/JBTM-2133 > 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: 4.17.19, 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/68/DB_TYPE=oracle,jdk=jdk7.latest,slave=linux/consoleText > {code} > txcore_lockrecord LockRecord_Thread_Test032b Fail (0m37.778s) > txcore_lockrecord LockRecord_Thread_Test035b Fail (0m15.279s) > txcore_lockrecord LockRecord_Thread_Test036a Fail (0m12.145s) > txcore_lockrecord LockRecord_Thread_Test036b Fail (0m21.774s) > txcore_lockrecord LockRecord_Thread_Test043b Fail (0m10.901s) > txcore_lockrecord LockRecord_Thread_Test044b Fail (0m23.904s) > txcore_lockrecord LockRecord_Thread_Test048a Fail (0m13.528s) > txcore_lockrecord LockRecord_Thread_Test048b Fail (0m30.007s) > crashrecovery12 CrashRecovery12_Test03 Fail (4m10.784s) > crashrecovery12 CrashRecovery12_Test04 Fail (4m10.153s) > crashrecovery12 CrashRecovery12_Test05 Fail (4m11.909s) > crashrecovery12 CrashRecovery12_Test06 Fail (4m11.862s) > crashrecovery12 CrashRecovery12_Test07 Fail (4m11.435s) > crashrecovery12 CrashRecovery12_Test02 Fail (4m9.581s) > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 09:51:17 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 28 May 2014 09:51:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2130) All JDBC object store qa tests fail In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971250#comment-12971250 ] RH Bugzilla Integration commented on JBTM-2130: ----------------------------------------------- Ondrej Chaloupka changed the Status of [bug 1081448|https://bugzilla.redhat.com/show_bug.cgi?id=1081448] from NEW to VERIFIED > All JDBC object store qa tests fail > ----------------------------------- > > Key: JBTM-2130 > URL: https://issues.jboss.org/browse/JBTM-2130 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 4.17.19, 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/66/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 17:21:15 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 28 May 2014 17:21:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971429#comment-12971429 ] Tom Jenkinson commented on JBTM-2184: ------------------------------------- Its only the stuff that is activated at runtime we need. So the org.jfree would only activate if you used the stats stuff and the hornetq if you used the HQ object store. I am assuming that the issue is that narayana-jta does not uber jar include the spi as its external to the project, hence making the spi available in maven central is the right thing to do (plus the example should be updated to include it as a provided dependency). It looks like something changed with the spi syncing as version 6 is in maven central: http://search.maven.org/#search%7Cga%7C1%7Cjboss-transaction-spi > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Paul Robinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed May 28 17:21:15 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 28 May 2014 17:21:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971429#comment-12971429 ] Tom Jenkinson edited comment on JBTM-2184 at 5/28/14 5:20 PM: -------------------------------------------------------------- Its only the stuff that is activated at runtime we need. So the org.jfree would only trip if you used the stats stuff and the hornetq if you used the HQ object store. I am assuming that the issue is that narayana-jta does not uber jar include the spi as its external to the project, hence making the spi available in maven central is the right thing to do (plus the example should be updated to include it as a provided dependency). It looks like something changed with the spi syncing as version 6 is in maven central: http://search.maven.org/#search%7Cga%7C1%7Cjboss-transaction-spi was (Author: tomjenkinson): Its only the stuff that is activated at runtime we need. So the org.jfree would only activate if you used the stats stuff and the hornetq if you used the HQ object store. I am assuming that the issue is that narayana-jta does not uber jar include the spi as its external to the project, hence making the spi available in maven central is the right thing to do (plus the example should be updated to include it as a provided dependency). It looks like something changed with the spi syncing as version 6 is in maven central: http://search.maven.org/#search%7Cga%7C1%7Cjboss-transaction-spi > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Paul Robinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 07:07:15 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 29 May 2014 07:07:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2162) Change CMR commit failure message In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971584#comment-12971584 ] RH Bugzilla Integration commented on JBTM-2162: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1087726|https://bugzilla.redhat.com/show_bug.cgi?id=1087726] from MODIFIED to ON_QA > Change CMR commit failure message > --------------------------------- > > Key: JBTM-2162 > URL: https://issues.jboss.org/browse/JBTM-2162 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 4.17.20 > > > If a transaction containing an XA and a CMR resource is committed and the CMR resource fails the commit then the warning message mentions onePhaseCommit. Even though the CMR is in reality a one phase resource the message can be confusing. > Please change the message to something more generic. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 07:09:15 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 29 May 2014 07:09:15 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971586#comment-12971586 ] RH Bugzilla Integration commented on JBTM-2159: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1089251|https://bugzilla.redhat.com/show_bug.cgi?id=1089251] from MODIFIED to ON_QA > 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 12: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.(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 15: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.(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.(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) From issues at jboss.org Thu May 29 07:09:16 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 29 May 2014 07:09:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971587#comment-12971587 ] RH Bugzilla Integration commented on JBTM-2121: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1027126|https://bugzilla.redhat.com/show_bug.cgi?id=1027126] from MODIFIED to ON_QA > 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) From issues at jboss.org Thu May 29 07:09:16 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 29 May 2014 07:09:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971588#comment-12971588 ] RH Bugzilla Integration commented on JBTM-2165: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1095413|https://bugzilla.redhat.com/show_bug.cgi?id=1095413] from MODIFIED to ON_QA > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu May 29 07:47:16 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 29 May 2014 07:47:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971606#comment-12971606 ] RH Bugzilla Integration commented on JBTM-2121: ----------------------------------------------- Hayk Hovsepyan changed the Status of [bug 1027126|https://bugzilla.redhat.com/show_bug.cgi?id=1027126] from ON_QA to VERIFIED > 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) From issues at jboss.org Fri May 30 06:35:16 2014 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 30 May 2014 06:35:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971913#comment-12971913 ] Tom Jenkinson commented on JBTM-2184: ------------------------------------- The artifact is now synced so we can add the dependency in the quickstarts on org.jboss.jboss-transaction-spi:7.1.0.Final > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Paul Robinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri May 30 09:03:16 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 30 May 2014 09:03:16 -0400 (EDT) Subject: [jbossts-issues] [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 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971958#comment-12971958 ] RH Bugzilla Integration commented on JBTM-2159: ----------------------------------------------- Miroslav Novak changed the Status of [bug 1089251|https://bugzilla.redhat.com/show_bug.cgi?id=1089251] from ON_QA to VERIFIED > 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 12: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.(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 15: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.(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.(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) From issues at jboss.org Fri May 30 11:23:15 2014 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 30 May 2014 11:23:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2139) update the narayana-quickstart jobs to make sure the txfooapp example is working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2139: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/124 > update the narayana-quickstart jobs to make sure the txfooapp example is working > -------------------------------------------------------------------------------- > > Key: JBTM-2139 > URL: https://issues.jboss.org/browse/JBTM-2139 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.2 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)