From issues at jboss.org Wed Jun 1 08:27:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 1 Jun 2016 08:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2679: ---------------------------------- Affects Version/s: 5.3.2.Final > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 1 08:27:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 1 Jun 2016 08:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2679: ---------------------------------- Description: Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. Created assembly plugin jira: https://issues.apache.org/jira/browse/MASSEMBLY-809 was:Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. > Created assembly plugin jira: https://issues.apache.org/jira/browse/MASSEMBLY-809 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 1 08:28:00 2016 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 1 Jun 2016 08:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246220#comment-13246220 ] Ondra Chaloupka commented on JBTM-2679: --------------------------------------- I've created assembly plugin jira here: https://issues.apache.org/jira/browse/MASSEMBLY-809 > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. > Created assembly plugin jira: https://issues.apache.org/jira/browse/MASSEMBLY-809 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 1 10:13:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 1 Jun 2016 10:13:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246350#comment-13246350 ] RH Bugzilla Integration commented on JBTM-2583: ----------------------------------------------- Dmitrii Tikhomirov changed the Status of [bug 1310603|https://bugzilla.redhat.com/show_bug.cgi?id=1310603] from ASSIGNED to MODIFIED > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 1 16:06:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 1 Jun 2016 16:06:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2583: --------------------------------- > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 1 16:07:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 1 Jun 2016 16:07:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: 5.2.17.Final 4.17.34 > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.34, 5.2.17.Final, 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 1 16:07:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 1 Jun 2016 16:07:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2583. ------------------------------- Resolution: Done > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final, 5.2.17.Final, 4.17.34 > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:56:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:56:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2675. --------------------------------- > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 5.3.3.Final > > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:56:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:56:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2670) Update raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2670. --------------------------------- > Update raw-xts-api-demo quickstart > ---------------------------------- > > Key: JBTM-2670 > URL: https://issues.jboss.org/browse/JBTM-2670 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.3.3.Final > > > raw-xts-api-demo quickstart has out of date readme and dependencies. It doesn't work with current WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:56:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:56:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2663) Upgrade to jboss-connector-api_1.7_spec 1.0.0.Final in jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2663. --------------------------------- > Upgrade to jboss-connector-api_1.7_spec 1.0.0.Final in jboss-transaction-spi > ---------------------------------------------------------------------------- > > Key: JBTM-2663 > URL: https://issues.jboss.org/browse/JBTM-2663 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.3.3.Final > > > It includes the JTA 1.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:56:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:56:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2657) Missing narayana-osgi-jta artifact with the release profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2657. --------------------------------- > Missing narayana-osgi-jta artifact with the release profile > ----------------------------------------------------------- > > Key: JBTM-2657 > URL: https://issues.jboss.org/browse/JBTM-2657 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Labels: JTA, OSGI > Fix For: 5.3.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:56:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:56:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2655) QA suite failure: TestGroup_txcore_recovery (JDBC store) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2655. --------------------------------- > QA suite failure: TestGroup_txcore_recovery (JDBC store) > -------------------------------------------------------- > > Key: JBTM-2655 > URL: https://issues.jboss.org/browse/JBTM-2655 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.3.3.Final > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-jdbcobjectstore/191/DB_TYPE=db2,jdk=jdk8.latest,slave=linux/consoleFull -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2647) Extend compensations BAControler to allow enlistment of handlers by instance In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2647. --------------------------------- > Extend compensations BAControler to allow enlistment of handlers by instance > ---------------------------------------------------------------------------- > > Key: JBTM-2647 > URL: https://issues.jboss.org/browse/JBTM-2647 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.3.3.Final > > > Currently BAControler allows enlistment of handler only by class. It later creates instances using those classes when finishing the compensating transaction. Because of that it should be easy to allow enlisting of instances. This would allow using labdas when implementing handlers. Also instance could carry some extra information needed to compensate the transaction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2648) Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2648. --------------------------------- > Failing .Narayana qa testcase crashrecovery12 method CrashRecovery12_Test03 when journal object store is used > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2648 > URL: https://issues.jboss.org/browse/JBTM-2648 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.14.Final > Reporter: Ondra Chaloupka > Assignee: Gytis Trikleris > Fix For: 5.3.3.Final > > Attachments: TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12.txt, testoutput.zip > > > When using journal object store (amq) then we experience failues of test {{crashrecovery12 CrashRecovery12_Test03}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2641) Add localisation to JMS module warnings In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2641. --------------------------------- > Add localisation to JMS module warnings > --------------------------------------- > > Key: JBTM-2641 > URL: https://issues.jboss.org/browse/JBTM-2641 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.3.3.Final > > > Warning messages in JMS modules should be localised same as other modules in ArjunaJTA. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2634) Create Narayana Spring Boot starter quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2634. --------------------------------- > Create Narayana Spring Boot starter quickstart > ---------------------------------------------- > > Key: JBTM-2634 > URL: https://issues.jboss.org/browse/JBTM-2634 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.3.3.Final > > > Create a demonstrator application for Narayana Spring Boot starter before raising pull request to Spring. This would allow to make a better review of the Narayana Spring Boot integration on the forum. > Quickstart should have a simple example of JTA and crash recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2619. --------------------------------- > Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) > -------------------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.3.3.Final > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2606) Create Spring Boot starter for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2606. --------------------------------- > Create Spring Boot starter for Narayana > --------------------------------------- > > Key: JBTM-2606 > URL: https://issues.jboss.org/browse/JBTM-2606 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.3.3.Final > > > Spring provides a bunch of Spring Boot starter artefacts in order to make integration of certain projects easier. We should investigate having one for Narayana. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2678) @TxLogged annotation does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2678: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > @TxLogged annotation does not work > ---------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa58158c5e3ac6a#diff-a01554d0172e1da7703c5134820edb6aL124 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2676: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2671) TXBridge quickstart execution steps are inaccurate In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2671: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > TXBridge quickstart execution steps are inaccurate > -------------------------------------------------- > > Key: JBTM-2671 > URL: https://issues.jboss.org/browse/JBTM-2671 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, TxBridge, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Execution steps for both wsat-jta-multi_hop and wsat-jta-multi_service quickstarts tells to start WildFly in one console and then execute the test with managed Arquillian container. Which is obviously wrong. > We shouldn't suggest to start the container manually, but only use the managed container. > Also, it might be good to not redirect output to the file, but instead print it directly and use egrep as showed in the current execution steps. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2673) ThreadUtil getThreadId(Thread) ignores argument In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2673: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > ThreadUtil getThreadId(Thread) ignores argument > ----------------------------------------------- > > Key: JBTM-2673 > URL: https://issues.jboss.org/browse/JBTM-2673 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > During investigation of https://developer.jboss.org/thread/269784?start=15&tstart=0 it was observed that the ThreadUtil implementation does not use the Thread argument and simply uses a ThreadLocal: > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/utils/ThreadUtil.java#L51 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2669) Refactor "impl" package in compensations module to "internal" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2669: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Refactor "impl" package in compensations module to "internal" > ------------------------------------------------------------- > > Key: JBTM-2669 > URL: https://issues.jboss.org/browse/JBTM-2669 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2667) JDBC Connection leak with Postgres In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2667: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > JDBC Connection leak with Postgres > ---------------------------------- > > Key: JBTM-2667 > URL: https://issues.jboss.org/browse/JBTM-2667 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Assignee: Tom Jenkinson > Fix For: 5.next > > > When using Narayana's JDBC TransactionalDriver with a Postgres XA datasource, the connections are never closed. > The problem can be workarounded by adding a modifier : > {code:java} > ModifierFactory.putModifier ("postgresql native driver", -1, -1, PsqlConnectionModifier.class.getName()); > {code} > With a modifier, the close method is called on the XAConnection object, with no modifier it's called on the Connection object. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2668) Entity manager does not join transaction properly in JTA and Hibernate quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2668: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Entity manager does not join transaction properly in JTA and Hibernate quickstart > --------------------------------------------------------------------------------- > > Key: JBTM-2668 > URL: https://issues.jboss.org/browse/JBTM-2668 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > To reproduce begin transaction at the start of TestCase.testJpa method and roll it back just before assertion. During the abort in BasicAction pending list is empty and no resources are rolled back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2665) Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2665: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release > ------------------------------------------------------------------------------ > > Key: JBTM-2665 > URL: https://issues.jboss.org/browse/JBTM-2665 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.3.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The OSGI build depends on an upgrade of the jboss-transacton-spi (JBTM-2663) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2662) Export org.jboss.tm, has 1, private references [org.jboss.logging] In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2662: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Export org.jboss.tm, has 1, private references [org.jboss.logging] > -------------------------------------------------------------------- > > Key: JBTM-2662 > URL: https://issues.jboss.org/browse/JBTM-2662 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2660) multiple jars provide the same package:javax/transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2660: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > multiple jars provide the same package:javax/transaction > -------------------------------------------------------- > > Key: JBTM-2660 > URL: https://issues.jboss.org/browse/JBTM-2660 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Split package, multiple jars provide the same package:javax/transaction > Use Import/Export Package directive -split-package:=(merge-first|merge-last|error|first) to get rid of this warning > Package found in [Jar:jboss-transaction-api_1.2_spec, Jar:jboss-transaction-api_1.1_spec] > Class path [Jar:., Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:jbosgi-metadata, Jar:jboss-transaction-api_1.2_spec, Jar:jta, Jar:common, Jar:arjuna, Jar:jconsole, Jar:jboss-transaction-spi, Jar:jboss-connector-api_1.5_spec, Jar:jboss-transaction-api_1.1_spec, Jar:narayana-jts-integration, Jar:jboss-logging, Jar:artemis-journal, Jar:artemis-commons, Jar:jboss-logmanager, Jar:netty-all, Jar:commons-beanutils, Jar:commons-collections, Jar:guava, Jar:artemis-native, Jar:spring-tx, Jar:aopalliance, Jar:spring-aop, Jar:spring-asm, Jar:spring-beans, Jar:spring-context, Jar:spring-expression, Jar:spring-core, Jar:commons-logging] -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2661) Unknown directive cardinality: in Require-Capability In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2661: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Unknown directive cardinality: in Require-Capability > ---------------------------------------------------- > > Key: JBTM-2661 > URL: https://issues.jboss.org/browse/JBTM-2661 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Unknown directive cardinality: in Require-Capability, allowed directives are effective:,resolution:,filter:, and 'x-*'. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2659) narayana-osgi-jta build bundle warings In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2659: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > narayana-osgi-jta build bundle warings > -------------------------------------- > > Key: JBTM-2659 > URL: https://issues.jboss.org/browse/JBTM-2659 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > There are three warning when building the bundle. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2656) XATerminatorImple#recover could return an empty array in preference to null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2656: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > XATerminatorImple#recover could return an empty array in preference to null > --------------------------------------------------------------------------- > > Key: JBTM-2656 > URL: https://issues.jboss.org/browse/JBTM-2656 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.3.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > The javadoc (http://docs.oracle.com/javaee/7/api/javax/resource/spi/XATerminator.html#recover-int-) for the XATerminator recover > method says the resource manager should return zero or more XIDs or throw an exception but our implementation of it returns null if there are no in doubt Xids. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2624: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2650) Remove typo from BAControler interface and its implementations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2650. --------------------------------- > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: JBTM-2650 > URL: https://issues.jboss.org/browse/JBTM-2650 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.3.3.Final > > > Fix typos in BAControler, LocalBAControler, and RemoteBAControler names. Also variables when those classes are used also have typos. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2652) Include STM javadocs on narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2652: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Include STM javadocs on narayana.io > ----------------------------------- > > Key: JBTM-2652 > URL: https://issues.jboss.org/browse/JBTM-2652 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation, STM > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Should be part of http://narayana.io/docs/api/index.html -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2646) Include a quickstart showing a command line equivalent of the wildfly transaction console In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2646: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Include a quickstart showing a command line equivalent of the wildfly transaction console > ----------------------------------------------------------------------------------------- > > Key: JBTM-2646 > URL: https://issues.jboss.org/browse/JBTM-2646 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tooling > Affects Versions: 5.3.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Provide a standalone tool (in the form of a quickstart) that duplicates the functionality of the wildfly transactions console. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2623) Check Glassfish-to-Narayana interoperability (via JTS). In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2623: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Check Glassfish-to-Narayana interoperability (via JTS). > ------------------------------------------------------- > > Key: JBTM-2623 > URL: https://issues.jboss.org/browse/JBTM-2623 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > This task facilitates the resolution of JBTM-223 Check WL-to-JBossTS interoperability (via JTS). > Whilst developing a test for recovery with WebLogic I was unable to make progress due to issue \[1\] (basically registering resources for recovery fails). Checking recovery using glassfish may be easier since the source code is readily available and may help with figuring out the correct solution with WL. > \[1\] According to [https://docs.oracle.com/cd/E12839_01/web.1111/e13731/jtatxexp.htm#WLJTA279] > XA resources can be registered for recovery via a singleton bean that runs at start up and registers them with the WL transaction manager. When I do this I get the exception as shown: > {quote} > javax.transaction.SystemException: Resource 'Dummy'can be registered only in a server process > at org.glassfish.transaction.TransactionManagerImplCommon.registerStaticResource(TransactionManagerImplCommon.java:695) > at org.jboss.narayana.RecoveryBean.register(RecoveryBean.java:61) > at org.jboss.narayana.RecoveryBean.init(RecoveryBean.java:30) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:377) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethods(Jsr250Metadata.java:352) > at com.oracle.pitchfork.intercept.InterceptionMetadata.invokeLifecycleMethods(InterceptionMetadata.java:399) > at weblogic.ejb.container.injection.EjbComponentCreatorImpl.invokePostConstruct(EjbComponentCreatorImpl.java:55) > at weblogic.ejb.container.manager.SingletonSessionManager.constructAndInitBean(SingletonSessionManager.java:330) > at weblogic.ejb.container.manager.SingletonSessionManager.access$300(SingletonSessionManager.java:62) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.doActualInit(SingletonSessionManager.java:753) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.initInternal(SingletonSessionManager.java:701) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.init(SingletonSessionManager.java:588) > at weblogic.ejb.container.manager.SingletonSessionManager.init(SingletonSessionManager.java:255) > at weblogic.ejb.container.manager.SingletonSessionManager.perhapsInit(SingletonSessionManager.java:251) > at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:968) > at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:597) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138) > at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:216) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:211) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:73) > at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24) > at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258) > at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48) > at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) > at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:226) > at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:418) > at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) > at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200) > at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) > at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240) > at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) > at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) > at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:210) > at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:118) > at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:78) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1017) > at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:388) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:430) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:606) > at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:77) > at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:231) > at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:254) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:413) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1162) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1147) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:263) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2632) Allow the setting of an initial delay in PeriodRecovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2632: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Allow the setting of an initial delay in PeriodRecovery > ------------------------------------------------------- > > Key: JBTM-2632 > URL: https://issues.jboss.org/browse/JBTM-2632 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Matthew Robson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently Periodic Recovery kicks off at the same interval on every server. As a domain mode cluster grows in size, this leads to significant contention in the DB, especially for RAC implementations. Completion time goes from milliseconds with 1 server to 20+ seconds with 20+ servers. > In an effort to avoid this, an offset the initial start of Periodic Recovery could be provided for the nodes in the cluster. > Periodic Recovery currently leverages 2 properties: > > > > > The proposal would be to add a 3rd property, 'RecoveryEnvironmentBean.periodicRecoveryInitilizationOffset' which, when set, would be used for each node. If not set, it would default to current behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:03 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2622: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Implement possible new compensations api > ---------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:04 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2605: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:04 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2571) Enable code coverage for XTS crash recovery tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2571: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Enable code coverage for XTS crash recovery tests > ------------------------------------------------- > > Key: JBTM-2571 > URL: https://issues.jboss.org/browse/JBTM-2571 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > Code coverage data is not collected during the XTS crash recovery tests execution. Currently this seems to be blocked by [1], [2], and [3]. > [1] https://community.jboss.org/message/817252 > [2] https://issues.jboss.org/browse/ARQ-1014 > [3] https://issues.jboss.org/browse/ARQ-918 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:04 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2553: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:04 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2542: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Migrate performance tests to the performance repo > ------------------------------------------------- > > Key: JBTM-2542 > URL: https://issues.jboss.org/browse/JBTM-2542 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Attachments: config.xml, eap-cmp-config.xml > > > We still have lots of performance related unit tests that need migrating: > rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceDefaultUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceVolatileUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceVolatileUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceDefaultUnitTest.java > ArjunaJTA/jta/tests/classes/com/hp/mwtests/ts/jta/commitmarkable/PerformanceTestCommitMarkableResource.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance1.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance2.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance4.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance3.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance1.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance2.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance3.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/PerfHammer.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/GridWorker.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/local/synchronizations/Performance.java > ArjunaJTA/jta/tests/classes/io/narayana/perf/product/Product.java > ArjunaJTA/jta/tests/classes/io/narayana/perf/product/ProductWorker.java -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:04 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2498: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:04 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2480: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:04 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2458) Think of the possibility to improve Compensations API with lambdas In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2458: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Think of the possibility to improve Compensations API with lambdas > ------------------------------------------------------------------ > > Key: JBTM-2458 > URL: https://issues.jboss.org/browse/JBTM-2458 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Emmanuel suggested to reduce verbosity in Compensations API by making it possible to use lambdas for handler implementation. > We should try to think of the best API changes to introduce that. > We could rewrite MongoDB quickstart to make it easier to visualise the difference. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:05 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2206) Use synchronized HashMaps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2206: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Use synchronized HashMaps > ------------------------- > > Key: JBTM-2206 > URL: https://issues.jboss.org/browse/JBTM-2206 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Transaction Core > Reporter: Jesper Pedersen > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Change usage of Hashtable into synchronized HashMap's instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:05 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2203) Remove ReentrantLock from StateManager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2203: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Remove ReentrantLock from StateManager > -------------------------------------- > > Key: JBTM-2203 > URL: https://issues.jboss.org/browse/JBTM-2203 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Remove unused lock from StateManager, and add the access methods to LockManager instead -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:05 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2115) Not all classes are under code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2115: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:05 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-1804: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:05 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-1107: ---------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Compensations > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers would be invoked in case of the system crash. > In addition, @CompensationScoped beans should be available during the recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 2 09:57:05 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 2 Jun 2016 09:57:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS). In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-223: --------------------------------- Fix Version/s: 5.next (was: 5.3.3.Final) > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 3 04:18:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 3 Jun 2016 04:18:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2683) The txfooapp quickstart segment fault In-Reply-To: References: Message-ID: Amos Feng created JBTM-2683: ------------------------------- Summary: The txfooapp quickstart segment fault Key: JBTM-2683 URL: https://issues.jboss.org/browse/JBTM-2683 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie, Demonstrator Reporter: Amos Feng Assignee: Amos Feng Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Jun 4 07:34:00 2016 From: issues at jboss.org (Abhijeet Kumar (JIRA)) Date: Sat, 4 Jun 2016 07:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2684) Connection pooling for JBossTS Narayana In-Reply-To: References: Message-ID: Abhijeet Kumar created JBTM-2684: ------------------------------------ Summary: Connection pooling for JBossTS Narayana Key: JBTM-2684 URL: https://issues.jboss.org/browse/JBTM-2684 Project: JBoss Transaction Manager Issue Type: Enhancement Components: JTA Affects Versions: 5.2.9.Final Reporter: Abhijeet Kumar Hi, I'm using JBossTS (Narayana) version 5.2.9 Final. There is no supports for connection pooling through the TransactionDriver. Establishing new physical connection for every transaction will slow down my production service. Can you please guide me to develop a custom wrapper around the TransactionalDriver of Narayana? I'm using Apache Tomcat JDBC 8 for connection pooling. I'm also using MysQL as DBServer and MySQLXADataSource as the XADatasource for the TransactionalDriver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 05:03:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 6 Jun 2016 05:03:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2668) Entity manager does not join transaction properly in JTA and Hibernate quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2668: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Entity manager does not join transaction properly in JTA and Hibernate quickstart > --------------------------------------------------------------------------------- > > Key: JBTM-2668 > URL: https://issues.jboss.org/browse/JBTM-2668 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > To reproduce begin transaction at the start of TestCase.testJpa method and roll it back just before assertion. During the abort in BasicAction pending list is empty and no resources are rolled back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 07:05:10 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jun 2016 07:05:10 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2621) Tests that rely on the old perf benchmark harness need porting to use JMH In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1018 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Tests that rely on the old perf benchmark harness need porting to use JMH > ------------------------------------------------------------------------- > > Key: JBTM-2621 > URL: https://issues.jboss.org/browse/JBTM-2621 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > The relevant tests are: > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance1 > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance3 > if there are no others then once ported the old performance benchmark harness can be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 07:28:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jun 2016 07:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2684) Connection pooling for JBossTS Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2684: -------------------------------- Forum Reference: https://developer.jboss.org/message/957369?et=watches.email.thread#957369 > Connection pooling for JBossTS Narayana > --------------------------------------- > > Key: JBTM-2684 > URL: https://issues.jboss.org/browse/JBTM-2684 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.2.9.Final > Reporter: Abhijeet Kumar > > Hi, > I'm using JBossTS (Narayana) version 5.2.9 Final. There is no supports for connection pooling through the TransactionDriver. Establishing new physical connection for every transaction will slow down my production service. > Can you please guide me to develop a custom wrapper around the TransactionalDriver of Narayana? > I'm using Apache Tomcat JDBC 8 for connection pooling. I'm also using MysQL as DBServer and MySQLXADataSource as the XADatasource for the TransactionalDriver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 07:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jun 2016 07:30:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2684) Connection pooling for JBossTS Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2684. ------------------------------- Resolution: Won't Fix As discussed on the forum, this is by design. If you have a pull request to address this we can reopen this issue but its not something we are looking at implementing at this point in time so I will close it for now. > Connection pooling for JBossTS Narayana > --------------------------------------- > > Key: JBTM-2684 > URL: https://issues.jboss.org/browse/JBTM-2684 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.2.9.Final > Reporter: Abhijeet Kumar > > Hi, > I'm using JBossTS (Narayana) version 5.2.9 Final. There is no supports for connection pooling through the TransactionDriver. Establishing new physical connection for every transaction will slow down my production service. > Can you please guide me to develop a custom wrapper around the TransactionalDriver of Narayana? > I'm using Apache Tomcat JDBC 8 for connection pooling. I'm also using MysQL as DBServer and MySQLXADataSource as the XADatasource for the TransactionalDriver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 07:33:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jun 2016 07:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2674) JTA does not set transaction timeout for XAResource for propagated transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2674: ----------------------------------- Assignee: David Lloyd (was: Tom Jenkinson) > JTA does not set transaction timeout for XAResource for propagated transactions > ------------------------------------------------------------------------------- > > Key: JBTM-2674 > URL: https://issues.jboss.org/browse/JBTM-2674 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Ondra Chaloupka > Assignee: David Lloyd > > I can see a fact that transaction timeout is not provided by subordinate transaction when passed by ejb remote call when JTA transaction are used. > Even when transaction timeout is defined (it could be seen that timeout is used when xaresources is used on client) the server where transaction is propagated shows xa resources using the default timeou value. > Client server (caller) - timeout is _6 seconds_ > {code} > 2016-05-19 11:50:51,461 TRACE [com.arjuna.ats.jta] (default task-18) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:483, xid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, timeout:6, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-483 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 7b44816f >, record id=0:ffff7f000001:57a802d4:573d8c57:21 > {code} > Server (callee) - uses timeout _0 seconds_ > {code} > 2016-05-19 11:50:39,374 TRACE [com.arjuna.ats.jta] (default task-12) XAResourceRecord.topLevelPrepare for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:502, xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, timeout:0, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-502 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 4f35ed3f >, record id=0:ffff7f000001:3b603de1:573d8c5f:18 > {code} > Scenario that I'm running is > # enlist jms xa resource on client > # call to second server, it means enlist ejb remoting xa resource to transaction > # enlist test xa on server > # enlist jms xa resource on server > # enlist test xa on client > # starting 2PC > # prepare jms xa resource on server > # prepare ejb remoting xa resource on server > # prepare test xa resource on client > # transaction timeout is hit > # if underlying jms resource timeouts then XAResource.prepare call fails with XAER_NOTA and the whole transaction is rolled back > # > _(attaching server.log files for EAP 7.0.0/Narayana 5.2.16.Final where jbossts is caller and jbossts2 is callee)_ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 07:55:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jun 2016 07:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248227#comment-13248227 ] Tom Jenkinson commented on JBTM-2677: ------------------------------------- public final int doPhase2Abort () { if (jtsLogger.logger.isTraceEnabled()) { jtsLogger.logger.trace("ServerTransaction::doPhase2Abort ( " + get_uid() + " )"); } /* * If the transaction has already terminated, then return the status. If * there hasn't been a heuristic outcome then we try to massage the result * to be consistent with what the caller expects: the fact that the * transaction is marked as committed during prepare without any problems means * that the intentions lists are zero so it's fine to say that it aborted instead. */ org.omg.CosTransactions.Status s = get_status(); if ((s == org.omg.CosTransactions.Status.StatusCommitted) || (s == org.omg.CosTransactions.Status.StatusRolledBack)) { int status = finalStatus(); switch (status) { case ActionStatus.COMMITTED: case ActionStatus.COMMITTING: case ActionStatus.ABORTED: case ActionStatus.ABORTING: return ActionStatus.ABORTED; default: return status; } } This was changed in https://issues.jboss.org/browse/JBTM-507. I have had a look at the mentioned particular test if we just return finalStatus it seems to still pass so I think the change may likely be safely reverted. Prototype: https://github.com/jbosstm/narayana/pull/1019 > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.next > > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 07:55:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jun 2016 07:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2677: -------------------------------- Fix Version/s: 5.next > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.next > > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 10:43:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jun 2016 10:43:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248401#comment-13248401 ] Tom Jenkinson commented on JBTM-2605: ------------------------------------- Is this done? > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 10:43:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jun 2016 10:43:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2605: ----------------------------------- Assignee: Gytis Trikleris > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 10:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jun 2016 10:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2458) Think of the possibility to improve Compensations API with lambdas In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248402#comment-13248402 ] Tom Jenkinson commented on JBTM-2458: ------------------------------------- Is this done? > Think of the possibility to improve Compensations API with lambdas > ------------------------------------------------------------------ > > Key: JBTM-2458 > URL: https://issues.jboss.org/browse/JBTM-2458 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Emmanuel suggested to reduce verbosity in Compensations API by making it possible to use lambdas for handler implementation. > We should try to think of the best API changes to introduce that. > We could rewrite MongoDB quickstart to make it easier to visualise the difference. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 03:12:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 7 Jun 2016 03:12:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248700#comment-13248700 ] Gytis Trikleris commented on JBTM-2605: --------------------------------------- I think that it is. Unless there were other requirements for just Spring integration other than a quickstart. > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 03:13:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 7 Jun 2016 03:13:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2622: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Implement possible new compensations api > ---------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 03:14:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 7 Jun 2016 03:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2458) Think of the possibility to improve Compensations API with lambdas In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris resolved JBTM-2458. ----------------------------------- Resolution: Done > Think of the possibility to improve Compensations API with lambdas > ------------------------------------------------------------------ > > Key: JBTM-2458 > URL: https://issues.jboss.org/browse/JBTM-2458 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Emmanuel suggested to reduce verbosity in Compensations API by making it possible to use lambdas for handler implementation. > We should try to think of the best API changes to introduce that. > We could rewrite MongoDB quickstart to make it easier to visualise the difference. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 06:01:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 7 Jun 2016 06:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Amos Feng created pull request #1020 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 06:14:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 7 Jun 2016 06:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2685: -------------------------------------- Summary: Check that narayana builds and runs using the Java SE 9 compiler Key: JBTM-2685 URL: https://issues.jboss.org/browse/JBTM-2685 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Affects Versions: 5.3.3.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 07:29:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jun 2016 07:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248863#comment-13248863 ] Tom Jenkinson commented on JBTM-2605: ------------------------------------- Lets mark this as resolved then > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 07:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jun 2016 07:30:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2605. --------------------------------- Resolution: Done > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 09:23:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 10 Jun 2016 09:23:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248227#comment-13248227 ] Tom Jenkinson edited comment on JBTM-2677 at 6/10/16 9:22 AM: -------------------------------------------------------------- public final int doPhase2Abort () { if (jtsLogger.logger.isTraceEnabled()) { jtsLogger.logger.trace("ServerTransaction::doPhase2Abort ( " + get_uid() + " )"); } /* * If the transaction has already terminated, then return the status. If * there hasn't been a heuristic outcome then we try to massage the result * to be consistent with what the caller expects: the fact that the * transaction is marked as committed during prepare without any problems means * that the intentions lists are zero so it's fine to say that it aborted instead. */ org.omg.CosTransactions.Status s = get_status(); if ((s == org.omg.CosTransactions.Status.StatusCommitted) || (s == org.omg.CosTransactions.Status.StatusRolledBack)) { int status = finalStatus(); switch (status) { case ActionStatus.COMMITTED: case ActionStatus.COMMITTING: case ActionStatus.ABORTED: case ActionStatus.ABORTING: return ActionStatus.ABORTED; default: return status; } } This was changed in https://issues.jboss.org/browse/JBTM-507. Prototype: https://github.com/jbosstm/narayana/pull/1019 was (Author: tomjenkinson): public final int doPhase2Abort () { if (jtsLogger.logger.isTraceEnabled()) { jtsLogger.logger.trace("ServerTransaction::doPhase2Abort ( " + get_uid() + " )"); } /* * If the transaction has already terminated, then return the status. If * there hasn't been a heuristic outcome then we try to massage the result * to be consistent with what the caller expects: the fact that the * transaction is marked as committed during prepare without any problems means * that the intentions lists are zero so it's fine to say that it aborted instead. */ org.omg.CosTransactions.Status s = get_status(); if ((s == org.omg.CosTransactions.Status.StatusCommitted) || (s == org.omg.CosTransactions.Status.StatusRolledBack)) { int status = finalStatus(); switch (status) { case ActionStatus.COMMITTED: case ActionStatus.COMMITTING: case ActionStatus.ABORTED: case ActionStatus.ABORTING: return ActionStatus.ABORTED; default: return status; } } This was changed in https://issues.jboss.org/browse/JBTM-507. I have had a look at the mentioned particular test if we just return finalStatus it seems to still pass so I think the change may likely be safely reverted. Prototype: https://github.com/jbosstm/narayana/pull/1019 > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.next > > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 09:29:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 10 Jun 2016 09:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248227#comment-13248227 ] Tom Jenkinson edited comment on JBTM-2677 at 6/10/16 9:28 AM: -------------------------------------------------------------- {code} public final int doPhase2Abort () { if (jtsLogger.logger.isTraceEnabled()) { jtsLogger.logger.trace("ServerTransaction::doPhase2Abort ( " + get_uid() + " )"); } /* * If the transaction has already terminated, then return the status. If * there hasn't been a heuristic outcome then we try to massage the result * to be consistent with what the caller expects: the fact that the * transaction is marked as committed during prepare without any problems means * that the intentions lists are zero so it's fine to say that it aborted instead. */ org.omg.CosTransactions.Status s = get_status(); if ((s == org.omg.CosTransactions.Status.StatusCommitted) || (s == org.omg.CosTransactions.Status.StatusRolledBack)) { int status = finalStatus(); switch (status) { case ActionStatus.COMMITTED: case ActionStatus.COMMITTING: case ActionStatus.ABORTED: case ActionStatus.ABORTING: return ActionStatus.ABORTED; default: return status; } } {code} This was changed in https://issues.jboss.org/browse/JBTM-507. Prototype: https://github.com/jbosstm/narayana/pull/1019 was (Author: tomjenkinson): public final int doPhase2Abort () { if (jtsLogger.logger.isTraceEnabled()) { jtsLogger.logger.trace("ServerTransaction::doPhase2Abort ( " + get_uid() + " )"); } /* * If the transaction has already terminated, then return the status. If * there hasn't been a heuristic outcome then we try to massage the result * to be consistent with what the caller expects: the fact that the * transaction is marked as committed during prepare without any problems means * that the intentions lists are zero so it's fine to say that it aborted instead. */ org.omg.CosTransactions.Status s = get_status(); if ((s == org.omg.CosTransactions.Status.StatusCommitted) || (s == org.omg.CosTransactions.Status.StatusRolledBack)) { int status = finalStatus(); switch (status) { case ActionStatus.COMMITTED: case ActionStatus.COMMITTING: case ActionStatus.ABORTED: case ActionStatus.ABORTING: return ActionStatus.ABORTED; default: return status; } } This was changed in https://issues.jboss.org/browse/JBTM-507. Prototype: https://github.com/jbosstm/narayana/pull/1019 > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.next > > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 10:59:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 10 Jun 2016 10:59:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248227#comment-13248227 ] Tom Jenkinson edited comment on JBTM-2677 at 6/10/16 10:58 AM: --------------------------------------------------------------- {code} public final int doPhase2Abort () { if (jtsLogger.logger.isTraceEnabled()) { jtsLogger.logger.trace("ServerTransaction::doPhase2Abort ( " + get_uid() + " )"); } /* * If the transaction has already terminated, then return the status. If * there hasn't been a heuristic outcome then we try to massage the result * to be consistent with what the caller expects: the fact that the * transaction is marked as committed during prepare without any problems means * that the intentions lists are zero so it's fine to say that it aborted instead. */ org.omg.CosTransactions.Status s = get_status(); if ((s == org.omg.CosTransactions.Status.StatusCommitted) || (s == org.omg.CosTransactions.Status.StatusRolledBack)) { int status = finalStatus(); switch (status) { case ActionStatus.COMMITTED: case ActionStatus.COMMITTING: case ActionStatus.ABORTED: case ActionStatus.ABORTING: return ActionStatus.ABORTED; default: return status; } } {code} This was changed in https://issues.jboss.org/browse/JBTM-507. was (Author: tomjenkinson): {code} public final int doPhase2Abort () { if (jtsLogger.logger.isTraceEnabled()) { jtsLogger.logger.trace("ServerTransaction::doPhase2Abort ( " + get_uid() + " )"); } /* * If the transaction has already terminated, then return the status. If * there hasn't been a heuristic outcome then we try to massage the result * to be consistent with what the caller expects: the fact that the * transaction is marked as committed during prepare without any problems means * that the intentions lists are zero so it's fine to say that it aborted instead. */ org.omg.CosTransactions.Status s = get_status(); if ((s == org.omg.CosTransactions.Status.StatusCommitted) || (s == org.omg.CosTransactions.Status.StatusRolledBack)) { int status = finalStatus(); switch (status) { case ActionStatus.COMMITTED: case ActionStatus.COMMITTING: case ActionStatus.ABORTED: case ActionStatus.ABORTING: return ActionStatus.ABORTED; default: return status; } } {code} This was changed in https://issues.jboss.org/browse/JBTM-507. Prototype: https://github.com/jbosstm/narayana/pull/1019 > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.next > > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 11:34:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 10 Jun 2016 11:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251025#comment-13251025 ] Tom Jenkinson commented on JBTM-2677: ------------------------------------- Please can you attach a trace log, I have trouble getting the test running. > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.next > > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 11:39:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 10 Jun 2016 11:39:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2677: -------------------------------- Comment: was deleted (was: Please can you attach a trace log, I have trouble getting the test running.) > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.next > > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 11:39:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 10 Jun 2016 11:39:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2677: -------------------------------- Comment: was deleted (was: I see the log on the JBEAP) > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.next > > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 11:39:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 10 Jun 2016 11:39:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251033#comment-13251033 ] Tom Jenkinson commented on JBTM-2677: ------------------------------------- I see the log on the JBEAP > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Fix For: 5.next > > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 13 03:24:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 13 Jun 2016 03:24:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2686) Introduce a Heuristic example in the karaf osgi-jta quickstart In-Reply-To: References: Message-ID: Amos Feng created JBTM-2686: ------------------------------- Summary: Introduce a Heuristic example in the karaf osgi-jta quickstart Key: JBTM-2686 URL: https://issues.jboss.org/browse/JBTM-2686 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Demonstrator Reporter: Amos Feng Assignee: Amos Feng This example could be used to show how to mange the transaction object stores with the karaf cli commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 13 03:28:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 13 Jun 2016 03:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2686) Introduce a Heuristic example in the karaf osgi-jta quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Amos Feng created pull request #171 in GitHub --------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Introduce a Heuristic example in the karaf osgi-jta quickstart > -------------------------------------------------------------- > > Key: JBTM-2686 > URL: https://issues.jboss.org/browse/JBTM-2686 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > This example could be used to show how to mange the transaction object stores with the karaf cli commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 13 11:23:01 2016 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Mon, 13 Jun 2016 11:23:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2687) There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests In-Reply-To: References: Message-ID: Daniel Simko created JBTM-2687: ---------------------------------- Summary: There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests Key: JBTM-2687 URL: https://issues.jboss.org/browse/JBTM-2687 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing, TxBridge Affects Versions: 5.3.3.Final Reporter: Daniel Simko Assignee: Gytis Trikleris Priority: Minor There are three times: {code}parameters.add(new BasicNameValuePair("isTransaction", "ture"));{code} instead of {code}parameters.add(new BasicNameValuePair("isTransaction", "true"));{code} which affect test behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 13 11:29:01 2016 From: issues at jboss.org (Anonymous (JIRA)) Date: Mon, 13 Jun 2016 11:29:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2687) There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Dan Simko created pull request #1021 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests > ------------------------------------------------------------------------------------- > > Key: JBTM-2687 > URL: https://issues.jboss.org/browse/JBTM-2687 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing, TxBridge > Affects Versions: 5.3.3.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > There are three times: > {code}parameters.add(new BasicNameValuePair("isTransaction", "ture"));{code} > instead of > {code}parameters.add(new BasicNameValuePair("isTransaction", "true"));{code} > which affect test behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 14 06:06:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 14 Jun 2016 06:06:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2679: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next 5.2.18.Final Resolution: Done > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next, 5.2.18.Final > > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. > Created assembly plugin jira: https://issues.apache.org/jira/browse/MASSEMBLY-809 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 14 06:07:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 14 Jun 2016 06:07:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252012#comment-13252012 ] Tom Jenkinson commented on JBTM-2679: ------------------------------------- Hi Ondra, the fix version is 5.next (in case we added a new feature too). I marked it resolved - thanks for the contribution! > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next, 5.2.18.Final > > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. > Created assembly plugin jira: https://issues.apache.org/jira/browse/MASSEMBLY-809 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 14 13:10:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 14 Jun 2016 13:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2688) Message was not delivered to the queue in Spring Boot QS In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2688: ------------------------------------- Summary: Message was not delivered to the queue in Spring Boot QS Key: JBTM-2688 URL: https://issues.jboss.org/browse/JBTM-2688 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.next {code} ------------------------------------------------------------------------------- Test set: org.jboss.narayana.quickstart.spring.QuickstartApplicationTests ------------------------------------------------------------------------------- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.443 sec <<< FAILURE! testCommit(org.jboss.narayana.quickstart.spring.QuickstartApplicationTests) Time elapsed: 2.43 sec <<< FAILURE! java.lang.AssertionError: Expected: a string containing "Message received: Created entry 'Test Value'" but: was " . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v1.4.0.M3) 2016-06-14 14:34:55.166 INFO 5790 --- [ main] o.j.n.q.spring.QuickstartApplication : Starting QuickstartApplication on jaime.eng.hst.ams2.redhat.com with PID 5790 (/home/hudson/workspace/btny-pulls-narayana-quickstart/spring/narayana-spring-boot/target/classes started by hudson in /home/hudson/workspace/btny-pulls-narayana-quickstart/spring/narayana-spring-boot) 2016-06-14 14:34:55.167 INFO 5790 --- [ main] o.j.n.q.spring.QuickstartApplication : No active profile set, falling back to default profiles: default 2016-06-14 14:34:55.170 INFO 5790 --- [ main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext at 1d0cdb6: startup date [Tue Jun 14 14:34:55 BST 2016]; root of context hierarchy 2016-06-14 14:34:55.655 INFO 5790 --- [ main] f.a.AutowiredAnnotationBeanPostProcessor : JSR-330 'javax.inject.Inject' annotation found and supported for autowiring 2016-06-14 14:34:55.787 INFO 5790 --- [ main] com.arjuna.ats.jbossatx : ARJUNA032010: JBossTS Recovery Service (tag: unknown) - JBoss Inc. 2016-06-14 14:34:55.787 INFO 5790 --- [ main] com.arjuna.ats.jbossatx : ARJUNA032013: Starting transaction recovery manager 2016-06-14 14:34:55.870 INFO 5790 --- [ main] o.s.t.jta.JtaTransactionManager : Using JTA UserTransaction: Transaction: unknown 2016-06-14 14:34:55.870 INFO 5790 --- [ main] o.s.t.jta.JtaTransactionManager : Using JTA TransactionManager: Transaction: unknown 2016-06-14 14:34:55.980 INFO 5790 --- [ main] j.LocalContainerEntityManagerFactoryBean : Building JPA container EntityManagerFactory for persistence unit 'default' 2016-06-14 14:34:55.981 INFO 5790 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [ name: default ...] 2016-06-14 14:34:55.995 INFO 5790 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.H2Dialect 2016-06-14 14:34:56.040 INFO 5790 --- [ main] o.h.t.schema.internal.SchemaCreatorImpl : HHH000476: Executing import script 'org.hibernate.tool.schema.internal.exec.ScriptSourceInputNonExistentImpl at 637cff' 2016-06-14 14:34:56.045 INFO 5790 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default' 2016-06-14 14:34:56.191 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/tmp/artemis-data/journal,bindingsDirectory=data/bindings,largeMessagesDirectory=data/largemessages,pagingDirectory=data/paging) 2016-06-14 14:34:56.192 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221045: libaio is not available, switching the configuration into NIO 2016-06-14 14:34:56.193 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE 2016-06-14 14:34:56.220 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221003: Trying to deploy queue jms.queue.quickstart-messages 2016-06-14 14:34:56.231 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221007: Server is now live 2016-06-14 14:34:56.231 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.2.0 [localhost, nodeID=c852656c-3234-11e6-94cb-52540027ba72] 2016-06-14 14:34:56.496 INFO 5790 --- [ main] o.s.j.e.a.AnnotationMBeanExporter : Registering beans for JMX exposure on startup 2016-06-14 14:34:56.503 INFO 5790 --- [ main] o.s.c.support.DefaultLifecycleProcessor : Starting beans in phase 2147483647 2016-06-14 14:34:56.509 INFO 5790 --- [ main] o.j.n.q.spring.QuickstartApplication : Started QuickstartApplication in 1.418 seconds (JVM running for 10.75) 2016-06-14 14:34:56.520 INFO 5790 --- [ main] o.h.h.i.QueryTranslatorFactoryInitiator : HHH000397: Using ASTQueryTranslatorFactory Entries at the start: [] Creating entry 'Test Value' Entries at the end: [Entry{id=1, value='Test Value'}] 2016-06-14 14:34:57.444 INFO 5790 --- [ main] s.c.a.AnnotationConfigApplicationContext : Closing org.springframework.context.annotation.AnnotationConfigApplicationContext at 1d0cdb6: startup date [Tue Jun 14 14:34:55 BST 2016]; root of context hierarchy 2016-06-14 14:34:57.446 INFO 5790 --- [ main] o.s.c.support.DefaultLifecycleProcessor : Stopping beans in phase 2147483647 2016-06-14 14:34:57.447 WARN 5790 --- [enerContainer-1] o.s.j.l.DefaultMessageListenerContainer : Rejecting received message because of the listener container having been stopped in the meantime: ActiveMQMessage[ID:c88ada9c-3234-11e6-94cb-52540027ba72]:PERSISTENT/ClientMessage[messageID=7, durable=true, address=jms.queue.quickstart-messages,userID=c88ada9c-3234-11e6-94cb-52540027ba72,properties=TypedProperties[__AMQ_CID=c8897b08-3234-11e6-94cb-52540027ba72]] 2016-06-14 14:34:57.456 INFO 5790 --- [ main] o.s.j.e.a.AnnotationMBeanExporter : Unregistering JMX-exposed beans on shutdown 2016-06-14 14:34:57.466 INFO 5790 --- [ main] org.apache.activemq.artemis.core.server : AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.2.0 [c852656c-3234-11e6-94cb-52540027ba72] stopped, uptime 1.275 seconds 2016-06-14 14:34:57.469 INFO 5790 --- [ main] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'default' 2016-06-14 14:34:57.470 INFO 5790 --- [ main] .SchemaDropperImpl$DelayedDropActionImpl : HHH000477: Starting delayed drop of schema as part of SessionFactory shut-down' 2016-06-14 14:34:57.488 INFO 5790 --- [ main] com.arjuna.ats.jbossatx : ARJUNA032014: Stopping transaction recovery manager " at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8) at org.jboss.narayana.quickstart.spring.QuickstartApplicationTests.testCommit(QuickstartApplicationTests.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.springframework.boot.test.rule.OutputCapture$1.evaluate(OutputCapture.java:61) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 15 03:54:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 15 Jun 2016 03:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2689) narayana-osgi-jta integration test does not work with the karaf 4.x In-Reply-To: References: Message-ID: Amos Feng created JBTM-2689: ------------------------------- Summary: narayana-osgi-jta integration test does not work with the karaf 4.x Key: JBTM-2689 URL: https://issues.jboss.org/browse/JBTM-2689 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Amos Feng Assignee: Amos Feng The aquillian-container-karaf-embedded only support the karaf 2.3.3 and we are using the shell command with 4.x Now we just disable the integration test temperately. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 15 03:57:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 15 Jun 2016 03:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2624: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 15 06:20:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 15 Jun 2016 06:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2686) Introduce a Heuristic example in the karaf osgi-jta quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252734#comment-13252734 ] Michael Musgrove commented on JBTM-2686: ---------------------------------------- Where is the link to the PR? > Introduce a Heuristic example in the karaf osgi-jta quickstart > -------------------------------------------------------------- > > Key: JBTM-2686 > URL: https://issues.jboss.org/browse/JBTM-2686 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > This example could be used to show how to mange the transaction object stores with the karaf cli commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 15 06:59:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 15 Jun 2016 06:59:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2690) Update "wiki-example" to use WildFly In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2690: ----------------------------------- Summary: Update "wiki-example" to use WildFly Key: JBTM-2690 URL: https://issues.jboss.org/browse/JBTM-2690 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Reporter: Tom Jenkinson Priority: Minor It is using AS6 so should be updated to use WildFly -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 15 07:07:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 15 Jun 2016 07:07:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2690) Update "wiki-example" to use WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252766#comment-13252766 ] Michael Musgrove commented on JBTM-2690: ---------------------------------------- We already have a distributed JTS quickstart for wildfly/EAP (https://github.com/wildfly/quickstart/tree/10.x/jts? / https://github.com/jboss-eap/quickstart/tree/master-eap6/jts > Update "wiki-example" to use WildFly > ------------------------------------ > > Key: JBTM-2690 > URL: https://issues.jboss.org/browse/JBTM-2690 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Priority: Minor > > It is using AS6 so should be updated to use WildFly -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 03:27:01 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 16 Jun 2016 03:27:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253242#comment-13253242 ] RH Bugzilla Integration commented on JBTM-2550: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1333245|https://bugzilla.redhat.com/show_bug.cgi?id=1333245] from MODIFIED to ON_QA > If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Affects Versions: 5.2.8.Final > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.33, 5.2.10.Final > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR > We can catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 03:28:02 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 16 Jun 2016 03:28:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253262#comment-13253262 ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1329142|https://bugzilla.redhat.com/show_bug.cgi?id=1329142] from MODIFIED to ON_QA > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 03:28:07 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 16 Jun 2016 03:28:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253275#comment-13253275 ] RH Bugzilla Integration commented on JBTM-2583: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1310603|https://bugzilla.redhat.com/show_bug.cgi?id=1310603] from MODIFIED to ON_QA > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.34, 5.2.17.Final, 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 04:47:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 16 Jun 2016 04:47:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253314#comment-13253314 ] Tom Jenkinson commented on JBTM-2676: ------------------------------------- Please can you add a test case? I wonder if my patch would help here: https://github.com/jbosstm/narayana/pull/1022 > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 04:54:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 16 Jun 2016 04:54:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253323#comment-13253323 ] Tom Jenkinson commented on JBTM-2676: ------------------------------------- Also, a stack trace would be great thanks > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 05:28:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 16 Jun 2016 05:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253360#comment-13253360 ] Gytis Trikleris commented on JBTM-2676: --------------------------------------- I can add a test case to the jdbc unit tests. But will have to @Ignore it for the CI. > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 05:36:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 16 Jun 2016 05:36:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253363#comment-13253363 ] Tom Jenkinson commented on JBTM-2676: ------------------------------------- Good plan, thanks > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 05:42:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 16 Jun 2016 05:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2691) Add jms module to narayana-* uber jars In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2691: ----------------------------------- Summary: Add jms module to narayana-* uber jars Key: JBTM-2691 URL: https://issues.jboss.org/browse/JBTM-2691 Project: JBoss Transaction Manager Issue Type: Task Reporter: Tom Jenkinson Assignee: Gytis Trikleris Fix For: 5.next This would match transactional driver (jdbc) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 05:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 16 Jun 2016 05:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2691) Add jms module to narayana-* uber jars In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2691: ----------------------------------- Assignee: Tom Jenkinson (was: Gytis Trikleris) > Add jms module to narayana-* uber jars > -------------------------------------- > > Key: JBTM-2691 > URL: https://issues.jboss.org/browse/JBTM-2691 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > This would match transactional driver (jdbc) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 05:54:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 16 Jun 2016 05:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2676 started by Gytis Trikleris. --------------------------------------------- > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 08:03:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 16 Jun 2016 08:03:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2691) Add jms module to narayana-* uber jars In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1023 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Add jms module to narayana-* uber jars > -------------------------------------- > > Key: JBTM-2691 > URL: https://issues.jboss.org/browse/JBTM-2691 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > This would match transactional driver (jdbc) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 08:48:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 16 Jun 2016 08:48:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #1024 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 16 08:49:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 16 Jun 2016 08:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2676: ---------------------------------- Status: Open (was: Pull Request Sent) This pull request is only to add a reproducible tests. It is not a resolution. > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 05:49:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 17 Jun 2016 05:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2676: -------------------------------- Description: Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. See new JTA and Hibernate standalone quickstart for reproduction. {code} 2016-06-15 02:21:07,413 [main] WARN com.arjuna.ats.jta - ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization at e4b6f47 with exception org.hibernate.exception.GenericJDBCException: Unable to release JDBC Connection at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47) at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:111) at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:97) at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:172) at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.afterTransaction(LogicalConnectionManagedImpl.java:135) at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransaction(JdbcCoordinatorImpl.java:290) at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransactionCompletion(JdbcCoordinatorImpl.java:490) at org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.afterCompletion(JtaTransactionCoordinatorImpl.java:345) at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorNonTrackingImpl.doAfterCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:60) at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorTrackingImpl.afterCompletion(SynchronizationCallbackCoordinatorTrackingImpl.java:72) at org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization.afterCompletion(RegisteredSynchronization.java:44) at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:542) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:473) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127) at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) at org.jboss.narayana.quickstart.jta.TestCase.testRollback(TestCase.java:145) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:241) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:75) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) Caused by: java.sql.SQLException: ARJUNA017020: Transaction is not active on the thread! at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1071) at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:166) ... 45 more {code} was: Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. See new JTA and Hibernate standalone quickstart for reproduction. > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. > {code} > 2016-06-15 02:21:07,413 [main] WARN com.arjuna.ats.jta - ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization at e4b6f47 with exception > org.hibernate.exception.GenericJDBCException: Unable to release JDBC Connection > at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:111) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:97) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:172) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.afterTransaction(LogicalConnectionManagedImpl.java:135) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransaction(JdbcCoordinatorImpl.java:290) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransactionCompletion(JdbcCoordinatorImpl.java:490) > at org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.afterCompletion(JtaTransactionCoordinatorImpl.java:345) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorNonTrackingImpl.doAfterCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:60) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorTrackingImpl.afterCompletion(SynchronizationCallbackCoordinatorTrackingImpl.java:72) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization.afterCompletion(RegisteredSynchronization.java:44) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:542) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:473) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127) > at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) > at org.jboss.narayana.quickstart.jta.TestCase.testRollback(TestCase.java:145) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:241) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:75) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > Caused by: java.sql.SQLException: ARJUNA017020: Transaction is not active on the thread! > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1071) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:166) > ... 45 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 05:50:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 17 Jun 2016 05:50:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253960#comment-13253960 ] Tom Jenkinson commented on JBTM-2676: ------------------------------------- @gytis is it valid to call connection.close in after completion? The check is to make sure the transaction is not accessed > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. > {code} > 2016-06-15 02:21:07,413 [main] WARN com.arjuna.ats.jta - ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization at e4b6f47 with exception > org.hibernate.exception.GenericJDBCException: Unable to release JDBC Connection > at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:111) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:97) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:172) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.afterTransaction(LogicalConnectionManagedImpl.java:135) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransaction(JdbcCoordinatorImpl.java:290) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransactionCompletion(JdbcCoordinatorImpl.java:490) > at org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.afterCompletion(JtaTransactionCoordinatorImpl.java:345) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorNonTrackingImpl.doAfterCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:60) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorTrackingImpl.afterCompletion(SynchronizationCallbackCoordinatorTrackingImpl.java:72) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization.afterCompletion(RegisteredSynchronization.java:44) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:542) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:473) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127) > at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) > at org.jboss.narayana.quickstart.jta.TestCase.testRollback(TestCase.java:145) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:241) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:75) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > Caused by: java.sql.SQLException: ARJUNA017020: Transaction is not active on the thread! > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1071) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:166) > ... 45 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 05:51:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 17 Jun 2016 05:51:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253961#comment-13253961 ] Tom Jenkinson commented on JBTM-2676: ------------------------------------- I think it has to be valid because otherwise HHH would not be able to release in a rollback situation. > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. > {code} > 2016-06-15 02:21:07,413 [main] WARN com.arjuna.ats.jta - ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization at e4b6f47 with exception > org.hibernate.exception.GenericJDBCException: Unable to release JDBC Connection > at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:111) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:97) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:172) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.afterTransaction(LogicalConnectionManagedImpl.java:135) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransaction(JdbcCoordinatorImpl.java:290) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransactionCompletion(JdbcCoordinatorImpl.java:490) > at org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.afterCompletion(JtaTransactionCoordinatorImpl.java:345) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorNonTrackingImpl.doAfterCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:60) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorTrackingImpl.afterCompletion(SynchronizationCallbackCoordinatorTrackingImpl.java:72) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization.afterCompletion(RegisteredSynchronization.java:44) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:542) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:473) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127) > at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) > at org.jboss.narayana.quickstart.jta.TestCase.testRollback(TestCase.java:145) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:241) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:75) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > Caused by: java.sql.SQLException: ARJUNA017020: Transaction is not active on the thread! > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1071) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:166) > ... 45 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 05:52:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 17 Jun 2016 05:52:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253963#comment-13253963 ] Tom Jenkinson commented on JBTM-2676: ------------------------------------- Did you try just removing the checkTransaction from isClosed in connectionImple? > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. > {code} > 2016-06-15 02:21:07,413 [main] WARN com.arjuna.ats.jta - ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization at e4b6f47 with exception > org.hibernate.exception.GenericJDBCException: Unable to release JDBC Connection > at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:111) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:97) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:172) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.afterTransaction(LogicalConnectionManagedImpl.java:135) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransaction(JdbcCoordinatorImpl.java:290) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransactionCompletion(JdbcCoordinatorImpl.java:490) > at org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.afterCompletion(JtaTransactionCoordinatorImpl.java:345) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorNonTrackingImpl.doAfterCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:60) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorTrackingImpl.afterCompletion(SynchronizationCallbackCoordinatorTrackingImpl.java:72) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization.afterCompletion(RegisteredSynchronization.java:44) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:542) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:473) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127) > at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) > at org.jboss.narayana.quickstart.jta.TestCase.testRollback(TestCase.java:145) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:241) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:75) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > Caused by: java.sql.SQLException: ARJUNA017020: Transaction is not active on the thread! > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1071) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:166) > ... 45 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 05:57:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 17 Jun 2016 05:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253966#comment-13253966 ] Tom Jenkinson commented on JBTM-2676: ------------------------------------- You will likely need to check the status of the transaction as being active before doing the stuff within https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/ConnectionImple.java#L327 > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. > {code} > 2016-06-15 02:21:07,413 [main] WARN com.arjuna.ats.jta - ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization at e4b6f47 with exception > org.hibernate.exception.GenericJDBCException: Unable to release JDBC Connection > at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:111) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:97) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:172) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.afterTransaction(LogicalConnectionManagedImpl.java:135) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransaction(JdbcCoordinatorImpl.java:290) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransactionCompletion(JdbcCoordinatorImpl.java:490) > at org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.afterCompletion(JtaTransactionCoordinatorImpl.java:345) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorNonTrackingImpl.doAfterCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:60) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorTrackingImpl.afterCompletion(SynchronizationCallbackCoordinatorTrackingImpl.java:72) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization.afterCompletion(RegisteredSynchronization.java:44) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:542) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:473) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127) > at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) > at org.jboss.narayana.quickstart.jta.TestCase.testRollback(TestCase.java:145) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:241) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:75) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > Caused by: java.sql.SQLException: ARJUNA017020: Transaction is not active on the thread! > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1071) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:166) > ... 45 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 05:58:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 17 Jun 2016 05:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253967#comment-13253967 ] Gytis Trikleris commented on JBTM-2676: --------------------------------------- There are a few issues currently. First of all isClosed will fail during afterCompletion. Secondly, delist will fail, but technically there is no point to delist at this stage, so we could only delist when transaction is active. Finally, we should ignore delayed close, because it's too late to register synchronization. > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. > {code} > 2016-06-15 02:21:07,413 [main] WARN com.arjuna.ats.jta - ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization at e4b6f47 with exception > org.hibernate.exception.GenericJDBCException: Unable to release JDBC Connection > at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:111) > at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:97) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:172) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.afterTransaction(LogicalConnectionManagedImpl.java:135) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransaction(JdbcCoordinatorImpl.java:290) > at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransactionCompletion(JdbcCoordinatorImpl.java:490) > at org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.afterCompletion(JtaTransactionCoordinatorImpl.java:345) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorNonTrackingImpl.doAfterCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:60) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorTrackingImpl.afterCompletion(SynchronizationCallbackCoordinatorTrackingImpl.java:72) > at org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization.afterCompletion(RegisteredSynchronization.java:44) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:542) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:473) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127) > at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143) > at org.jboss.narayana.quickstart.jta.TestCase.testRollback(TestCase.java:145) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:241) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:75) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > Caused by: java.sql.SQLException: ARJUNA017020: Transaction is not active on the thread! > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1071) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.releaseConnection(LogicalConnectionManagedImpl.java:166) > ... 45 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 12:36:00 2016 From: issues at jboss.org (Guillaume Nodet (JIRA)) Date: Fri, 17 Jun 2016 12:36:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: Guillaume Nodet created JBTM-2692: ------------------------------------- Summary: Narayana OSGi bundle is missing optional packages Key: JBTM-2692 URL: https://issues.jboss.org/browse/JBTM-2692 Project: JBoss Transaction Manager Issue Type: Feature Request Affects Versions: 5.3.3.Final Reporter: Guillaume Nodet The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. Patch below: {code} diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml index 87d32c5..cd68637 100644 --- a/osgi/jta/pom.xml +++ b/osgi/jta/pom.xml @@ -206,6 +206,9 @@ org.apache.felix.service.command, org.apache.karaf.shell.api.action, org.apache.karaf.shell.api.action.lifecycle, + javax.enterprise.util;resolution:=optional, + javax.interceptor;resolution:=optional + javax.enterprise.context;resolution:=optional true {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 12:55:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 17 Jun 2016 12:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2692: ----------------------------------- Assignee: Amos Feng > Narayana OSGi bundle is missing optional packages > ------------------------------------------------- > > Key: JBTM-2692 > URL: https://issues.jboss.org/browse/JBTM-2692 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Affects Versions: 5.3.3.Final > Reporter: Guillaume Nodet > Assignee: Amos Feng > Fix For: 5.next > > > The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. > Patch below: > {code} > diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml > index 87d32c5..cd68637 100644 > --- a/osgi/jta/pom.xml > +++ b/osgi/jta/pom.xml > @@ -206,6 +206,9 @@ > org.apache.felix.service.command, > org.apache.karaf.shell.api.action, > org.apache.karaf.shell.api.action.lifecycle, > + javax.enterprise.util;resolution:=optional, > + javax.interceptor;resolution:=optional > + javax.enterprise.context;resolution:=optional > > true > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 12:55:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 17 Jun 2016 12:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2692: -------------------------------- Fix Version/s: 5.next > Narayana OSGi bundle is missing optional packages > ------------------------------------------------- > > Key: JBTM-2692 > URL: https://issues.jboss.org/browse/JBTM-2692 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Affects Versions: 5.3.3.Final > Reporter: Guillaume Nodet > Assignee: Amos Feng > Fix For: 5.next > > > The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. > Patch below: > {code} > diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml > index 87d32c5..cd68637 100644 > --- a/osgi/jta/pom.xml > +++ b/osgi/jta/pom.xml > @@ -206,6 +206,9 @@ > org.apache.felix.service.command, > org.apache.karaf.shell.api.action, > org.apache.karaf.shell.api.action.lifecycle, > + javax.enterprise.util;resolution:=optional, > + javax.interceptor;resolution:=optional > + javax.enterprise.context;resolution:=optional > > true > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 12:55:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 17 Jun 2016 12:55:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2692: -------------------------------- Priority: Blocker (was: Major) > Narayana OSGi bundle is missing optional packages > ------------------------------------------------- > > Key: JBTM-2692 > URL: https://issues.jboss.org/browse/JBTM-2692 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Affects Versions: 5.3.3.Final > Reporter: Guillaume Nodet > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. > Patch below: > {code} > diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml > index 87d32c5..cd68637 100644 > --- a/osgi/jta/pom.xml > +++ b/osgi/jta/pom.xml > @@ -206,6 +206,9 @@ > org.apache.felix.service.command, > org.apache.karaf.shell.api.action, > org.apache.karaf.shell.api.action.lifecycle, > + javax.enterprise.util;resolution:=optional, > + javax.interceptor;resolution:=optional > + javax.enterprise.context;resolution:=optional > > true > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 12:56:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 17 Jun 2016 12:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254246#comment-13254246 ] Tom Jenkinson commented on JBTM-2692: ------------------------------------- Can I just check, we just need to add the lines you mention above? > Narayana OSGi bundle is missing optional packages > ------------------------------------------------- > > Key: JBTM-2692 > URL: https://issues.jboss.org/browse/JBTM-2692 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Affects Versions: 5.3.3.Final > Reporter: Guillaume Nodet > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. > Patch below: > {code} > diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml > index 87d32c5..cd68637 100644 > --- a/osgi/jta/pom.xml > +++ b/osgi/jta/pom.xml > @@ -206,6 +206,9 @@ > org.apache.felix.service.command, > org.apache.karaf.shell.api.action, > org.apache.karaf.shell.api.action.lifecycle, > + javax.enterprise.util;resolution:=optional, > + javax.interceptor;resolution:=optional > + javax.enterprise.context;resolution:=optional > > true > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 17 13:37:00 2016 From: issues at jboss.org (Guillaume Nodet (JIRA)) Date: Fri, 17 Jun 2016 13:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254263#comment-13254263 ] Guillaume Nodet commented on JBTM-2692: --------------------------------------- Yes, that will allow the CDI annotations on @Transactional and @TransactionScoped to be available, else the class is visible but without annotations, which cause CDI failures. > Narayana OSGi bundle is missing optional packages > ------------------------------------------------- > > Key: JBTM-2692 > URL: https://issues.jboss.org/browse/JBTM-2692 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Affects Versions: 5.3.3.Final > Reporter: Guillaume Nodet > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. > Patch below: > {code} > diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml > index 87d32c5..cd68637 100644 > --- a/osgi/jta/pom.xml > +++ b/osgi/jta/pom.xml > @@ -206,6 +206,9 @@ > org.apache.felix.service.command, > org.apache.karaf.shell.api.action, > org.apache.karaf.shell.api.action.lifecycle, > + javax.enterprise.util;resolution:=optional, > + javax.interceptor;resolution:=optional > + javax.enterprise.context;resolution:=optional > > true > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 20 05:18:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 20 Jun 2016 05:18:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254476#comment-13254476 ] RH Bugzilla Integration commented on JBTM-2550: ----------------------------------------------- Daniel Simko changed the Status of [bug 1333245|https://bugzilla.redhat.com/show_bug.cgi?id=1333245] from ON_QA to VERIFIED > If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Affects Versions: 5.2.8.Final > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.33, 5.2.10.Final > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR > We can catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 20 22:37:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 20 Jun 2016 22:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254912#comment-13254912 ] Amos Feng commented on JBTM-2692: --------------------------------- Thanks, is there any CDI test I check for these changes ? > Narayana OSGi bundle is missing optional packages > ------------------------------------------------- > > Key: JBTM-2692 > URL: https://issues.jboss.org/browse/JBTM-2692 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Affects Versions: 5.3.3.Final > Reporter: Guillaume Nodet > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. > Patch below: > {code} > diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml > index 87d32c5..cd68637 100644 > --- a/osgi/jta/pom.xml > +++ b/osgi/jta/pom.xml > @@ -206,6 +206,9 @@ > org.apache.felix.service.command, > org.apache.karaf.shell.api.action, > org.apache.karaf.shell.api.action.lifecycle, > + javax.enterprise.util;resolution:=optional, > + javax.interceptor;resolution:=optional > + javax.enterprise.context;resolution:=optional > > true > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 20 22:37:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 20 Jun 2016 22:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254912#comment-13254912 ] Amos Feng edited comment on JBTM-2692 at 6/20/16 10:36 PM: ----------------------------------------------------------- Thanks, is there any CDI test I can check for these changes ? was (Author: zhfeng): Thanks, is there any CDI test I check for these changes ? > Narayana OSGi bundle is missing optional packages > ------------------------------------------------- > > Key: JBTM-2692 > URL: https://issues.jboss.org/browse/JBTM-2692 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Affects Versions: 5.3.3.Final > Reporter: Guillaume Nodet > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. > Patch below: > {code} > diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml > index 87d32c5..cd68637 100644 > --- a/osgi/jta/pom.xml > +++ b/osgi/jta/pom.xml > @@ -206,6 +206,9 @@ > org.apache.felix.service.command, > org.apache.karaf.shell.api.action, > org.apache.karaf.shell.api.action.lifecycle, > + javax.enterprise.util;resolution:=optional, > + javax.interceptor;resolution:=optional > + javax.enterprise.context;resolution:=optional > > true > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 22 01:50:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 22 Jun 2016 01:50:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Amos Feng created pull request #1026 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Narayana OSGi bundle is missing optional packages > ------------------------------------------------- > > Key: JBTM-2692 > URL: https://issues.jboss.org/browse/JBTM-2692 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Affects Versions: 5.3.3.Final > Reporter: Guillaume Nodet > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. > Patch below: > {code} > diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml > index 87d32c5..cd68637 100644 > --- a/osgi/jta/pom.xml > +++ b/osgi/jta/pom.xml > @@ -206,6 +206,9 @@ > org.apache.felix.service.command, > org.apache.karaf.shell.api.action, > org.apache.karaf.shell.api.action.lifecycle, > + javax.enterprise.util;resolution:=optional, > + javax.interceptor;resolution:=optional > + javax.enterprise.context;resolution:=optional > > true > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 22 03:46:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 22 Jun 2016 03:46:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2689) narayana-osgi-jta integration test does not work with the karaf 4.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255500#comment-13255500 ] Tom Jenkinson commented on JBTM-2689: ------------------------------------- Have you raised a discussion on the Arquillian forums? If not you should do and link it here. > narayana-osgi-jta integration test does not work with the karaf 4.x > ------------------------------------------------------------------- > > Key: JBTM-2689 > URL: https://issues.jboss.org/browse/JBTM-2689 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > > The aquillian-container-karaf-embedded only support the karaf 2.3.3 and we are using the shell command with 4.x > Now we just disable the integration test temperately. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 22 12:44:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 22 Jun 2016 12:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2693) jca-and-hibernate quickstart CI failure In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2693: -------------------------------------- Summary: jca-and-hibernate quickstart CI failure Key: JBTM-2693 URL: https://issues.jboss.org/browse/JBTM-2693 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Affects Versions: 5.3.3.Final Reporter: Michael Musgrove Assignee: Gytis Trikleris The quickstart fails with a hibernate constraint violation: CI output: http://172.17.130.4:8083/job/narayana-quickstarts-ipv6/28 Output: {quote} 2016-06-18 07:36:23,944 [main] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - Unique index or primary key violation: "UK_6M4FUHXJ4CKIXI1VSB8OSII7R_INDEX_5 ON PUBLIC.CUSTOMER(NAME)"; SQL statement: insert into Customer (name, id) values (?, ?) [23505-171] 2016-06-18 07:36:23,947 [main] WARN com.arjuna.ats.arjuna - ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< -180000000000000:22cf30fffe66b53b:d118:5764ebe6:2a, org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization at 1b0a7baf > javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not execute statement 2016-06-18 07:36:23,944 [main] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - Unique index or primary key violation: "UK_6M4FUHXJ4CKIXI1VSB8OSII7R_INDEX_5 ON PUBLIC.CUSTOMER(NAME)"; SQL statement: insert into Customer (name, id) values (?, ?) [23505-171] 2016-06-18 07:36:23,947 [main] WARN com.arjuna.ats.arjuna - ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< -180000000000000:22cf30fffe66b53b:d118:5764ebe6:2a, org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization at 1b0a7baf > javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not execute statement {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 02:02:01 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 24 Jun 2016 02:02:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2480 started by Amos Feng. --------------------------------------- > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 02:03:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 24 Jun 2016 02:03:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2686) Introduce a Heuristic example in the karaf osgi-jta quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2686: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Introduce a Heuristic example in the karaf osgi-jta quickstart > -------------------------------------------------------------- > > Key: JBTM-2686 > URL: https://issues.jboss.org/browse/JBTM-2686 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > This example could be used to show how to mange the transaction object stores with the karaf cli commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 12:54:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 24 Jun 2016 12:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256975#comment-13256975 ] Michael Musgrove commented on JBTM-2685: ---------------------------------------- Status update: Git branch: https://github.com/mmusgrov/narayana/tree/JBTM-2685 CI job: http://albany.eng.hst.ams2.redhat.com/job/narayana-jdk-9 (its pinned to sansa and lancel on which I installed the java 9 jdk). There are still things that need resolving (all marked with in the relevant poms). Build issues: 1) ArjunaJTS/jtax/pom.xml all tests disabled - they fail with ClassDefFoundError: org/omg/CORBA/BAD_INV_ORDER even though I am running the JVM with -addmods java.corba Status: needs investigation 2) pom.xml: compensations module disabled - java.annotations.common jigsaw module hides javax.annotation-api-1.2 on the classpath but does not contain javax.annotation.Priority Status: two options: 1) replace or patch java.annotations.common or 2) remove the Priority annotation (email sent to [~paul.robinson] to get his opinion) 3) pom.xml: disable byteman-rulecheck-maven-plugin - fails with IllegalArgumentException checking scripts in our ArjunaCore/arjuna module Status: email sent to [~adinn] Test excludes (I am working my way through these): ArjunaJTA/jdbc/pom.xml - exclude SimpleJdbcTest.java ArjunaJTA/jta/pom.xml - exclude 8 test sources ArjunaJTA/cdi/pom.xml - exclude 4 test sources ArjunaJTA/spi/pom.xml - exclude TestSPI.java ArjunaCore/arjuna/pom.xml - exclude ObjectStoreTest.java and ReaperTestCase.java ./txframework/pom.xml - exclude 3 test sources ./osgi/jta/pom.xml - exclude OSGiJTATest.java ./rts/at/bridge/pom.xml - exclude 5 test sources ./rts/at/webservice/pom.xml - exclude ClientIntegrationTest.java ./rts/at/integration/pom.xml - exclude BasicIntegrationTestCase.java and RecoveryIntegrationTestCase.java ./ArjunaJTS/jts/pom.xml - exclude 14 test sources > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sat Jun 25 08:56:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 25 Jun 2016 08:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256975#comment-13256975 ] Michael Musgrove edited comment on JBTM-2685 at 6/25/16 8:55 AM: ----------------------------------------------------------------- Status update: Git branch: https://github.com/mmusgrov/narayana/tree/JBTM-2685 CI job: http://albany.eng.hst.ams2.redhat.com/job/narayana-jdk-9 (its pinned to sansa and lancel on which I installed the java 9 jdk). There are still things that need resolving (all marked with in the relevant poms). Build issues: 1) ArjunaJTS/jtax/pom.xml all tests disabled - they fail with ClassDefFoundError: org/omg/CORBA/BAD_INV_ORDER even though I am running the JVM with -addmods java.corba Status: needs investigation 2) pom.xml: compensations module disabled - java.annotations.common jigsaw module hides javax.annotation-api-1.2 on the classpath but does not contain javax.annotation.Priority Status: two options: 1) replace or patch java.annotations.common or 2) remove the Priority annotation (email sent to [~paul.robinson] to get his opinion) 3) pom.xml: disable byteman-rulecheck-maven-plugin - fails with IllegalArgumentException checking scripts in our ArjunaCore/arjuna module Status: https://issues.jboss.org/browse/BYTEMAN-324 Test excludes (I am working my way through these): ArjunaJTA/jdbc/pom.xml - exclude SimpleJdbcTest.java ArjunaJTA/jta/pom.xml - exclude 8 test sources ArjunaJTA/cdi/pom.xml - exclude 4 test sources ArjunaJTA/spi/pom.xml - exclude TestSPI.java ArjunaCore/arjuna/pom.xml - exclude ObjectStoreTest.java and ReaperTestCase.java ./txframework/pom.xml - exclude 3 test sources ./osgi/jta/pom.xml - exclude OSGiJTATest.java ./rts/at/bridge/pom.xml - exclude 5 test sources ./rts/at/webservice/pom.xml - exclude ClientIntegrationTest.java ./rts/at/integration/pom.xml - exclude BasicIntegrationTestCase.java and RecoveryIntegrationTestCase.java ./ArjunaJTS/jts/pom.xml - exclude 14 test sources was (Author: mmusgrov): Status update: Git branch: https://github.com/mmusgrov/narayana/tree/JBTM-2685 CI job: http://albany.eng.hst.ams2.redhat.com/job/narayana-jdk-9 (its pinned to sansa and lancel on which I installed the java 9 jdk). There are still things that need resolving (all marked with in the relevant poms). Build issues: 1) ArjunaJTS/jtax/pom.xml all tests disabled - they fail with ClassDefFoundError: org/omg/CORBA/BAD_INV_ORDER even though I am running the JVM with -addmods java.corba Status: needs investigation 2) pom.xml: compensations module disabled - java.annotations.common jigsaw module hides javax.annotation-api-1.2 on the classpath but does not contain javax.annotation.Priority Status: two options: 1) replace or patch java.annotations.common or 2) remove the Priority annotation (email sent to [~paul.robinson] to get his opinion) 3) pom.xml: disable byteman-rulecheck-maven-plugin - fails with IllegalArgumentException checking scripts in our ArjunaCore/arjuna module Status: email sent to [~adinn] Test excludes (I am working my way through these): ArjunaJTA/jdbc/pom.xml - exclude SimpleJdbcTest.java ArjunaJTA/jta/pom.xml - exclude 8 test sources ArjunaJTA/cdi/pom.xml - exclude 4 test sources ArjunaJTA/spi/pom.xml - exclude TestSPI.java ArjunaCore/arjuna/pom.xml - exclude ObjectStoreTest.java and ReaperTestCase.java ./txframework/pom.xml - exclude 3 test sources ./osgi/jta/pom.xml - exclude OSGiJTATest.java ./rts/at/bridge/pom.xml - exclude 5 test sources ./rts/at/webservice/pom.xml - exclude ClientIntegrationTest.java ./rts/at/integration/pom.xml - exclude BasicIntegrationTestCase.java and RecoveryIntegrationTestCase.java ./ArjunaJTS/jts/pom.xml - exclude 14 test sources > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 27 09:53:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 27 Jun 2016 09:53:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2694) Use InVM connector factory for JMS integration tests In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2694: ----------------------------------- Summary: Use InVM connector factory for JMS integration tests Key: JBTM-2694 URL: https://issues.jboss.org/browse/JBTM-2694 Project: JBoss Transaction Manager Issue Type: Task Components: Testing Reporter: Tom Jenkinson Fix For: 5.next Port 61616 doesn't work reliably on Windows boxes: http://stackoverflow.com/questions/11700233/activemq-cant-run-due-to-address-already-in-use-error Move tests to using InVM connector -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 27 09:56:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 27 Jun 2016 09:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2694) Use InVM connector factory for JMS integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1027 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Use InVM connector factory for JMS integration tests > ---------------------------------------------------- > > Key: JBTM-2694 > URL: https://issues.jboss.org/browse/JBTM-2694 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Fix For: 5.next > > > Port 61616 doesn't work reliably on Windows boxes: > http://stackoverflow.com/questions/11700233/activemq-cant-run-due-to-address-already-in-use-error > Move tests to using InVM connector -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 28 07:00:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jun 2016 07:00:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1028 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Migrate performance tests to the performance repo > ------------------------------------------------- > > Key: JBTM-2542 > URL: https://issues.jboss.org/browse/JBTM-2542 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Attachments: config.xml, eap-cmp-config.xml > > > We still have lots of performance related unit tests that need migrating: > rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceDefaultUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceVolatileUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceVolatileUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceDefaultUnitTest.java > ArjunaJTA/jta/tests/classes/com/hp/mwtests/ts/jta/commitmarkable/PerformanceTestCommitMarkableResource.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance1.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance2.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance4.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance3.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance1.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance2.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance3.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/PerfHammer.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/GridWorker.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/local/synchronizations/Performance.java > ArjunaJTA/jta/tests/classes/io/narayana/perf/product/Product.java > ArjunaJTA/jta/tests/classes/io/narayana/perf/product/ProductWorker.java -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 28 08:28:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 28 Jun 2016 08:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2695) Blacktie administration services test deployment fails In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2695: ------------------------------------- Summary: Blacktie administration services test deployment fails Key: JBTM-2695 URL: https://issues.jboss.org/browse/JBTM-2695 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Gytis Trikleris Assignee: Amos Feng Priority: Minor Fix For: 5.next {code} T E S T S ------------------------------------------------------- Running AdvertiseUnadvertiseTest 20:38:01,608 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/65/36deb9697994d21be752edb6296e8d3ea4456f/content 20:38:01,662 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") 20:38:02,983 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined} 20:38:02,999 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 12ms 20:38:03,036 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined} 20:38:03,037 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.undertow.listener.https: org.jboss.msc.service.StartException in service jboss.undertow.listener.https: Failed to start service Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.32 sec <<< FAILURE! - in AdvertiseUnadvertiseTest AdvertiseUnadvertiseTest Time elapsed: 7.319 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: test.war at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83) at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64) at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46) at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:87) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:201) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Caused by: java.lang.Exception: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined} at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134) at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123) at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85) at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42) at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55) at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77) at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64) at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46) at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:144) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:87) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:201) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Results : Tests in error: AdvertiseUnadvertiseTest.AdvertiseUnadvertiseTest ? Deployment Cannot deploy: ... Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Blacktie C++ Plugin ................................ SUCCESS [ 16.490 s] [INFO] BlackTie all files ................................. SUCCESS [ 2.660 s] [INFO] Blacktie Defaults and Dependencies ................. SUCCESS [ 0.096 s] [INFO] Blacktie C Defaults and Dependencies ............... SUCCESS [ 7.708 s] [INFO] Blacktie Java JNI Tests ............................ SUCCESS [ 3.153 s] [INFO] Blacktie Schemas ................................... SUCCESS [ 2.247 s] [INFO] BlackTie Messaging (via JMS) ....................... SUCCESS [ 5.733 s] [INFO] Blacktie Java XATMI Implementation ................. SUCCESS [05:37 min] [INFO] Blacktie Java NBF Implementation ................... SUCCESS [ 4.431 s] [INFO] Blacktie Administration Services ................... FAILURE [ 52.390 s] [INFO] Blacktie Administration Services EAR ............... SKIPPED [INFO] Blacktie Core C++ Implementation ................... SKIPPED [INFO] Blacktie Codec C++ Implementation .................. SKIPPED [INFO] Blacktie C++ REST Transport ........................ SKIPPED [INFO] Blacktie Utilities ................................. SKIPPED [INFO] Blacktie C++ TX Client Library ..................... SKIPPED [INFO] Blacktie C++ Hybrid Transport ...................... SKIPPED [INFO] Blacktie C++ XATMI Implementation .................. SKIPPED [INFO] Blacktie C++ Queue Client .......................... SKIPPED [INFO] Blacktie NBF ....................................... SKIPPED [INFO] BlackTie Admin CLI Tool ............................ SKIPPED [INFO] Blacktie Server Code Generation .................... SKIPPED [INFO] Blacktie Java/C C/Java XATMI Tests ................. SKIPPED [INFO] Blacktie Distribution .............................. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 07:36 min [INFO] Finished at: 2016-06-24T20:38:03+01:00 [INFO] Final Memory: 60M/144M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on project blacktie-admin-services: There are test failures. [ERROR] [ERROR] Please refer to /home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/blacktie-admin-services/target/surefire-reports for the individual test results. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :blacktie-admin-services UID PID PPID C STIME TTY TIME CMD hudson 8757 8755 0 Apr12 ? 00:22:38 sshd: hudson at notty hudson 8835 8757 0 Apr12 ? 00:00:00 bash -c cd "/home/hudson" && java -jar slave.jar hudson 8852 8835 0 Apr12 ? 01:03:45 java -jar slave.jar hudson 9476 32418 0 Apr12 ? 00:00:18 /usr/local/jdk1.8.0_60/jre/bin/java -Dnames=.* -Dadditional.elements=-DObjectStoreEnvironmentBean.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.communicationStore.tablePrefix=Communication -DObjectStoreEnvironmentBean.communicationStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.stateStore.tablePrefix=stateStore -DObjectStoreEnvironmentBean.stateStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.tablePrefix=Action -DObjectStoreEnvironmentBean.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.ibm.db2.jcc.DB2DataSource;DatabaseName=BTDB1;User=db2;Password=db2;ServerName=tywin.eng.hst.ams2.redhat.com;PortNumber=50001;DriverType=4 -DObjectStoreEnvironmentBean.stateStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.ibm.db2.jcc.DB2DataSource;DatabaseName=BTDB1;User=db2;Password=db2;ServerName=tywin.eng.hst.ams2.redhat.com;PortNumber=50001;DriverType=4 -DObjectStoreEnvironmentBean.communicationStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.ibm.db2.jcc.DB2DataSource;DatabaseName=BTDB1;User=db2;Password=db2;ServerName=tywin.eng.hst.ams2.redhat.com;PortNumber=50001;DriverType=4 -Dtest.timeout= -classpath /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/ext/junit.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/tests/build/jbossts-jts-qa.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/jbossjts.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/artemis-commons.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/artemis-journal.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/artemis-native.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/commons-beanutils.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/commons-collections.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/commons-logging.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/dom4j.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/guava.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/hamcrest-core.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/ironjacamar-spec-api.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/jboss-connector-api_1.5_spec.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/jboss-logging-annotations.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/jboss-logging-processor.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/jboss-loggin hudson 14629 1 0 Apr08 ? 00:00:00 /bin/bash -xe /tmp/hudson1493082877525066780.sh hudson 14655 14629 0 Apr08 ? 00:00:00 /bin/bash -xe /tmp/hudson1493082877525066780.sh hudson 19882 8852 0 20:07 ? 00:00:00 /bin/bash -xe /tmp/hudson3887036970646544553.sh hudson 19887 19882 0 20:07 ? 00:00:00 /bin/bash -xe /tmp/hudson3887036970646544553.sh hudson 21590 19887 0 20:30 ? 00:00:00 /bin/sh blacktie/wildfly-10.1.0.Final-SNAPSHOT/bin/standalone.sh -c standalone-blacktie.xml -Djboss.bind.address=localhost -Djboss.bind.address.unsecure=localhost -Djboss.bind.address.management=localhost hudson 21646 21590 6 20:30 ? 00:00:30 /usr/local/jdk1.8.0_60//bin/java -D[Standalone] -server -Xmx256m -XX:MaxPermSize=256m -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties -jar /home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar -mp /home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/modules org.jboss.as.standalone -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/standalone -c standalone-blacktie.xml -Djboss.bind.address=localhost -Djboss.bind.address.unsecure=localhost -Djboss.bind.address.management=localhost hudson 22528 19887 0 20:38 ? 00:00:00 ps -f hudson 32418 14655 0 Apr12 ? 00:00:41 /usr/local/jdk1.8.0_60//jre/bin/java -classpath /home/hudson/apache-ant-1.8.2/lib/ant-launcher.jar -Dant.home=/home/hudson/apache-ant-1.8.2 -Dant.library.dir=/home/hudson/apache-ant-1.8.2/lib org.apache.tools.ant.launch.Launcher -cp -f run-tests.xml ci-jts-tests -Dprofile=db2 -Dcode.coverage=false blacktie/wildfly-10.1.0.Final-SNAPSHOT/bin/standalone.sh: line 307: 21646 Killed "/usr/local/jdk1.8.0_60//bin/java" -D"[Standalone]" -server -Xmx256m -XX:MaxPermSize=256m -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE "-Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log" "-Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties" -jar "/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar" -mp "/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/modules" org.jboss.as.standalone -Djboss.home.dir="/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT" -Djboss.server.base.dir="/home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk8.latest/label/linux64el5/blacktie/wildfly-10.1.0.Final-SNAPSHOT/standalone" '-c' 'standalone-blacktie.xml' '-Djboss.bind.address=localhost' '-Djboss.bind.address.unsecure=localhost' '-Djboss.bind.address.management=localhost' pkill: 2508 - Operation not permitted pkill: 1841 - Operation not permitted pkill: 3071 - Operation not permitted pkill: 1413 - Operation not permitted pkill: 1497 - Operation not permitted pkill: 1502 - Operation not permitted pkill: 1503 - Operation not permitted pkill: 1596 - Operation not permitted pkill: 2221 - Operation not permitted UID PID PPID C STIME TTY TIME CMD hudson 8757 8755 0 Apr12 ? 00:22:38 sshd: hudson at notty hudson 8835 8757 0 Apr12 ? 00:00:00 bash -c cd "/home/hudson" && java -jar slave.jar hudson 8852 8835 0 Apr12 ? 01:03:45 java -jar slave.jar hudson 9476 32418 0 Apr12 ? 00:00:18 /usr/local/jdk1.8.0_60/jre/bin/java -Dnames=.* -Dadditional.elements=-DObjectStoreEnvironmentBean.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.communicationStore.tablePrefix=Communication -DObjectStoreEnvironmentBean.communicationStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.stateStore.tablePrefix=stateStore -DObjectStoreEnvironmentBean.stateStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.tablePrefix=Action -DObjectStoreEnvironmentBean.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.ibm.db2.jcc.DB2DataSource;DatabaseName=BTDB1;User=db2;Password=db2;ServerName=tywin.eng.hst.ams2.redhat.com;PortNumber=50001;DriverType=4 -DObjectStoreEnvironmentBean.stateStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.ibm.db2.jcc.DB2DataSource;DatabaseName=BTDB1;User=db2;Password=db2;ServerName=tywin.eng.hst.ams2.redhat.com;PortNumber=50001;DriverType=4 -DObjectStoreEnvironmentBean.communicationStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.ibm.db2.jcc.DB2DataSource;DatabaseName=BTDB1;User=db2;Password=db2;ServerName=tywin.eng.hst.ams2.redhat.com;PortNumber=50001;DriverType=4 -Dtest.timeout= -classpath /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/ext/junit.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/tests/build/jbossts-jts-qa.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/jbossjts.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/artemis-commons.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/artemis-journal.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/artemis-native.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/commons-beanutils.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/commons-collections.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/commons-logging.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/dom4j.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/guava.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/hamcrest-core.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/ironjacamar-spec-api.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/jboss-connector-api_1.5_spec.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/jboss-logging-annotations.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/jboss-logging-processor.jar:/home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk8.latest/slave/linux/qa/dist/narayana-full-5.3.3.Final-SNAPSHOT/lib/ext/jboss-loggin hudson 14629 1 0 Apr08 ? 00:00:00 /bin/bash -xe /tmp/hudson1493082877525066780.sh hudson 14655 14629 0 Apr08 ? 00:00:00 /bin/bash -xe /tmp/hudson1493082877525066780.sh hudson 19882 8852 0 20:07 ? 00:00:00 /bin/bash -xe /tmp/hudson3887036970646544553.sh hudson 19887 19882 0 20:07 ? 00:00:00 /bin/bash -xe /tmp/hudson3887036970646544553.sh hudson 22539 19887 0 20:38 ? 00:00:00 ps -f hudson 32418 14655 0 Apr12 ? 00:00:41 /usr/local/jdk1.8.0_60//jre/bin/java -classpath /home/hudson/apache-ant-1.8.2/lib/ant-launcher.jar -Dant.home=/home/hudson/apache-ant-1.8.2 -Dant.library.dir=/home/hudson/apache-ant-1.8.2/lib org.apache.tools.ant.launch.Launcher -cp -f run-tests.xml ci-jts-tests -Dprofile=db2 -Dcode.coverage=false Some tests failed: http://albany.eng.hst.ams2.redhat.com/job/narayana/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux64el5/1101/ {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 28 08:34:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 28 Jun 2016 08:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2696) TestGroup_txcore_recovery failure on DB2 In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2696: ------------------------------------- Summary: TestGroup_txcore_recovery failure on DB2 Key: JBTM-2696 URL: https://issues.jboss.org/browse/JBTM-2696 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Minor Fix For: 5.next {code} [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery [junit] Tests run: 36, Failures: 1, Errors: 0, Time elapsed: 3,224.323 sec [junit] Test org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery FAILED {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 28 09:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jun 2016 09:30:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2206) Use synchronized HashMaps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2206: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: (was: 5.next) Resolution: Rejected Our CI did not show this pull request having a significant performance improvement. If you believe our performance testing is not adequate in this area please do feel free to continue the discussions on our forum. We could look to add further tests that you might recommend so as to see the improvement. > Use synchronized HashMaps > ------------------------- > > Key: JBTM-2206 > URL: https://issues.jboss.org/browse/JBTM-2206 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Transaction Core > Reporter: Jesper Pedersen > Assignee: Tom Jenkinson > Priority: Minor > > Change usage of Hashtable into synchronized HashMap's instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 28 09:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jun 2016 09:31:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2203) Remove ReentrantLock from StateManager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2203: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: (was: 5.next) Resolution: Rejected Our CI did not show this pull request having a significant performance improvement. If you believe our performance testing is not adequate in this area please do feel free to continue the discussions on our forum. We could look to add further tests that you might recommend so as to see the improvement. > Remove ReentrantLock from StateManager > -------------------------------------- > > Key: JBTM-2203 > URL: https://issues.jboss.org/browse/JBTM-2203 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > > Remove unused lock from StateManager, and add the access methods to LockManager instead -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 29 04:02:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 29 Jun 2016 04:02:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2692) Narayana OSGi bundle is missing optional packages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2692: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Narayana OSGi bundle is missing optional packages > ------------------------------------------------- > > Key: JBTM-2692 > URL: https://issues.jboss.org/browse/JBTM-2692 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Affects Versions: 5.3.3.Final > Reporter: Guillaume Nodet > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > The problem is that the annotations on @Transactional are lost, which makes this annotation unusable in a CDI environment. > Patch below: > {code} > diff --git a/osgi/jta/pom.xml b/osgi/jta/pom.xml > index 87d32c5..cd68637 100644 > --- a/osgi/jta/pom.xml > +++ b/osgi/jta/pom.xml > @@ -206,6 +206,9 @@ > org.apache.felix.service.command, > org.apache.karaf.shell.api.action, > org.apache.karaf.shell.api.action.lifecycle, > + javax.enterprise.util;resolution:=optional, > + javax.interceptor;resolution:=optional > + javax.enterprise.context;resolution:=optional > > true > > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 29 04:04:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 29 Jun 2016 04:04:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2697) Add a test to check @Transactional work with the narayana osgi bundle In-Reply-To: References: Message-ID: Amos Feng created JBTM-2697: ------------------------------- Summary: Add a test to check @Transactional work with the narayana osgi bundle Key: JBTM-2697 URL: https://issues.jboss.org/browse/JBTM-2697 Project: JBoss Transaction Manager Issue Type: Task Reporter: Amos Feng Assignee: Amos Feng It needs to add a test to check if the annotation works -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 29 04:09:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 29 Jun 2016 04:09:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2687) There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2687: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests > ------------------------------------------------------------------------------------- > > Key: JBTM-2687 > URL: https://issues.jboss.org/browse/JBTM-2687 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing, TxBridge > Affects Versions: 5.3.3.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > There are three times: > {code}parameters.add(new BasicNameValuePair("isTransaction", "ture"));{code} > instead of > {code}parameters.add(new BasicNameValuePair("isTransaction", "true"));{code} > which affect test behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 29 09:29:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 29 Jun 2016 09:29:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2696) TestGroup_txcore_recovery failure on DB2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2696: -------------------------------- Description: {code} [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery [junit] Tests run: 36, Failures: 1, Errors: 0, Time elapsed: 3,224.323 sec [junit] Test org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery FAILED {code} Recovery_Crash_LockManager_Test008/server_0_output.txt {code} 2016-06-25 03:12:45,296 out: 2016-06-25 03:12:45,290 [Periodic Recovery] WARN com.arjuna.ats.txoj - ARJUNA015011: RecoveredTransactionalObject::findHoldingTransaction - exception 2016-06-25 03:12:45,296 out: java.io.IOException: java.lang.NullPointerException 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:741) 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.findHoldingTransaction(RecoveredTransactionalObject.java:175) 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.replayPhase2(RecoveredTransactionalObject.java:88) 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.recoverObject(TORecoveryModule.java:232) 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.periodicWorkSecondPass(TORecoveryModule.java:183) 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:793) 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) 2016-06-25 03:12:45,296 out: Caused by: java.lang.NullPointerException 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:706) 2016-06-25 03:12:45,296 out: ... 6 more {code} was: {code} [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery [junit] Tests run: 36, Failures: 1, Errors: 0, Time elapsed: 3,224.323 sec [junit] Test org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery FAILED {code} > TestGroup_txcore_recovery failure on DB2 > ---------------------------------------- > > Key: JBTM-2696 > URL: https://issues.jboss.org/browse/JBTM-2696 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > {code} > [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery > [junit] Tests run: 36, Failures: 1, Errors: 0, Time elapsed: 3,224.323 sec > [junit] Test org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery FAILED > {code} > Recovery_Crash_LockManager_Test008/server_0_output.txt > {code} > 2016-06-25 03:12:45,296 out: 2016-06-25 03:12:45,290 [Periodic Recovery] WARN com.arjuna.ats.txoj - ARJUNA015011: RecoveredTransactionalObject::findHoldingTransaction - exception > 2016-06-25 03:12:45,296 out: java.io.IOException: java.lang.NullPointerException > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:741) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.findHoldingTransaction(RecoveredTransactionalObject.java:175) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.replayPhase2(RecoveredTransactionalObject.java:88) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.recoverObject(TORecoveryModule.java:232) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.periodicWorkSecondPass(TORecoveryModule.java:183) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:793) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > 2016-06-25 03:12:45,296 out: Caused by: java.lang.NullPointerException > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:706) > 2016-06-25 03:12:45,296 out: ... 6 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 29 09:42:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 29 Jun 2016 09:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2696) TestGroup_txcore_recovery failure on DB2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1029 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > TestGroup_txcore_recovery failure on DB2 > ---------------------------------------- > > Key: JBTM-2696 > URL: https://issues.jboss.org/browse/JBTM-2696 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > {code} > [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery > [junit] Tests run: 36, Failures: 1, Errors: 0, Time elapsed: 3,224.323 sec > [junit] Test org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery FAILED > {code} > Recovery_Crash_LockManager_Test008/server_0_output.txt > {code} > 2016-06-25 03:12:45,296 out: 2016-06-25 03:12:45,290 [Periodic Recovery] WARN com.arjuna.ats.txoj - ARJUNA015011: RecoveredTransactionalObject::findHoldingTransaction - exception > 2016-06-25 03:12:45,296 out: java.io.IOException: java.lang.NullPointerException > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:741) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.findHoldingTransaction(RecoveredTransactionalObject.java:175) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.replayPhase2(RecoveredTransactionalObject.java:88) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.recoverObject(TORecoveryModule.java:232) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.periodicWorkSecondPass(TORecoveryModule.java:183) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:793) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > 2016-06-25 03:12:45,296 out: Caused by: java.lang.NullPointerException > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:706) > 2016-06-25 03:12:45,296 out: ... 6 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 29 09:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 29 Jun 2016 09:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2696) TestGroup_txcore_recovery failure on DB2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2696: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > TestGroup_txcore_recovery failure on DB2 > ---------------------------------------- > > Key: JBTM-2696 > URL: https://issues.jboss.org/browse/JBTM-2696 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > {code} > [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery > [junit] Tests run: 36, Failures: 1, Errors: 0, Time elapsed: 3,224.323 sec > [junit] Test org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery FAILED > {code} > Recovery_Crash_LockManager_Test008/server_0_output.txt > {code} > 2016-06-25 03:12:45,296 out: 2016-06-25 03:12:45,290 [Periodic Recovery] WARN com.arjuna.ats.txoj - ARJUNA015011: RecoveredTransactionalObject::findHoldingTransaction - exception > 2016-06-25 03:12:45,296 out: java.io.IOException: java.lang.NullPointerException > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:741) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.findHoldingTransaction(RecoveredTransactionalObject.java:175) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.replayPhase2(RecoveredTransactionalObject.java:88) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.recoverObject(TORecoveryModule.java:232) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.periodicWorkSecondPass(TORecoveryModule.java:183) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:793) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > 2016-06-25 03:12:45,296 out: Caused by: java.lang.NullPointerException > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:706) > 2016-06-25 03:12:45,296 out: ... 6 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:27:00 2016 From: issues at jboss.org (gil cattaneo (JIRA)) Date: Thu, 30 Jun 2016 05:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) jboss-transaction-spi don't include the license file In-Reply-To: References: Message-ID: gil cattaneo created JBTM-2698: ---------------------------------- Summary: jboss-transaction-spi don't include the license file Key: JBTM-2698 URL: https://issues.jboss.org/browse/JBTM-2698 Project: JBoss Transaction Manager Issue Type: Bug Reporter: gil cattaneo hi Not available LICENSE file in source directory structure Please. Added license and copyright notice. the fedora pakaging guideline is very strictly precise about this problem https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text Thanks Regards p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:33:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 05:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) jboss-transaction-spi don't include the license file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2698: ----------------------------------- Assignee: Michael Musgrove > jboss-transaction-spi don't include the license file > ---------------------------------------------------- > > Key: JBTM-2698 > URL: https://issues.jboss.org/browse/JBTM-2698 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: gil cattaneo > Assignee: Michael Musgrove > Fix For: 5.next > > > hi > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text > Thanks > Regards > p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:33:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 05:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) jboss-transaction-spi don't include the license file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2698: -------------------------------- Fix Version/s: 5.next > jboss-transaction-spi don't include the license file > ---------------------------------------------------- > > Key: JBTM-2698 > URL: https://issues.jboss.org/browse/JBTM-2698 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: gil cattaneo > Assignee: Michael Musgrove > Fix For: 5.next > > > hi > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text > Thanks > Regards > p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:33:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 05:33:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) jboss-transaction-spi don't include the license file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2698: -------------------------------- Issue Type: Task (was: Bug) > jboss-transaction-spi don't include the license file > ---------------------------------------------------- > > Key: JBTM-2698 > URL: https://issues.jboss.org/browse/JBTM-2698 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: gil cattaneo > Assignee: Michael Musgrove > Fix For: 5.next > > > hi > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text > Thanks > Regards > p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:33:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 05:33:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) jboss-transaction-spi don't include the license file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2698: -------------------------------- Priority: Blocker (was: Major) > jboss-transaction-spi don't include the license file > ---------------------------------------------------- > > Key: JBTM-2698 > URL: https://issues.jboss.org/browse/JBTM-2698 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: gil cattaneo > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > hi > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text > Thanks > Regards > p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:34:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 05:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) GitHub projects don't include the license file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2698: -------------------------------- Summary: GitHub projects don't include the license file (was: jboss-transaction-spi don't include the license file) > GitHub projects don't include the license file > ---------------------------------------------- > > Key: JBTM-2698 > URL: https://issues.jboss.org/browse/JBTM-2698 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: gil cattaneo > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > hi > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text > Thanks > Regards > p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:34:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 05:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) GitHub projects don't include the license file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259108#comment-13259108 ] Tom Jenkinson commented on JBTM-2698: ------------------------------------- Include Narayana and jboss-transaction-spi > GitHub projects don't include the license file > ---------------------------------------------- > > Key: JBTM-2698 > URL: https://issues.jboss.org/browse/JBTM-2698 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: gil cattaneo > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > hi > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text > Thanks > Regards > p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:34:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 30 Jun 2016 05:34:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259109#comment-13259109 ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Ji?? B?lek changed the Status of [bug 1329142|https://bugzilla.redhat.com/show_bug.cgi?id=1329142] from ON_QA to VERIFIED > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:36:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 05:36:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) GitHub projects don't include the license file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2698: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > GitHub projects don't include the license file > ---------------------------------------------- > > Key: JBTM-2698 > URL: https://issues.jboss.org/browse/JBTM-2698 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: gil cattaneo > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > hi > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text > Thanks > Regards > p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 05:39:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 05:39:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) GitHub projects don't include the license file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1030 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > GitHub projects don't include the license file > ---------------------------------------------- > > Key: JBTM-2698 > URL: https://issues.jboss.org/browse/JBTM-2698 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: gil cattaneo > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > hi > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text > Thanks > Regards > p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 06:57:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 30 Jun 2016 06:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2665) Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1031 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release > ------------------------------------------------------------------------------ > > Key: JBTM-2665 > URL: https://issues.jboss.org/browse/JBTM-2665 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.3.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The OSGI build depends on an upgrade of the jboss-transacton-spi (JBTM-2663) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 06:58:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 30 Jun 2016 06:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2665) Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2665 started by Michael Musgrove. ---------------------------------------------- > Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release > ------------------------------------------------------------------------------ > > Key: JBTM-2665 > URL: https://issues.jboss.org/browse/JBTM-2665 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.3.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The OSGI build depends on an upgrade of the jboss-transacton-spi (JBTM-2663) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 06:58:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 30 Jun 2016 06:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2665) Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2665: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/narayana/pull/1031 > Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release > ------------------------------------------------------------------------------ > > Key: JBTM-2665 > URL: https://issues.jboss.org/browse/JBTM-2665 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.3.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The OSGI build depends on an upgrade of the jboss-transacton-spi (JBTM-2663) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 10:05:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 30 Jun 2016 10:05:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2665) Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2665: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade jboss-transacton-spi dependency to 7.3.2.Final before the next release > ------------------------------------------------------------------------------ > > Key: JBTM-2665 > URL: https://issues.jboss.org/browse/JBTM-2665 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.3.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The OSGI build depends on an upgrade of the jboss-transacton-spi (JBTM-2663) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 10:11:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 10:11:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2696) TestGroup_txcore_recovery failure on DB2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2696: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Incomplete Description I have merged a patch with more logging > TestGroup_txcore_recovery failure on DB2 > ---------------------------------------- > > Key: JBTM-2696 > URL: https://issues.jboss.org/browse/JBTM-2696 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > {code} > [junit] Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery > [junit] Tests run: 36, Failures: 1, Errors: 0, Time elapsed: 3,224.323 sec > [junit] Test org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_recovery FAILED > {code} > Recovery_Crash_LockManager_Test008/server_0_output.txt > {code} > 2016-06-25 03:12:45,296 out: 2016-06-25 03:12:45,290 [Periodic Recovery] WARN com.arjuna.ats.txoj - ARJUNA015011: RecoveredTransactionalObject::findHoldingTransaction - exception > 2016-06-25 03:12:45,296 out: java.io.IOException: java.lang.NullPointerException > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:741) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.findHoldingTransaction(RecoveredTransactionalObject.java:175) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.RecoveredTransactionalObject.replayPhase2(RecoveredTransactionalObject.java:88) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.recoverObject(TORecoveryModule.java:232) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.txoj.recovery.TORecoveryModule.periodicWorkSecondPass(TORecoveryModule.java:183) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:793) > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) > 2016-06-25 03:12:45,296 out: Caused by: java.lang.NullPointerException > 2016-06-25 03:12:45,296 out: at com.arjuna.ats.arjuna.StateManager.unpackHeader(StateManager.java:706) > 2016-06-25 03:12:45,296 out: ... 6 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 30 10:15:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jun 2016 10:15:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2698) GitHub projects don't include the license file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2698: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > GitHub projects don't include the license file > ---------------------------------------------- > > Key: JBTM-2698 > URL: https://issues.jboss.org/browse/JBTM-2698 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: gil cattaneo > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > hi > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text > Thanks > Regards > p.s. reported also @ https://github.com/jbosstm/jboss-transaction-spi/issues/9 -- This message was sent by Atlassian JIRA (v6.4.11#64026)