From issues at jboss.org Wed Jul 1 06:06:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 1 Jul 2015 06:06:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2443) Raise a JTA HeuristicMixed if a one phase commit XAResource raises RMFAIL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085294#comment-13085294 ] Michael Musgrove commented on JBTM-2443: ---------------------------------------- Adding link since the change is partially undoing a prior fix > Raise a JTA HeuristicMixed if a one phase commit XAResource raises RMFAIL > ------------------------------------------------------------------------- > > Key: JBTM-2443 > URL: https://issues.jboss.org/browse/JBTM-2443 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > If a one phase commit is performed on an XAResource and it raises RMFAIL we have no way to know whether the resource committed or rolled back. We currently do not raise an exception in this scenario as an interpretation of the XA spec allows us to. > We have had community feedback that this has an issue for user applications and having consulted with the rest of our community and no negative comments received we will modify the behavior so that this scenario results in the closest exception that JTA allows HeuristicMixed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 06:30:05 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 1 Jul 2015 06:30:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2449: -------------------------------------- Summary: SPI class ServerVMClientUserTransaction should be Serializable and Referenceable Key: JBTM-2449 URL: https://issues.jboss.org/browse/JBTM-2449 Project: JBoss Transaction Manager Issue Type: Bug Components: SPI Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 06:41:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 1 Jul 2015 06:41:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-2449. ---------------------------------- Resolution: Duplicate Issue Duplicate of JBTM-77 > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 09:33:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 1 Jul 2015 09:33:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reopened JBTM-2449: ------------------------------------ Reopening since it is not a duplicate of JBTM 77 > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 09:35:02 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 1 Jul 2015 09:35:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2449: ------------------------------------------ Bugzilla Update: (was: Perform) > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 09:36:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 1 Jul 2015 09:36:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2449: ----------------------------------- Issue Type: Feature Request (was: Bug) > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 1 11:11:04 2015 From: issues at jboss.org (=?UTF-8?Q?Ond=C5=99ej_Chaloupka_=28JIRA=29?=) Date: Wed, 1 Jul 2015 11:11:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2428) JTS client side transaction context seems not being propagated to EAP server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ond?ej Chaloupka closed JBTM-2428. ---------------------------------- Resolution: Done Found this being trouble of configuration of the testcase. > JTS client side transaction context seems not being propagated to EAP server > ---------------------------------------------------------------------------- > > Key: JBTM-2428 > URL: https://issues.jboss.org/browse/JBTM-2428 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.1.1 > Reporter: Ond?ej Chaloupka > Assignee: Ond?ej Chaloupka > > It seems that transaction context is not propagated when JTS transaction is started on client. > This was working for EAP 6.4 where iiop corba implementation was used. The testing client is based on guide [1]. > The call from client to server via IIOP [4] works fine but when I'm trying to start transaction on client side and then expecting being propagated to server, server proclaims that there is no txn in the context. > This is how the orb is set up [2] > This is how the transaction is started [3] > This is how the remote call on ejb app server is done [4] > [1] https://developer.jboss.org/wiki/TransactionPropagationWithJBoss > [2] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/base/TestBaseOneServer.java;h=ed9b30aabe11fdb5f3290763beb167182a22a819;hb=HEAD#l530 > [3] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/base/TestBaseOneServer.java;h=ed9b30aabe11fdb5f3290763beb167182a22a819;hb=HEAD#l511 > [4] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/client/TxUtil.java;h=5dd55e22a52df6fd3845b1de5134f436f721a437;hb=HEAD#l69 > [5] [com.arjuna.ats.jts] (main) ARJUNA022251: The ORBManager is already associated with an ORB/OA. > FINE [javax.enterprise.resource.corba._DEFAULT_.rpc.protocol] (main) "IOP01600014: (BAD_INV_ORDER) Cannot access this attribute or method at this point": org.omg.CORBA.BAD_INV_ORDER: vmcid: OMG minor code: 14 completed: No > -- or -- > FINE [javax.enterprise.resource.corba._CORBA_.rpc.presentation] (main) "IOP00110227: (BAD_PARAM) ORBDynamicStubFactoryFactoryClass property had value com.sun.corba.se.impl.presentation.rmi.bcel.StubFactoryFactoryBCELImpl, which could not be loaded by the ORB ClassLoader": org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 227 completed: No -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 12:35:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 2 Jul 2015 12:35:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2449: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/jboss-transaction-spi/pull/6, https://github.com/jbosstm/narayana/pull/881 > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 2 14:31:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 2 Jul 2015 14:31:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2449: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 3 00:56:03 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 3 Jul 2015 00:56:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086136#comment-13086136 ] RH Bugzilla Integration commented on JBTM-2449: ----------------------------------------------- baranowb changed the Status of [bug 1235886|https://bugzilla.redhat.com/show_bug.cgi?id=1235886] from ASSIGNED to MODIFIED > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 3 00:56:04 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 3 Jul 2015 00:56:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) Add a new Observer SPI for tracking transaction state association changes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086137#comment-13086137 ] RH Bugzilla Integration commented on JBTM-2343: ----------------------------------------------- baranowb changed the Status of [bug 1238926|https://bugzilla.redhat.com/show_bug.cgi?id=1238926] from NEW to MODIFIED > Add a new Observer SPI for tracking transaction state association changes > ------------------------------------------------------------------------- > > Key: JBTM-2343 > URL: https://issues.jboss.org/browse/JBTM-2343 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 3 08:50:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 3 Jul 2015 08:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2365) Create feature choice helper on narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2365: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create feature choice helper on narayana.io > ------------------------------------------- > > Key: JBTM-2365 > URL: https://issues.jboss.org/browse/JBTM-2365 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > It would be useful to have something on our homepage that lists all the different transports we use and what features are available when you select each of those transport. Mainly all features are available which allows us to list those too. > Ideally in the future it might replace our current landing page so we should try to include all details from that too where possible - so you could include an axis that said "commercial support available" STM = No, XTS = yes and so on. > Needs experimentation to see what will work best. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 3 10:27:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 3 Jul 2015 10:27:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086334#comment-13086334 ] Michael Musgrove commented on JBTM-2440: ---------------------------------------- The [IBM manual | http://download.boulder.ibm.com/ibmdl/pub/software/dw/jdk/docs/java8/lnx/en/sdkandruntimeguide.lnx.80_8.0.pdf] says bq. The Attach API can be enabled by setting the com.ibm.tools.attach.enable system property to the value yes; I tried this but tests marked up with the @BMUnitRunner annotation still fail with the error JVMTI_ERROR_NOT_AVAILABLE I tried enabling it in the pom via: * systemPropertyVariables; * systemProperties; and * -Dcom.ibm.tools.attach.enable=yes none of which work. I am going to work around the issue using an ibm jdk profile that disables byteman tests. > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 03:30:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 6 Jul 2015 03:30:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2440: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/876, https://github.com/jbosstm/narayana/pull/882 (was: https://github.com/jbosstm/narayana/pull/876) > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 08:54:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 6 Jul 2015 08:54:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2444: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ > --------------------------------------------------------------------------------------------- > > Key: JBTM-2444 > URL: https://issues.jboss.org/browse/JBTM-2444 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > {code} > Running org.jboss.narayana.quickstarts.jta.TestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE! > Results : > Tests in error: > org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 > {code} > The log file says: > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1] > Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}} > 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) > ... 96 more > {code} > Which leads me to believe it is likely due to the parsing in test-jms.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 09:00:04 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 6 Jul 2015 09:00:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2450: ------------------------------------- Summary: OracleXADataSource not found in jdbc test Key: JBTM-2450 URL: https://issues.jboss.org/browse/JBTM-2450 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Reporter: Gytis Trikleris Assignee: Tom Jenkinson Priority: Minor Fix For: 5.next {code} Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) Running com.hp.mwtests.ts.jdbc.utils.JNDISetup Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! java.lang.ClassNotFoundException: TODO at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 09:00:04 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 6 Jul 2015 09:00:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086746#comment-13086746 ] Gytis Trikleris commented on JBTM-2450: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana-catelyn/952 > OracleXADataSource not found in jdbc test > ----------------------------------------- > > Key: JBTM-2450 > URL: https://issues.jboss.org/browse/JBTM-2450 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > {code} > Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! > java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) > Running com.hp.mwtests.ts.jdbc.utils.JNDISetup > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! > java.lang.ClassNotFoundException: TODO > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 09:54:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 09:54:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086765#comment-13086765 ] Tom Jenkinson commented on JBTM-2450: ------------------------------------- As I didn't change anything here I am wondering if this is caused by some of Mikes changes to the poms in that build http://albany.eng.hst.ams2.redhat.com/job/narayana-catelyn/952/changes I am re-running the build to check if it fails again, if not I might need @mmusgrov to help. > OracleXADataSource not found in jdbc test > ----------------------------------------- > > Key: JBTM-2450 > URL: https://issues.jboss.org/browse/JBTM-2450 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > {code} > Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! > java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) > Running com.hp.mwtests.ts.jdbc.utils.JNDISetup > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! > java.lang.ClassNotFoundException: TODO > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 09:54:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 09:54:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086765#comment-13086765 ] Tom Jenkinson edited comment on JBTM-2450 at 7/6/15 9:54 AM: ------------------------------------------------------------- As I didn't change anything here I am wondering if this is caused by some of Mikes changes to the poms in that build http://albany.eng.hst.ams2.redhat.com/job/narayana-catelyn/952/changes I am re-running the build to check if it fails again, if not I might need [~mmusgrov] to help. was (Author: tomjenkinson): As I didn't change anything here I am wondering if this is caused by some of Mikes changes to the poms in that build http://albany.eng.hst.ams2.redhat.com/job/narayana-catelyn/952/changes I am re-running the build to check if it fails again, if not I might need @mmusgrov to help. > OracleXADataSource not found in jdbc test > ----------------------------------------- > > Key: JBTM-2450 > URL: https://issues.jboss.org/browse/JBTM-2450 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > {code} > Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! > java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) > Running com.hp.mwtests.ts.jdbc.utils.JNDISetup > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! > java.lang.ClassNotFoundException: TODO > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 09:56:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 6 Jul 2015 09:56:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086767#comment-13086767 ] Michael Musgrove commented on JBTM-2450: ---------------------------------------- I agree - it is probably related. I am investigating > OracleXADataSource not found in jdbc test > ----------------------------------------- > > Key: JBTM-2450 > URL: https://issues.jboss.org/browse/JBTM-2450 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > {code} > Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! > java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) > Running com.hp.mwtests.ts.jdbc.utils.JNDISetup > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! > java.lang.ClassNotFoundException: TODO > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 09:59:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 09:59:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2451) BlackTie quickstarts failing to deploy to WildFly In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2451: ----------------------------------- Summary: BlackTie quickstarts failing to deploy to WildFly Key: JBTM-2451 URL: https://issues.jboss.org/browse/JBTM-2451 Project: JBoss Transaction Manager Issue Type: Feature Request Components: BlackTie, Demonstrator Reporter: Tom Jenkinson Assignee: Amos Feng Priority: Blocker Fix For: 5.next Needs investigation: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quickstarts-catelyn/798/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:00:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:00:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2451) BlackTie quickstarts failing to deploy to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086771#comment-13086771 ] Tom Jenkinson commented on JBTM-2451: ------------------------------------- I assume the solution is related to JBTM-2444 > BlackTie quickstarts failing to deploy to WildFly > ------------------------------------------------- > > Key: JBTM-2451 > URL: https://issues.jboss.org/browse/JBTM-2451 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Needs investigation: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quickstarts-catelyn/798/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:05:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:05:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2451) BlackTie quickstarts failing to deploy to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2451: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/143 > BlackTie quickstarts failing to deploy to WildFly > ------------------------------------------------- > > Key: JBTM-2451 > URL: https://issues.jboss.org/browse/JBTM-2451 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Needs investigation: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quickstarts-catelyn/798/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:08:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:08:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2360) QA suite failure: CrashRecovery05_2_Test045 Fail In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2360: -------------------------------- Summary: QA suite failure: CrashRecovery05_2_Test045 Fail (was: QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2 crashrecovery05_2 CrashRecovery05_2_Test045 Fail) > QA suite failure: CrashRecovery05_2_Test045 Fail > ------------------------------------------------ > > Key: JBTM-2360 > URL: https://issues.jboss.org/browse/JBTM-2360 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/779/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux/ > I had a look and there are some messages that suggest that the connection was broken. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:08:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:08:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2405) QA suite failure: CrashRecovery05_1 Test04 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2405: -------------------------------- Summary: QA suite failure: CrashRecovery05_1 Test04 (was: QA suite test failure: CrashRecovery05_1 Test04) > QA suite failure: CrashRecovery05_1 Test04 > ------------------------------------------ > > Key: JBTM-2405 > URL: https://issues.jboss.org/browse/JBTM-2405 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/830/PROFILE=QA_JTS_JACORB,jdk=jdk8.latest,label=linux/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:09:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 6 Jul 2015 10:09:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reassigned JBTM-2450: -------------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > OracleXADataSource not found in jdbc test > ----------------------------------------- > > Key: JBTM-2450 > URL: https://issues.jboss.org/browse/JBTM-2450 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > {code} > Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! > java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) > Running com.hp.mwtests.ts.jdbc.utils.JNDISetup > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! > java.lang.ClassNotFoundException: TODO > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:10:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:10:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2300) XATMI implemenation tests failed due to HornetQ disconnection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2300. ------------------------------- Fix Version/s: (was: 5.later) Resolution: Out of Date WildFly have moved to using ActiveMQ - reopen if issue still exists > XATMI implemenation tests failed due to HornetQ disconnection > ------------------------------------------------------------- > > Key: JBTM-2300 > URL: https://issues.jboss.org/browse/JBTM-2300 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/753/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el7/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:11:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:11:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2447) BlackTie test failure - requires investigation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2447: -------------------------------- Summary: BlackTie test failure - requires investigation (was: BlackTie build failure - requires investigation) > BlackTie test failure - requires investigation > ---------------------------------------------- > > Key: JBTM-2447 > URL: https://issues.jboss.org/browse/JBTM-2447 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > > http://albany.eng.hst.ams2.redhat.com/job/narayana/745/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el6/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:12:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:12:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2447) BlackTie test failure - requires investigation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2447. ------------------------------- Resolution: Out of Date Looks like a wildfly deployment scanner issue. Please consider opening a WFLY issue if still exists > BlackTie test failure - requires investigation > ---------------------------------------------- > > Key: JBTM-2447 > URL: https://issues.jboss.org/browse/JBTM-2447 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > > http://albany.eng.hst.ams2.redhat.com/job/narayana/745/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el6/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:13:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:13:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2447) BlackTie test failure - requires investigation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086779#comment-13086779 ] Tom Jenkinson commented on JBTM-2447: ------------------------------------- {code} [exec] --16720:1:mallocfr newSuperblock at 0x86950000 (pszB 1048560) owner VALGRIND/exectxt 11:04:53,162 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0012: Scan of /home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk7.latest/label/linux32el6/blacktie/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/deployments threw Exception: java.lang.RuntimeException: WFLYDS0032: Failed to list files in directory /home/hudson/workspace/narayana/PROFILE/BLACKTIE/jdk/jdk7.latest/label/linux32el6/blacktie/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/deployments. Check that the contents of the directory are readable. at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.listDirectoryChildren(FileSystemDeploymentService.java:1131) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scanDirectory(FileSystemDeploymentService.java:633) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:453) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:375) at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentScanRunnable.run(FileSystemDeploymentService.java:155) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) at org.jboss.threads.JBossThread.run(JBossThread.java:320)  [exec] --16720:1:syswrap- thread_wrapper(tid=3): exit [exec] --16720:1:syswrap- run_a_thread_NORETURN(tid=3): post-thread_wrapper [exec] --16720:1:syswrap- run_a_thread_NORETURN(tid=3): not last one standing [exec] .2015-02-12 11:04:55,350 [0x4ed7d40] INFO (AtmiBrokerLogc :60 ) - TestTxTPCall::setUp [exec] 2015-02-12 11:04:55,382 [0x4ed7d40] ERROR (AtmiBrokerEnvParser :49 ) - Failed to open blacktie schema: ../cxx/compile//btconfig.xsd [exec] 2015-02-12 11:04:55,398 [0x4ed7d40] ERROR (AtmiBrokerEnv :421 ) - can not parse ./btconfig.xml [exec] 2015-02-12 11:04:55,474 [0x4ed7d40] ERROR (AtmiBrokerServer :247 ) - Server startup failed [exec] 2015-02-12 11:04:55,488 [0x4ed7d40] FATAL (AtmiBrokerServer :254 ) - serverinit failed [exec] F2015-02-12 11:04:55,558 [0x4ed7d40] INFO (AtmiBrokerLogc :60 ) - TestTxTPCall::tearDown {code} > BlackTie test failure - requires investigation > ---------------------------------------------- > > Key: JBTM-2447 > URL: https://issues.jboss.org/browse/JBTM-2447 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > > http://albany.eng.hst.ams2.redhat.com/job/narayana/745/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el6/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:14:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:14:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086782#comment-13086782 ] Tom Jenkinson commented on JBTM-2450: ------------------------------------- Thanks Mike - adding for completeness that its reproducible: http://albany.eng.hst.ams2.redhat.com/job/narayana-catelyn/953/ > OracleXADataSource not found in jdbc test > ----------------------------------------- > > Key: JBTM-2450 > URL: https://issues.jboss.org/browse/JBTM-2450 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > {code} > Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! > java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) > Running com.hp.mwtests.ts.jdbc.utils.JNDISetup > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! > java.lang.ClassNotFoundException: TODO > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:15:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:15:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2360) QA suite failure: CrashRecovery05_2_Test045 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2360: -------------------------------- Summary: QA suite failure: CrashRecovery05_2_Test045 (was: QA suite failure: CrashRecovery05_2_Test045 Fail) > QA suite failure: CrashRecovery05_2_Test045 > ------------------------------------------- > > Key: JBTM-2360 > URL: https://issues.jboss.org/browse/JBTM-2360 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/779/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux/ > I had a look and there are some messages that suggest that the connection was broken. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:16:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:16:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2405) QA suite failure: CrashRecovery05_1_Test04 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2405: -------------------------------- Summary: QA suite failure: CrashRecovery05_1_Test04 (was: QA suite failure: CrashRecovery05_1 Test04) > QA suite failure: CrashRecovery05_1_Test04 > ------------------------------------------ > > Key: JBTM-2405 > URL: https://issues.jboss.org/browse/JBTM-2405 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/830/PROFILE=QA_JTS_JACORB,jdk=jdk8.latest,label=linux/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:25:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:25:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2360) QA suite failure: CrashRecovery05_2_Test045 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2360: -------------------------------- Priority: Minor (was: Major) > QA suite failure: CrashRecovery05_2_Test045 > ------------------------------------------- > > Key: JBTM-2360 > URL: https://issues.jboss.org/browse/JBTM-2360 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/779/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux/ > I had a look and there are some messages that suggest that the connection was broken. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:30:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:30:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2450: -------------------------------- Priority: Blocker (was: Minor) > OracleXADataSource not found in jdbc test > ----------------------------------------- > > Key: JBTM-2450 > URL: https://issues.jboss.org/browse/JBTM-2450 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > {code} > Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! > java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) > Running com.hp.mwtests.ts.jdbc.utils.JNDISetup > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! > java.lang.ClassNotFoundException: TODO > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:31:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:31:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2439) XATMI CSTest failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086794#comment-13086794 ] Tom Jenkinson commented on JBTM-2439: ------------------------------------- Hi [~zhfeng] - please can you update the issue with more details as to the proposed cause? If you feel it might be HornetQ related it is fine to close this as "Out of Date" as they have upgraded to ActiveMQ > XATMI CSTest failed > ------------------- > > Key: JBTM-2439 > URL: https://issues.jboss.org/browse/JBTM-2439 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/863 > {code} > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest > 20:00:30,081 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:30,372 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:30,597 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:41,182 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:41,531 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:41,788 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:44,655 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:55163) Caught an exception: null: java.lang.NullPointerException > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) > at java.lang.Thread.run(Thread.java:744) > 20:00:54,478 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:54,749 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:55,057 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:05,617 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:05,865 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:06,103 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:16,623 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:16,900 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:17,169 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:38,604 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service pending for .testsui1 as consumer count is 0, will check again in 30000ms > 20:02:08,542 WARN [org.jboss.as.ejb3] (EJB default - 3) WFLYEJB0043: A previous execution of timer [id=ec057768-85a2-4e35-ac04-cebbf53ce28e timedObjectId=blacktie-admin-services-ear-5.1.2.Final-SNAPSHOT.blacktie-admin-services-5.1.2.Final-SNAPSHOT.QueueReaperBean auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 3aff5ed3 initialExpiration=Wed Jun 17 18:46:38 BST 2015 intervalDuration(in milli sec)=30000 nextExpiration=Wed Jun 17 20:02:08 BST 2015 timerState=IN_TIMEOUT info=queue reaper] is still in progress, skipping this overlapping scheduled execution at: Wed Jun 17 20:02:08 BST 2015. > 20:02:08,781 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service .testsui1 for consumer is 0 > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:02:23,382 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 5ec536b5 > 20:02:23,550 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:02:23,551 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:02:23,552 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 7642baf0 > 20:02:23,625 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:02:23,626 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:02:23,627 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2ecad1c6 > 20:02:23,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:02:23,743 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:02:23,744 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:02:23,745 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2684d6dd > 20:02:57,766 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 13: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 13 reason: Did not receive a message > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.SocketReceiverImpl.receive(SocketReceiverImpl.java:139) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.receive(ConnectionImpl.java:533) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:183) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:350) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,814 ERROR [org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl] (Thread-36 (HornetQ-client-global-threads-1622216728)) queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > 20:02:57,815 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 6: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 6 reason: queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl.send(StompSenderImpl.java:144) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpacall(ConnectionImpl.java:260) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:181) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:354) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,852 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 127) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,744 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:06,274 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:16,874 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:17,135 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:17,436 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:40,042 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:40,430 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:40,688 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:51,251 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:51,561 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:51,815 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:02,497 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:02,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:02,980 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:13,462 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:13,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:13,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:24,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:24,846 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:25,216 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:33,824 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:04:33,825 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:04:33,825 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 32f599dc > 20:04:33,910 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:04:33,911 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:04:33,911 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4a493aa5 > 20:04:33,989 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:04:33,990 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:04:33,990 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4afb2f0f > 20:04:34,065 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:04:34,098 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:04:34,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:04:34,100 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2d1d86a > 20:04:35,818 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:36,102 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:36,371 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:46,960 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:47,211 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:47,475 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:58,025 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:58,376 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:58,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 279.072 sec <<< FAILURE! > test_211(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest) Time elapsed: 101.173 sec <<< FAILURE! > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSControl.runTest(CSControl.java:153) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest.test_211(CSTest.java:27) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:32:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:32:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086796#comment-13086796 ] Tom Jenkinson commented on JBTM-2416: ------------------------------------- Hi [~zhfeng], did you manage to work out the cause of this issue yet? > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:33:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:33:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086798#comment-13086798 ] Tom Jenkinson commented on JBTM-2433: ------------------------------------- Hi [~gytis] - please can you update this issue with initial analysis? > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/858/PROFILE=XTS,jdk=jdk8.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:47:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:47:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2451) BlackTie quickstarts failing to deploy to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2451: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > BlackTie quickstarts failing to deploy to WildFly > ------------------------------------------------- > > Key: JBTM-2451 > URL: https://issues.jboss.org/browse/JBTM-2451 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Needs investigation: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quickstarts-catelyn/798/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:47:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:47:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2451) BlackTie quickstarts failing to deploy to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2451: ----------------------------------- Assignee: Tom Jenkinson (was: Amos Feng) > BlackTie quickstarts failing to deploy to WildFly > ------------------------------------------------- > > Key: JBTM-2451 > URL: https://issues.jboss.org/browse/JBTM-2451 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > Needs investigation: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quickstarts-catelyn/798/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:55:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:55:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2442) Update to use activemq-messaging subsystem in the standalone-blacktie.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2442: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update to use activemq-messaging subsystem in the standalone-blacktie.xml > ------------------------------------------------------------------------- > > Key: JBTM-2442 > URL: https://issues.jboss.org/browse/JBTM-2442 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration, BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > currently the wildfly 10.0.0.Alpha4 changes to use the activemq-messaging and the default resource adapter of the MDB changed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:55:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:55:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2446) Blacktie jatmibroker-xatmi hang with "javax.naming.NameNotFoundException: ConnectionFactory" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2446. --------------------------------- Resolution: Done > Blacktie jatmibroker-xatmi hang with "javax.naming.NameNotFoundException: ConnectionFactory" > -------------------------------------------------------------------------------------------- > > Key: JBTM-2446 > URL: https://issues.jboss.org/browse/JBTM-2446 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux64el6/872/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:57:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1679) Make @CompensationScoped beans available during recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086815#comment-13086815 ] Tom Jenkinson commented on JBTM-1679: ------------------------------------- How is this different to JBTM-1107? Should we close this as a duplicate? > Make @CompensationScoped beans available during recovery > -------------------------------------------------------- > > Key: JBTM-1679 > URL: https://issues.jboss.org/browse/JBTM-1679 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 10:57:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 6 Jul 2015 10:57:03 -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:comment-tabpanel&focusedCommentId=13086816#comment-13086816 ] Tom Jenkinson commented on JBTM-1107: ------------------------------------- We need a description for what this entails. It looks like its partially duplicated by JBTM-1679 > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 11:35:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 6 Jul 2015 11:35:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2433: ---------------------------------- Description: It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/858/PROFILE=XTS,jdk=jdk8.latest,label=linux {code} ------------------------------------------------------------------------------- Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! com.arjuna.wst.TransactionRolledBackException: null at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) {code} was: http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/858/PROFILE=XTS,jdk=jdk8.latest,label=linux {code} ------------------------------------------------------------------------------- Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! com.arjuna.wst.TransactionRolledBackException: null at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) {code} > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/858/PROFILE=XTS,jdk=jdk8.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 11:43:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 6 Jul 2015 11:43:03 -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: ---------------------------------- Description: 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. > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 11:44:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 6 Jul 2015 11:44:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1679) Make @CompensationScoped beans available during recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086831#comment-13086831 ] Gytis Trikleris commented on JBTM-1679: --------------------------------------- I think we could close it, since it is part of JBTM-1107. Or we could make it a subtask. > Make @CompensationScoped beans available during recovery > -------------------------------------------------------- > > Key: JBTM-1679 > URL: https://issues.jboss.org/browse/JBTM-1679 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 20:20:03 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 6 Jul 2015 20:20:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086946#comment-13086946 ] Amos Feng commented on JBTM-2416: --------------------------------- I think it might be related to the arquillian and it would be safe to close. > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 6 20:23:02 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 6 Jul 2015 20:23:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2439) XATMI CSTest failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086948#comment-13086948 ] Amos Feng commented on JBTM-2439: --------------------------------- OK, I will investigate it. > XATMI CSTest failed > ------------------- > > Key: JBTM-2439 > URL: https://issues.jboss.org/browse/JBTM-2439 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/863 > {code} > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest > 20:00:30,081 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:30,372 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:30,597 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:41,182 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:41,531 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:41,788 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:44,655 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:55163) Caught an exception: null: java.lang.NullPointerException > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) > at java.lang.Thread.run(Thread.java:744) > 20:00:54,478 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:54,749 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:55,057 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:05,617 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:05,865 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:06,103 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:16,623 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:16,900 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:17,169 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:38,604 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service pending for .testsui1 as consumer count is 0, will check again in 30000ms > 20:02:08,542 WARN [org.jboss.as.ejb3] (EJB default - 3) WFLYEJB0043: A previous execution of timer [id=ec057768-85a2-4e35-ac04-cebbf53ce28e timedObjectId=blacktie-admin-services-ear-5.1.2.Final-SNAPSHOT.blacktie-admin-services-5.1.2.Final-SNAPSHOT.QueueReaperBean auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 3aff5ed3 initialExpiration=Wed Jun 17 18:46:38 BST 2015 intervalDuration(in milli sec)=30000 nextExpiration=Wed Jun 17 20:02:08 BST 2015 timerState=IN_TIMEOUT info=queue reaper] is still in progress, skipping this overlapping scheduled execution at: Wed Jun 17 20:02:08 BST 2015. > 20:02:08,781 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service .testsui1 for consumer is 0 > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:02:23,382 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 5ec536b5 > 20:02:23,550 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:02:23,551 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:02:23,552 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 7642baf0 > 20:02:23,625 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:02:23,626 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:02:23,627 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2ecad1c6 > 20:02:23,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:02:23,743 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:02:23,744 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:02:23,745 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2684d6dd > 20:02:57,766 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 13: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 13 reason: Did not receive a message > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.SocketReceiverImpl.receive(SocketReceiverImpl.java:139) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.receive(ConnectionImpl.java:533) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:183) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:350) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,814 ERROR [org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl] (Thread-36 (HornetQ-client-global-threads-1622216728)) queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > 20:02:57,815 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 6: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 6 reason: queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl.send(StompSenderImpl.java:144) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpacall(ConnectionImpl.java:260) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:181) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:354) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,852 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 127) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,744 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:06,274 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:16,874 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:17,135 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:17,436 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:40,042 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:40,430 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:40,688 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:51,251 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:51,561 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:51,815 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:02,497 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:02,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:02,980 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:13,462 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:13,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:13,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:24,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:24,846 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:25,216 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:33,824 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:04:33,825 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:04:33,825 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 32f599dc > 20:04:33,910 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:04:33,911 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:04:33,911 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4a493aa5 > 20:04:33,989 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:04:33,990 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:04:33,990 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4afb2f0f > 20:04:34,065 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:04:34,098 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:04:34,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:04:34,100 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2d1d86a > 20:04:35,818 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:36,102 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:36,371 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:46,960 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:47,211 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:47,475 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:58,025 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:58,376 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:58,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 279.072 sec <<< FAILURE! > test_211(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest) Time elapsed: 101.173 sec <<< FAILURE! > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSControl.runTest(CSControl.java:153) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest.test_211(CSTest.java:27) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 04:37:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 04:37:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087075#comment-13087075 ] Tom Jenkinson commented on JBTM-2416: ------------------------------------- OK, lets do that then. > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 04:38:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 04:38:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1679) Make @CompensationScoped beans available during recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087079#comment-13087079 ] Tom Jenkinson commented on JBTM-1679: ------------------------------------- I think we should just close it and add it into the details for JBTM-1107 as it seems somewhat intrinsic to the behaviour. If you agree, please can you make the change? > Make @CompensationScoped beans available during recovery > -------------------------------------------------------- > > Key: JBTM-1679 > URL: https://issues.jboss.org/browse/JBTM-1679 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 04:44:04 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 7 Jul 2015 04:44:04 -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: ---------------------------------- Description: 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. was: 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. > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > 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.3.15#6346) From issues at jboss.org Tue Jul 7 04:45:05 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 7 Jul 2015 04:45:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1679) Make @CompensationScoped beans available during recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-1679. --------------------------------- Fix Version/s: (was: 5.next) Resolution: Duplicate Issue > Make @CompensationScoped beans available during recovery > -------------------------------------------------------- > > Key: JBTM-1679 > URL: https://issues.jboss.org/browse/JBTM-1679 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 04:55:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 04:55:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2433: -------------------------------- Comment: was deleted (was: Hi [~gytis] - please can you update this issue with initial analysis?) > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/858/PROFILE=XTS,jdk=jdk8.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:00:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 05:00:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2452: ----------------------------------- Summary: External Queues BlackTie quickstart no longer works with Artemis Key: JBTM-2452 URL: https://issues.jboss.org/browse/JBTM-2452 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie, Demonstrator Reporter: Tom Jenkinson Assignee: Amos Feng Priority: Blocker Current failures: http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console This is currently preventing release. {code} [exec] /home/hudson/workspace/narayana-quickstarts/blacktie [exec] Quickstart: Running externally managed queue quickstart [exec] [exec] BUILD SUCCESSFUL [exec] Total time: 3 seconds [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) [exec] at java.lang.Thread.run(Thread.java:744) [exec] [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 [exec] Unable to queue all messages {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:03:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 05:03:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087135#comment-13087135 ] Tom Jenkinson commented on JBTM-2452: ------------------------------------- I wonder if it could be related to JBTM-2436 somehow due to the lack of being able to use JNDI - what do you think [~gytis]? > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:06:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 05:06:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2452: -------------------------------- Fix Version/s: 5.next > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:19:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 7 Jul 2015 05:19:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087151#comment-13087151 ] Gytis Trikleris commented on JBTM-2452: --------------------------------------- It is the same exception, but it is not very uncommon I think. Is that service running on the unmanaged thread? > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:23:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 05:23:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087155#comment-13087155 ] Tom Jenkinson commented on JBTM-2452: ------------------------------------- I expect so as it is StompConnect - do you think [~zhfeng] should try using the ManagedThreadFactory? The server socket is spawned with "new Thread": https://github.com/jbosstm/narayana/blob/master/blacktie/wildfly-blacktie/subsystem/src/main/java/org/codehaus/stomp/tcp/TcpTransportServer.java#L123 The request process handlers are spawned with "new Thread" also: https://github.com/jbosstm/narayana/blob/master/blacktie/wildfly-blacktie/subsystem/src/main/java/org/codehaus/stomp/tcp/TcpTransport.java#L134 > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:31:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 7 Jul 2015 05:31:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087159#comment-13087159 ] Gytis Trikleris commented on JBTM-2452: --------------------------------------- I'm not sure. Somebody on WildFly dev list said that it's a bad idea to use ManagedThreadFactory in the subsystem, because of a hard dependency. But I still don't have other solution for this. Is it possible to get that queue is any other way? > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:32:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 7 Jul 2015 05:32:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087160#comment-13087160 ] Gytis Trikleris commented on JBTM-2452: --------------------------------------- They said that ManagedThreadFactory and JNDI are application tools. In subsystems we should use services. > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:35:02 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 7 Jul 2015 05:35:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087161#comment-13087161 ] Amos Feng commented on JBTM-2452: --------------------------------- I will manage to reproducer. It might be a configuration error of queue that has not deployed the "queue/BTR_TestOne". > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:45:02 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 7 Jul 2015 05:45:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087163#comment-13087163 ] Amos Feng commented on JBTM-2452: --------------------------------- OK, I can confirm this issue is related to the configuration of queue. It needs to update https://github.com/jbosstm/quickstart/blob/master/blacktie/test/initializeBlackTie.xml > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 05:54:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 05:54:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087164#comment-13087164 ] Tom Jenkinson commented on JBTM-2452: ------------------------------------- Great - thanks Amos. To Gytis' point, StompConnect is deployed as a .war but it looks like Amos has a handle on it anyway - thanks. > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 07:27:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 07:27:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087237#comment-13087237 ] Tom Jenkinson commented on JBTM-2452: ------------------------------------- Hi [~zhfeng], do you think you will be able to get a fix today so I can do a release? I don't mind trying to implement the fix if you can tell me what to do with initializeBlacktie.xml. > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 08:11:04 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 7 Jul 2015 08:11:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087275#comment-13087275 ] Amos Feng commented on JBTM-2452: --------------------------------- Thanks Tom - It looks like the similar changes with https://github.com/jbosstm/narayana/blob/master/blacktie/scripts/hudson/initializeJBoss.xml you need to update the of jms-destinations and security-setting of queues. > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 08:13:05 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 7 Jul 2015 08:13:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2453) Release the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: Amos Feng created JBTM-2453: ------------------------------- Summary: Release the narayana-osgi-jta bundle Key: JBTM-2453 URL: https://issues.jboss.org/browse/JBTM-2453 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Reporter: Amos Feng Assignee: Tom Jenkinson Fix For: 5.next for KARAF-3749, they are looking for the narayana osgi jta bundle. I think we have not released it to the maven repos and it could add to the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 09:29:02 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 7 Jul 2015 09:29:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng closed JBTM-2416. --------------------------- Resolution: Out of Date > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 09:50:03 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 7 Jul 2015 09:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2452: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/144 > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 10:04:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 10:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2436) Use ManagedThreadFactory, if available, to create PeriodicRecovery thread In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2436: -------------------------------- Fix Version/s: (was: 5.next) > Use ManagedThreadFactory, if available, to create PeriodicRecovery thread > ------------------------------------------------------------------------- > > Key: JBTM-2436 > URL: https://issues.jboss.org/browse/JBTM-2436 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 10:04:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 10:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2439) XATMI CSTest failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2439: -------------------------------- Fix Version/s: (was: 5.next) > XATMI CSTest failed > ------------------- > > Key: JBTM-2439 > URL: https://issues.jboss.org/browse/JBTM-2439 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/863 > {code} > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest > 20:00:30,081 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:30,372 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:30,597 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:41,182 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:41,531 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:41,788 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:44,655 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:55163) Caught an exception: null: java.lang.NullPointerException > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) > at java.lang.Thread.run(Thread.java:744) > 20:00:54,478 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:54,749 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:55,057 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:05,617 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:05,865 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:06,103 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:16,623 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:16,900 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:17,169 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:38,604 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service pending for .testsui1 as consumer count is 0, will check again in 30000ms > 20:02:08,542 WARN [org.jboss.as.ejb3] (EJB default - 3) WFLYEJB0043: A previous execution of timer [id=ec057768-85a2-4e35-ac04-cebbf53ce28e timedObjectId=blacktie-admin-services-ear-5.1.2.Final-SNAPSHOT.blacktie-admin-services-5.1.2.Final-SNAPSHOT.QueueReaperBean auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 3aff5ed3 initialExpiration=Wed Jun 17 18:46:38 BST 2015 intervalDuration(in milli sec)=30000 nextExpiration=Wed Jun 17 20:02:08 BST 2015 timerState=IN_TIMEOUT info=queue reaper] is still in progress, skipping this overlapping scheduled execution at: Wed Jun 17 20:02:08 BST 2015. > 20:02:08,781 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service .testsui1 for consumer is 0 > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:02:23,382 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 5ec536b5 > 20:02:23,550 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:02:23,551 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:02:23,552 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 7642baf0 > 20:02:23,625 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:02:23,626 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:02:23,627 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2ecad1c6 > 20:02:23,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:02:23,743 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:02:23,744 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:02:23,745 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2684d6dd > 20:02:57,766 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 13: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 13 reason: Did not receive a message > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.SocketReceiverImpl.receive(SocketReceiverImpl.java:139) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.receive(ConnectionImpl.java:533) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:183) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:350) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,814 ERROR [org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl] (Thread-36 (HornetQ-client-global-threads-1622216728)) queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > 20:02:57,815 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 6: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 6 reason: queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl.send(StompSenderImpl.java:144) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpacall(ConnectionImpl.java:260) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:181) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:354) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,852 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 127) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,744 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:06,274 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:16,874 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:17,135 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:17,436 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:40,042 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:40,430 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:40,688 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:51,251 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:51,561 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:51,815 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:02,497 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:02,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:02,980 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:13,462 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:13,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:13,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:24,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:24,846 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:25,216 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:33,824 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:04:33,825 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:04:33,825 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 32f599dc > 20:04:33,910 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:04:33,911 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:04:33,911 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4a493aa5 > 20:04:33,989 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:04:33,990 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:04:33,990 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4afb2f0f > 20:04:34,065 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:04:34,098 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:04:34,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:04:34,100 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2d1d86a > 20:04:35,818 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:36,102 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:36,371 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:46,960 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:47,211 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:47,475 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:58,025 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:58,376 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:58,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 279.072 sec <<< FAILURE! > test_211(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest) Time elapsed: 101.173 sec <<< FAILURE! > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSControl.runTest(CSControl.java:153) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest.test_211(CSTest.java:27) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 10:15:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 10:15:09 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2453) Release the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2453: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/884 > Release the narayana-osgi-jta bundle > ------------------------------------ > > Key: JBTM-2453 > URL: https://issues.jboss.org/browse/JBTM-2453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.next > > > for KARAF-3749, they are looking for the narayana osgi jta bundle. I think we have not released it to the maven repos and it could add to the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 10:15:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 10:15:09 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2453) Release the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2453: -------------------------------- Priority: Blocker (was: Major) > Release the narayana-osgi-jta bundle > ------------------------------------ > > Key: JBTM-2453 > URL: https://issues.jboss.org/browse/JBTM-2453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > for KARAF-3749, they are looking for the narayana osgi jta bundle. I think we have not released it to the maven repos and it could add to the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 10:38:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 10:38:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2439) XATMI CSTest failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2439: -------------------------------- Fix Version/s: 5.later > XATMI CSTest failed > ------------------- > > Key: JBTM-2439 > URL: https://issues.jboss.org/browse/JBTM-2439 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/863 > {code} > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest > 20:00:30,081 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:30,372 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:30,597 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:41,182 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:41,531 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:41,788 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:44,655 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:55163) Caught an exception: null: java.lang.NullPointerException > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) > at java.lang.Thread.run(Thread.java:744) > 20:00:54,478 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:54,749 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:55,057 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:05,617 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:05,865 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:06,103 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:16,623 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:16,900 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:17,169 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:38,604 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service pending for .testsui1 as consumer count is 0, will check again in 30000ms > 20:02:08,542 WARN [org.jboss.as.ejb3] (EJB default - 3) WFLYEJB0043: A previous execution of timer [id=ec057768-85a2-4e35-ac04-cebbf53ce28e timedObjectId=blacktie-admin-services-ear-5.1.2.Final-SNAPSHOT.blacktie-admin-services-5.1.2.Final-SNAPSHOT.QueueReaperBean auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 3aff5ed3 initialExpiration=Wed Jun 17 18:46:38 BST 2015 intervalDuration(in milli sec)=30000 nextExpiration=Wed Jun 17 20:02:08 BST 2015 timerState=IN_TIMEOUT info=queue reaper] is still in progress, skipping this overlapping scheduled execution at: Wed Jun 17 20:02:08 BST 2015. > 20:02:08,781 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service .testsui1 for consumer is 0 > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:02:23,382 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 5ec536b5 > 20:02:23,550 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:02:23,551 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:02:23,552 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 7642baf0 > 20:02:23,625 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:02:23,626 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:02:23,627 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2ecad1c6 > 20:02:23,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:02:23,743 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:02:23,744 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:02:23,745 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2684d6dd > 20:02:57,766 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 13: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 13 reason: Did not receive a message > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.SocketReceiverImpl.receive(SocketReceiverImpl.java:139) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.receive(ConnectionImpl.java:533) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:183) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:350) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,814 ERROR [org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl] (Thread-36 (HornetQ-client-global-threads-1622216728)) queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > 20:02:57,815 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 6: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 6 reason: queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl.send(StompSenderImpl.java:144) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpacall(ConnectionImpl.java:260) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:181) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:354) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,852 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 127) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,744 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:06,274 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:16,874 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:17,135 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:17,436 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:40,042 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:40,430 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:40,688 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:51,251 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:51,561 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:51,815 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:02,497 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:02,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:02,980 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:13,462 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:13,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:13,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:24,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:24,846 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:25,216 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:33,824 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:04:33,825 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:04:33,825 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 32f599dc > 20:04:33,910 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:04:33,911 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:04:33,911 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4a493aa5 > 20:04:33,989 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:04:33,990 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:04:33,990 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4afb2f0f > 20:04:34,065 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:04:34,098 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:04:34,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:04:34,100 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2d1d86a > 20:04:35,818 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:36,102 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:36,371 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:46,960 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:47,211 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:47,475 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:58,025 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:58,376 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:58,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 279.072 sec <<< FAILURE! > test_211(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest) Time elapsed: 101.173 sec <<< FAILURE! > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSControl.runTest(CSControl.java:153) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest.test_211(CSTest.java:27) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 10:38:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 10:38:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2436) Use ManagedThreadFactory, if available, to create PeriodicRecovery thread In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2436: -------------------------------- Fix Version/s: 5.later > Use ManagedThreadFactory, if available, to create PeriodicRecovery thread > ------------------------------------------------------------------------- > > Key: JBTM-2436 > URL: https://issues.jboss.org/browse/JBTM-2436 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 10:44:02 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 7 Jul 2015 10:44:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2320) Implement getContainer on Container class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087447#comment-13087447 ] Mark Little commented on JBTM-2320: ----------------------------------- Added implementation. Not entirely sure how useful it will be, but let's wait and see. > Implement getContainer on Container class > ----------------------------------------- > > Key: JBTM-2320 > URL: https://issues.jboss.org/browse/JBTM-2320 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Mark Little > > Currently it's a null-op ... > public static final Container getContainer (Object proxy) > { > return null; > } -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 10:44:02 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 7 Jul 2015 10:44:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2320) Implement getContainer on Container class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2320. ----------------------------- Resolution: Done > Implement getContainer on Container class > ----------------------------------------- > > Key: JBTM-2320 > URL: https://issues.jboss.org/browse/JBTM-2320 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Mark Little > > Currently it's a null-op ... > public static final Container getContainer (Object proxy) > { > return null; > } -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 11:17:06 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 7 Jul 2015 11:17:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2450. ------------------------------------ Resolution: Done > OracleXADataSource not found in jdbc test > ----------------------------------------- > > Key: JBTM-2450 > URL: https://issues.jboss.org/browse/JBTM-2450 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > {code} > Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! > java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) > Running com.hp.mwtests.ts.jdbc.utils.JNDISetup > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! > java.lang.ClassNotFoundException: TODO > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:00:04 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 7 Jul 2015 12:00:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2454: -------------------------------------- Summary: Internal IBM J9 compiler error building XTS Key: JBTM-2454 URL: https://issues.jboss.org/browse/JBTM-2454 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later On lancel we get the following error. I am unable to reproduce it on my laptop. The compiler details are: {quote} java version "1.8.0" Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) J9VM - R28_Java8_SR1_20150410_1531_B243669 JIT - tr.r14.java_20150402_88976.03 GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS J9CL - 20150410_243669) JCL - 20150413_01 based on Oracle jdk8u45-b13 {quote} and the build error is: {quote} [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. java.lang.NullPointerException at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) at com.sun.tools.javac.main.Main.compile(Main.java:535) at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:17:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 12:17:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2453) Release the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2453: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Release the narayana-osgi-jta bundle > ------------------------------------ > > Key: JBTM-2453 > URL: https://issues.jboss.org/browse/JBTM-2453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > for KARAF-3749, they are looking for the narayana osgi jta bundle. I think we have not released it to the maven repos and it could add to the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:47:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 12:47:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087489#comment-13087489 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/114/ > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:48:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 12:48:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087490#comment-13087490 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- Is this repeatable? I have a scheduled a second build to check. If its repeatable we should raise the issue on http://java.sun.com/webapps/bugreport > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 12:54:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 12:54:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2452: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 13:01:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 13:01:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2454: -------------------------------- Affects Version/s: 5.next (was: 5.1.1) > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.next > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 13:02:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 13:02:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087495#comment-13087495 ] Tom Jenkinson commented on JBTM-2440: ------------------------------------- Hi Mike, Am I right in thinking that this should be fixed, but we still have JBTM-2454? If so it is worth closing this one. Thanks, Tom > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:20:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 14:20:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087527#comment-13087527 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- The module name sounds strange "disabled context propagation" - should this even be tested (or indeed, in the repo), [~gytis]? > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.next > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 14:21:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 7 Jul 2015 14:21:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087528#comment-13087528 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/115/ > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.next > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 18:29:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 7 Jul 2015 18:29:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2440: ----------------------------------- Fix Version/s: 5.later (was: 5.next) > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 18:30:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 7 Jul 2015 18:30:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087568#comment-13087568 ] Michael Musgrove commented on JBTM-2440: ---------------------------------------- This issue (JBTM-2440) is to capture the fact that the @BMUnitRunner annotation does not work with the IBM JVM. I don't know how to fix that so I have committed a workaround that adds a profile that disables byteman when running with the ibm compiler. Since I have provided a workaround my preference is to move "fix version" field to 5.later but leave the issue as unresolved. Whereas issue JBTM-2454 records the fact that the the localjunit-disabled-context-propagation-tests do not compile (at least on lancel) with the IBM compiler and is unrelated to the bug in the @BMUnitRunner annotation. Remark: the @BMUnitRunner annotation requires the ability to dynamically load an agent but it fails with the IBM JVM. The com.ibm.tools.attach.enable system property ought to allow that behaviour but it still fails and my personal feeling is that there is an issue with the annotation - but, as I say, it is a gut feeling since the annotation implementation seems to work with other JVMs > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 7 18:39:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 7 Jul 2015 18:39:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087568#comment-13087568 ] Michael Musgrove edited comment on JBTM-2440 at 7/7/15 6:38 PM: ---------------------------------------------------------------- This issue (JBTM-2440) is to capture the fact that the @BMUnitRunner annotation does not work with the IBM JVM. I don't know how to fix that so I have committed a workaround that adds a profile that disables byteman when running with the ibm JVM. Since I have provided a workaround my preference is to move "fix version" field to 5.later but leave the issue as unresolved. Whereas issue JBTM-2454 records the fact that the the localjunit-disabled-context-propagation-tests do not compile (at least on lancel) with the IBM compiler and is unrelated to the bug in the @BMUnitRunner annotation. Remark: the @BMUnitRunner annotation requires the ability to dynamically load an agent but it fails with the IBM JVM. The com.ibm.tools.attach.enable system property ought to allow that behaviour but it still fails and my personal feeling is that there is an issue with the annotation - but, as I say, it is a gut feeling since the annotation implementation seems to work with other JVMs was (Author: mmusgrov): This issue (JBTM-2440) is to capture the fact that the @BMUnitRunner annotation does not work with the IBM JVM. I don't know how to fix that so I have committed a workaround that adds a profile that disables byteman when running with the ibm compiler. Since I have provided a workaround my preference is to move "fix version" field to 5.later but leave the issue as unresolved. Whereas issue JBTM-2454 records the fact that the the localjunit-disabled-context-propagation-tests do not compile (at least on lancel) with the IBM compiler and is unrelated to the bug in the @BMUnitRunner annotation. Remark: the @BMUnitRunner annotation requires the ability to dynamically load an agent but it fails with the IBM JVM. The com.ibm.tools.attach.enable system property ought to allow that behaviour but it still fails and my personal feeling is that there is an issue with the annotation - but, as I say, it is a gut feeling since the annotation implementation seems to work with other JVMs > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 02:26:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 8 Jul 2015 02:26:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087602#comment-13087602 ] Gytis Trikleris commented on JBTM-2454: --------------------------------------- [~tomjenkinson], yes it's the tests module. It requires modified standalone-xts.xml, thus was extracted from other XTS junit tests. > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.next > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 02:28:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 8 Jul 2015 02:28:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087602#comment-13087602 ] Gytis Trikleris edited comment on JBTM-2454 at 7/8/15 2:27 AM: --------------------------------------------------------------- [~tomjenkinson], yes it's the tests module. It requires modified standalone-xts.xml, thus was extracted from other XTS junit tests. It only tests case where default-context-propagation in XTS is disabled. was (Author: gytis): [~tomjenkinson], yes it's the tests module. It requires modified standalone-xts.xml, thus was extracted from other XTS junit tests. > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.next > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 03:53:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 03:53:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087649#comment-13087649 ] Tom Jenkinson commented on JBTM-2440: ------------------------------------- Understood - works for me > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 04:03:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 04:03:03 -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 ] Tom Jenkinson updated JBTM-1107: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > 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.3.15#6346) From issues at jboss.org Wed Jul 8 04:04:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 04:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2444: -------------------------------- Issue Type: Bug (was: Feature Request) > jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ > --------------------------------------------------------------------------------------------- > > Key: JBTM-2444 > URL: https://issues.jboss.org/browse/JBTM-2444 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > {code} > Running org.jboss.narayana.quickstarts.jta.TestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE! > Results : > Tests in error: > org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 > {code} > The log file says: > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1] > Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}} > 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) > ... 96 more > {code} > Which leads me to believe it is likely due to the parsing in test-jms.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 04:04:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 04:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2451) BlackTie quickstarts failing to deploy to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2451: -------------------------------- Issue Type: Bug (was: Feature Request) > BlackTie quickstarts failing to deploy to WildFly > ------------------------------------------------- > > Key: JBTM-2451 > URL: https://issues.jboss.org/browse/JBTM-2451 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > Needs investigation: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quickstarts-catelyn/798/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 04:04:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 04:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2449: -------------------------------- Issue Type: Bug (was: Feature Request) > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 04:05:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 04:05:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2308: -------------------------------- Fix Version/s: (was: 5.1.0) > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.next > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:12:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:12:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2455) Re-enable generate of javadoc jar for narayana-full In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2455: ----------------------------------- Summary: Re-enable generate of javadoc jar for narayana-full Key: JBTM-2455 URL: https://issues.jboss.org/browse/JBTM-2455 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System, Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next It seems as part of JBTM-2395 I the generation of the uber javadoc jar was disabled. It should be re-enabled for the next release. Workaround was to mod the pom during the release. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:15:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:15:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2455) Re-enable generate of javadoc jar for narayana-full In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2455: -------------------------------- Description: It seems as part of JBTM-2395 it seems the generation of the uber javadoc jar was accidentally disabled. It should be re-enabled for the next release. Workaround was to mod the pom during the release. was: It seems as part of JBTM-2395 I the generation of the uber javadoc jar was disabled. It should be re-enabled for the next release. Workaround was to mod the pom during the release. > Re-enable generate of javadoc jar for narayana-full > --------------------------------------------------- > > Key: JBTM-2455 > URL: https://issues.jboss.org/browse/JBTM-2455 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It seems as part of JBTM-2395 it seems the generation of the uber javadoc jar was accidentally disabled. It should be re-enabled for the next release. > Workaround was to mod the pom during the release. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:15:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:15:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2455) Re-enable generate of javadoc jar for narayana-full In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087697#comment-13087697 ] Tom Jenkinson commented on JBTM-2455: ------------------------------------- https://github.com/jbosstm/narayana/pull/842/files#diff-a4d765d7e7369c1baa9122475a4c5adfR245 > Re-enable generate of javadoc jar for narayana-full > --------------------------------------------------- > > Key: JBTM-2455 > URL: https://issues.jboss.org/browse/JBTM-2455 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It seems as part of JBTM-2395 it seems the generation of the uber javadoc jar was accidentally disabled. It should be re-enabled for the next release. > Workaround was to mod the pom during the release. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:16:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:16:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2453) Release the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2453: -------------------------------- Priority: Major (was: Blocker) > Release the narayana-osgi-jta bundle > ------------------------------------ > > Key: JBTM-2453 > URL: https://issues.jboss.org/browse/JBTM-2453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > for KARAF-3749, they are looking for the narayana osgi jta bundle. I think we have not released it to the maven repos and it could add to the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:11 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:11 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2444. ------------------------------- > jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ > --------------------------------------------------------------------------------------------- > > Key: JBTM-2444 > URL: https://issues.jboss.org/browse/JBTM-2444 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.2.0 > > > {code} > Running org.jboss.narayana.quickstarts.jta.TestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE! > Results : > Tests in error: > org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 > {code} > The log file says: > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1] > Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}} > 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) > ... 96 more > {code} > Which leads me to believe it is likely due to the parsing in test-jms.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:11 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:11 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1339. ------------------------------- > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:11 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:11 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2452. ------------------------------- > External Queues BlackTie quickstart no longer works with Artemis > ---------------------------------------------------------------- > > Key: JBTM-2452 > URL: https://issues.jboss.org/browse/JBTM-2452 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.2.0 > > > Current failures: > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/799/console > This is currently preventing release. > {code} > [exec] /home/hudson/workspace/narayana-quickstarts/blacktie > [exec] Quickstart: Running externally managed queue quickstart > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne > [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417) > [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119) > [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262) > [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135) > [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) > [exec] at java.lang.Thread.run(Thread.java:744) > [exec] > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure > [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6 > [exec] Unable to queue all messages > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:11 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:11 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2425) Upgrade to latest wildfly version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2425. ------------------------------- > Upgrade to latest wildfly version > --------------------------------- > > Key: JBTM-2425 > URL: https://issues.jboss.org/browse/JBTM-2425 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > Latest is 10.0.0.Alpha3-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:12 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:12 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2448) Upgrade wildfly to 10.0.0.Alpha5-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2448. ------------------------------- > Upgrade wildfly to 10.0.0.Alpha5-SNAPSHOT > ----------------------------------------- > > Key: JBTM-2448 > URL: https://issues.jboss.org/browse/JBTM-2448 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:12 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:12 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2365) Create feature choice helper on narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2365. ------------------------------- > Create feature choice helper on narayana.io > ------------------------------------------- > > Key: JBTM-2365 > URL: https://issues.jboss.org/browse/JBTM-2365 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.2.0 > > > It would be useful to have something on our homepage that lists all the different transports we use and what features are available when you select each of those transport. Mainly all features are available which allows us to list those too. > Ideally in the future it might replace our current landing page so we should try to include all details from that too where possible - so you could include an axis that said "commercial support available" STM = No, XTS = yes and so on. > Needs experimentation to see what will work best. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:12 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:12 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2308. ------------------------------- > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.2.0 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:12 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:12 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2421) Provide some quickstarts for STM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2421. ------------------------------- > Provide some quickstarts for STM > -------------------------------- > > Key: JBTM-2421 > URL: https://issues.jboss.org/browse/JBTM-2421 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, STM > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > As part of my JBug I took the example from the documentation and produced a set of quickstarts that would be useful to contribute to the project. > The examples show: > 1. Pessimistic locking > 2. Optimistic locking > 3. Use of an STM object in a JTA transaction -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:12 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:12 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2375) Upload IDL and WSDL files to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2375. ------------------------------- > Upload IDL and WSDL files to the web page > ----------------------------------------- > > Key: JBTM-2375 > URL: https://issues.jboss.org/browse/JBTM-2375 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.2.0 > > > Upload IDL and WSDL files to the web page, so that they would be easy to find. Also, update documentation to use the correct links. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:12 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:12 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2386) Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2386. ------------------------------- > Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT > ----------------------------------------- > > Key: JBTM-2386 > URL: https://issues.jboss.org/browse/JBTM-2386 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.2.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/818 > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/819 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:13 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:13 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2450) OracleXADataSource not found in jdbc test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2450. ------------------------------- > OracleXADataSource not found in jdbc test > ----------------------------------------- > > Key: JBTM-2450 > URL: https://issues.jboss.org/browse/JBTM-2450 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.2.0 > > > {code} > Running com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.391 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest) Time elapsed: 0.219 sec <<< ERROR! > java.lang.ClassNotFoundException: oracle.jdbc.xa.client.OracleXADataSource > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.getDataSource(SimpleJdbcTest.java:79) > at com.hp.mwtests.ts.jdbc.basic.SimpleJdbcTest.test(SimpleJdbcTest.java:33) > Running com.hp.mwtests.ts.jdbc.utils.JNDISetup > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.172 sec <<< FAILURE! > test(com.hp.mwtests.ts.jdbc.utils.JNDISetup) Time elapsed: 0.016 sec <<< ERROR! > java.lang.ClassNotFoundException: TODO > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at com.hp.mwtests.ts.jdbc.utils.JNDISetup.test(JNDISetup.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:13 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:13 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2370) Document how to run the performance benchmark standalone and link this from performance runs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2370. ------------------------------- > Document how to run the performance benchmark standalone and link this from performance runs > -------------------------------------------------------------------------------------------- > > Key: JBTM-2370 > URL: https://issues.jboss.org/browse/JBTM-2370 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > Create an article on our wiki (or maybe better done by updating the https://github.com/jbosstm/performance/blob/master/README.md) and then link it from the performance output. > It doesn't need to say how to run against the PR I would say, that can be left to the reader. > Nothing too heavy, just the general flags and how to run it. > git clone narayana master > git clone performance master > (cd narayana && ./build.sh -DskipTests) > (cd performance && ./build.sh -DskipTests) > cd performance > export JMH_ARGS=... > ./build.sh... -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:12 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:12 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2451) BlackTie quickstarts failing to deploy to WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2451. ------------------------------- > BlackTie quickstarts failing to deploy to WildFly > ------------------------------------------------- > > Key: JBTM-2451 > URL: https://issues.jboss.org/browse/JBTM-2451 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.2.0 > > > Needs investigation: http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quickstarts-catelyn/798/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:13 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:13 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2417) Create CI pull request job for narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2417. ------------------------------- > Create CI pull request job for narayana.io > ------------------------------------------ > > Key: JBTM-2417 > URL: https://issues.jboss.org/browse/JBTM-2417 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:13 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:13 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2393) Add google analytics to the docs and narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2393. ------------------------------- > Add google analytics to the docs and narayana.io > ------------------------------------------------ > > Key: JBTM-2393 > URL: https://issues.jboss.org/browse/JBTM-2393 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.2.0 > > > For the docs, see an example here: > https://github.com/pressgang/pressgang-tools/blob/master/pressgang-tools-example/pom.xml#L79 > > UA-XXXXXXX-X > GTM-NJWS5L > MyProject > > We don't want that in normal builds, maybe add it in a release profile and update brp.xml to generate the docs with that enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:13 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:13 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2434) @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2434. ------------------------------- > @Transactional annotation on stereotype leads to error "ARJUNA016107: Expected an @Transactional annotation at class and/or method level" > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2434 > URL: https://issues.jboss.org/browse/JBTM-2434 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Environment: JDK 1.7u72 x64, Windows 8.1 Professional > Reporter: Alexander Morozov > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.2.0 > > Attachments: wildfly-jta-cdi.zip > > > It is seems that CDI Transactional extesion doesn't support well @Transactional annotation on CDI stereotypes. JTA transaction is created by library interceptor, but in case of exception on component's side, _com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.getTransactional(...)_ method failed to locate @Transactional annotation on target component. It leads to exception like that > {code} > java.lang.RuntimeException: ARJUNA016107: Expected an @Transactional annotation at class and/or method level > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.getTransactional(TransactionalInterceptorBase.java:83) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.handleException(TransactionalInterceptorBase.java:118) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx(TransactionalInterceptorBase.java:106) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory.intercept(TransactionalInterceptorMandatory.java:58) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) > at com.mycompany.wildfly.jta.cdi.UserEventDispatcher$Proxy$_$$_WeldSubclass.dispatch(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserEventDispatcher$Proxy$_$$_WeldClientProxy.dispatch(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserApplicationService.addUser(UserApplicationService.java:18) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldSubclass.addUser$$super(Unknown Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) > at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInOurTx(TransactionalInterceptorBase.java:92) > at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.intercept(TransactionalInterceptorRequired.java:52) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:74) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) > at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) > at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldSubclass.addUser(Unknown Source) > at com.mycompany.wildfly.jta.cdi.UserApplicationService$Proxy$_$$_WeldClientProxy.addUser(Unknown Source) > at com.mycompany.wildfly.jta.cdi.BootstrapExtension.start(BootstrapExtension.java:20) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > ......... > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:14 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:14 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2449. ------------------------------- > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:14 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:14 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2403) Add a quickstart for Undertow + REST-AT + JAX-RS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2403. ------------------------------- > Add a quickstart for Undertow + REST-AT + JAX-RS > ------------------------------------------------ > > Key: JBTM-2403 > URL: https://issues.jboss.org/browse/JBTM-2403 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.2.0 > > > Undertow + REST-AT + JAX-RS is a good simple showcase of our projects. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:14 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:14 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2397) Update pom.xml for JDK8 compatability with findbugs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2397. ------------------------------- > Update pom.xml for JDK8 compatability with findbugs > --------------------------------------------------- > > Key: JBTM-2397 > URL: https://issues.jboss.org/browse/JBTM-2397 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > Current version of parent is 17 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:14 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:14 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2295. ------------------------------- > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:14 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:14 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2414. ------------------------------- > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:14 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:14 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2420) BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2420. ------------------------------- > BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s) > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2420 > URL: https://issues.jboss.org/browse/JBTM-2420 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, REST > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.2.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-catelyn/918/consoleFull -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:14 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:14 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2418) NPE in BaseTransactionManagerDelegate commit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2418. ------------------------------- > NPE in BaseTransactionManagerDelegate commit > -------------------------------------------- > > Key: JBTM-2418 > URL: https://issues.jboss.org/browse/JBTM-2418 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > BaseTransactionManagerDelegate#commit should throw IllegalStateException if there is no transaction present. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:15 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2437) Failed to deploy BlackTie administration service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2437. ------------------------------- > Failed to deploy BlackTie administration service > ------------------------------------------------ > > Key: JBTM-2437 > URL: https://issues.jboss.org/browse/JBTM-2437 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.2.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-catelyn/941 > {code} > Running AdvertiseUnadvertiseTest > 17:21:55,250 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location C:\hudson\workspace\narayana-catelyn\blacktie\wildfly-10.0.0.Alpha4-SNAPSHOT\standalone\data\content\01\b2548ae63569dec6b9fd46d34b21b7f7d0e55e\content > 17:21:55,297 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 17:21:56,047 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 17:21:56,515 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0013: Deployment deployment "test.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations) > 17:21:56,797 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" => ["jboss.deployment.unit.\"test.war\".component.BlacktieStompAdministrationService.CREATE is missing [jboss.ra.activemq-ra]"]} > 17:21:56,797 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" => ["jboss.deployment.unit.\"test.war\".component.BlacktieStompAdministrationService.CREATE is missing [jboss.ra.activemq-ra]"]} > 17:21:56,843 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.1.3.Final > 17:21:57,094 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 294ms > 17:21:57,094 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.START, service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.VIEW."org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService".MESSAGE_ENDPOINT, service jboss.deployment.unit."test.war".moduleDeploymentRuntimeInformation] > service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.START (missing) dependents: [service jboss.deployment.unit."test.war".moduleDeploymentRuntimeInformationStart, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.VIEW."org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService".MESSAGE_ENDPOINT (missing) dependents: [service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.START, service jboss.deployment.unit."test.war".moduleDeploymentRuntimeInformation] > service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.START] > service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.START] > service jboss.deployment.unit."test.war".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.START, service jboss.deployment.unit."test.war".moduleDeploymentRuntimeInformationStart] > service jboss.ra.activemq-ra (missing) dependents: [service jboss.deployment.unit."test.war".component.BlacktieStompAdministrationService.CREATE] > service jboss.undertow.deployment.default-server.default-host./test (missing) dependents: [service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test] > service jboss.undertow.deployment.default-server.default-host./test.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.313 sec <<< FAILURE! > AdvertiseUnadvertiseTest Time elapsed: 6.313 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: test.war > 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:146) > 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.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.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.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.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.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.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.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:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:159) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:87) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:15 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2441) Skip license download when building wildfly 5_BRANCH In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2441. ------------------------------- > Skip license download when building wildfly 5_BRANCH > ---------------------------------------------------- > > Key: JBTM-2441 > URL: https://issues.jboss.org/browse/JBTM-2441 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > A number of our CI jobs build the 5_BRANCH of wildfly (wildfly master + the narayana master) but they occasionally fail on the wildfly release profile whilst downloading the licenses (via the license-maven-plugin in feature-pack/pom.xml) running out of heap space. > I will add -Dlicense.skipDownloadLicenses=true to our narayana.sh CI build script -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:15 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2453) Release the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2453. ------------------------------- > Release the narayana-osgi-jta bundle > ------------------------------------ > > Key: JBTM-2453 > URL: https://issues.jboss.org/browse/JBTM-2453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > for KARAF-3749, they are looking for the narayana osgi jta bundle. I think we have not released it to the maven repos and it could add to the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:15 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2446) Blacktie jatmibroker-xatmi hang with "javax.naming.NameNotFoundException: ConnectionFactory" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2446. ------------------------------- > Blacktie jatmibroker-xatmi hang with "javax.naming.NameNotFoundException: ConnectionFactory" > -------------------------------------------------------------------------------------------- > > Key: JBTM-2446 > URL: https://issues.jboss.org/browse/JBTM-2446 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.2.0 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux64el6/872/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:15 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2442) Update to use activemq-messaging subsystem in the standalone-blacktie.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2442. ------------------------------- > Update to use activemq-messaging subsystem in the standalone-blacktie.xml > ------------------------------------------------------------------------- > > Key: JBTM-2442 > URL: https://issues.jboss.org/browse/JBTM-2442 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration, BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.2.0 > > > currently the wildfly 10.0.0.Alpha4 changes to use the activemq-messaging and the default resource adapter of the MDB changed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:15 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2407) Remove CDIExtensionProcessor in the XTS subsytem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2407. ------------------------------- > Remove CDIExtensionProcessor in the XTS subsytem > ------------------------------------------------ > > Key: JBTM-2407 > URL: https://issues.jboss.org/browse/JBTM-2407 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.2.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > WFLY-1370 removes the need for the CDIExtensionProcessor in the XTS subsytem. > There is currently a hack in CDIExtensionProcessor in 5_BRANCH. This MUST be removed if WFLY-1370 is not merged in time for release. Hence I have marked this as critical. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:15 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:15 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2443) Raise a JTA HeuristicMixed if a one phase commit XAResource raises RMFAIL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2443. ------------------------------- > Raise a JTA HeuristicMixed if a one phase commit XAResource raises RMFAIL > ------------------------------------------------------------------------- > > Key: JBTM-2443 > URL: https://issues.jboss.org/browse/JBTM-2443 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > If a one phase commit is performed on an XAResource and it raises RMFAIL we have no way to know whether the resource committed or rolled back. We currently do not raise an exception in this scenario as an interpretation of the XA spec allows us to. > We have had community feedback that this has an issue for user applications and having consulted with the rest of our community and no negative comments received we will modify the behavior so that this scenario results in the closest exception that JTA allows HeuristicMixed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:16 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2432) Cannot test IBM J9 VM on linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2432. ------------------------------- > Cannot test IBM J9 VM on linux > ------------------------------- > > Key: JBTM-2432 > URL: https://issues.jboss.org/browse/JBTM-2432 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > We currently have provisional support for the IBM? J9 virtual machine for Java 7 but building narayana master now requires Java 8 (which we inherited from WildFly master which enforces Java 8). > Now it appears that the J9 virtual machine for Java 8 is not available on linux. When you go to the download page the linux download button redirects to the Oracle Hot Spot VM. We either need to abandon support for J9 or we add a CI machine running z/OS -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:16 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2369. ------------------------------- > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:16 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2427) btadmin.ListRunningInstanceIdsTest hang on the Linux In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2427. ------------------------------- > btadmin.ListRunningInstanceIdsTest hang on the Linux > ---------------------------------------------------- > > Key: JBTM-2427 > URL: https://issues.jboss.org/browse/JBTM-2427 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.2.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux32el5/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:16 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2408) Remove CDI extension descriptors from compensations quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2408. ------------------------------- > Remove CDI extension descriptors from compensations quickstarts > --------------------------------------------------------------- > > Key: JBTM-2408 > URL: https://issues.jboss.org/browse/JBTM-2408 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:16 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2423. ------------------------------- > ORBRunner uses the orb after run() returns > ------------------------------------------ > > Key: JBTM-2423 > URL: https://issues.jboss.org/browse/JBTM-2423 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: > {quote} > Once an ORB has shutdown, only object reference management operations(duplicate, > release and is_nil) may be invoked on the ORB or any object reference obtained > from it. > {quote} > Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: > {quote} > This operation will block until the ORB has completed the shutdown process, > {quote} > This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: > # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; > # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held > # at this point the jdk orb shutdown would normally then return allowing the > the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:16 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:16 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2424) Change hornetq dependency to the journal only In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2424. ------------------------------- > Change hornetq dependency to the journal only > --------------------------------------------- > > Key: JBTM-2424 > URL: https://issues.jboss.org/browse/JBTM-2424 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.2.0 > > > Currently we depend on hornetq-core. The later releases provide a hornetq-journal artifact that we use instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:17 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2213) Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2213. ------------------------------- > Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba > ------------------------------------------------------------------------------------------ > > Key: JBTM-2213 > URL: https://issues.jboss.org/browse/JBTM-2213 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.2.0 > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.narayana.txframework.api.annotation.lifecycle.ba" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipant.java:[45,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[112,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[154,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[115,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[162,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[57,146] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[115,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[158,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[62,27] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[65,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[118,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[166,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:17 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2395. ------------------------------- > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:17 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2415) Clean documentation dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2415. ------------------------------- > Clean documentation dependencies > -------------------------------- > > Key: JBTM-2415 > URL: https://issues.jboss.org/browse/JBTM-2415 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.2.0 > > > There are many unused dependencies and plugins in documentation pom. > Also, build-release-packages.xml file is out of date and not used. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:17 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2404. ------------------------------- > narayana-codeCoverage CI job is not producing any output > -------------------------------------------------------- > > Key: JBTM-2404 > URL: https://issues.jboss.org/browse/JBTM-2404 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/consoleFull -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:17 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2406) BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2406. ------------------------------- > BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition > ---------------------------------------------------------------------------------------- > > Key: JBTM-2406 > URL: https://issues.jboss.org/browse/JBTM-2406 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.2.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/825/PROFILE=XTS,jdk=jdk7.latest,label=linux/ > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest > ------------------------------------------------------------------------------- > Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 44.774 sec <<< FAILURE! > testManualComplete(org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest) Time elapsed: 4.202 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest.testManualComplete(BAParticipantCompletionTest.java:129) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:17 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2429) Disable java debugger in the surefire tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2429. ------------------------------- > Disable java debugger in the surefire tests > ------------------------------------------- > > Key: JBTM-2429 > URL: https://issues.jboss.org/browse/JBTM-2429 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.2.0 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > We are having intermittent problems with arquillian tests on the mac that start containers one after the other. It seems that a previous one is slow to shut down causing the next one to fail to start with > {code} > ERROR: transport error 202: bind failed: Address already in use > JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized > {code} > I plan to disable the debugger (I think we enabled it because of a hang on an old issue where we needed the debugger port open to aid diagnosis). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:17 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2391) Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2391. ------------------------------- > Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT > ------------------------------------------------------------ > > Key: JBTM-2391 > URL: https://issues.jboss.org/browse/JBTM-2391 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > 10.0.0.Alpha1-SNAPSHOT is master on WFLY now -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:18:18 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:18:18 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2214) Remove deprecation warnings for com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2214. ------------------------------- > Remove deprecation warnings for com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2214 > URL: https://issues.jboss.org/browse/JBTM-2214 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.2.0 > > > If you run: > ./build.sh clean install -DskipTests | grep "com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessAgreementWithParticipantCompletionStub.java:[173,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/SubordinateCoordinatorCompletionParticipantStub.java:[260,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessAgreementWithCoordinatorCompletionStub.java:[207,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestFaultedExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[64,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestNoExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[59,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestNoExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[62,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestFaultedExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[60,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wstx/tests/common/FailureBusinessParticipant.java:[106,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wstx/tests/common/DemoBusinessParticipant.java:[100,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestSystemExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[67,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestWrongStateExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[63,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestSystemExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[63,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestWrongStateExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[67,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/WSTX11-interop/src/main/java/com/jboss/transaction/txinterop/webservices/bainterop/participant/ParticipantCompletionParticipantAdapter.java:[56,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/xtstest/src/org/jboss/jbossts/xts/servicetests/service/participant/ParticipantCompletionTestParticipant.java:[99,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/compensations/impl/ParticipantImpl.java:[144,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/compensations/impl/remote/RemoteParticipant.java:[81,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[113,21] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[116,21] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:34:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:34:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2456) mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2456: ----------------------------------- Summary: mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find Key: JBTM-2456 URL: https://issues.jboss.org/browse/JBTM-2456 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System, Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson The workaround is to provide a path on the command line. This will probably be OK but NRP needs updating at least: https://developer.jboss.org/wiki/NarayanaReleaseProcess and provide no default -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:47:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:47:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2456) mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087705#comment-13087705 ] Tom Jenkinson commented on JBTM-2456: ------------------------------------- It was removed in https://github.com/jbosstm/documentation/commit/207fc61e879da0dfb5dc2b8bef38e1e5bb1e2309 > mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2456 > URL: https://issues.jboss.org/browse/JBTM-2456 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > The workaround is to provide a path on the command line. This will probably be OK but NRP needs updating at least: https://developer.jboss.org/wiki/NarayanaReleaseProcess and provide no default -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:48:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:48:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2456) mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2456: -------------------------------- Fix Version/s: 5.next > mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2456 > URL: https://issues.jboss.org/browse/JBTM-2456 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > The workaround is to provide a path on the command line. This will probably be OK but NRP needs updating at least: https://developer.jboss.org/wiki/NarayanaReleaseProcess and provide no default -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 05:48:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 05:48:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2456) mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2456: ----------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2456 > URL: https://issues.jboss.org/browse/JBTM-2456 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > The workaround is to provide a path on the command line. This will probably be OK but NRP needs updating at least: https://developer.jboss.org/wiki/NarayanaReleaseProcess and provide no default -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:40:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:40:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1575) Test support for Informix In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1575: -------------------------------- Affects Version/s: (was: 5.0.0.M2) > Test support for Informix > ------------------------- > > Key: JBTM-1575 > URL: https://issues.jboss.org/browse/JBTM-1575 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Testing > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Optional > Fix For: 6.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:42:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:42:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite on JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1854: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Hornetq failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:42:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:42:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite on JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087766#comment-13087766 ] Tom Jenkinson commented on JBTM-1854: ------------------------------------- Lets try to tackle this in the next iteration > Hornetq failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:42:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:42:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1922) RTS error and warning messages do have unique codes for identification purposes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1922: -------------------------------- Fix Version/s: 5.next (was: 6.later) > RTS error and warning messages do have unique codes for identification purposes > ------------------------------------------------------------------------------- > > Key: JBTM-1922 > URL: https://issues.jboss.org/browse/JBTM-1922 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Affects Versions: 5.0.0.M4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > > ANDIAMO-7 says that all error and warning messages should have a unique code that can be used to identify them. RTS does not conform with this requirement. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:43:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:43:02 -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 ] Tom Jenkinson updated JBTM-2115: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > 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.3.15#6346) From issues at jboss.org Wed Jul 8 08:43:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:43:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1310) Store JTS participant records with their parent transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087767#comment-13087767 ] Tom Jenkinson commented on JBTM-1310: ------------------------------------- Does this affect all versions or 4.17.1+ in particular? > Store JTS participant records with their parent transaction > ----------------------------------------------------------- > > Key: JBTM-1310 > URL: https://issues.jboss.org/browse/JBTM-1310 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Affects Versions: 4.17.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.later > > > In JTA mode participant records are stored together with their owning transaction but this does not happen in JTS mode even when the parent transaction is local. This results in extra log writes thus impacting throughput. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:44:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:44:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2183: -------------------------------- Affects Version/s: (was: 5.0.1) (was: 4.17.20) > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.jboss.org/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.later > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:45:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:45:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1340: -------------------------------- Fix Version/s: 5.next (was: 6.later) > BeanPopulator overhead needs looking into > ----------------------------------------- > > Key: JBTM-1340 > URL: https://issues.jboss.org/browse/JBTM-1340 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 4.17.2 > Environment: Mac OS 10.7 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.next > > > During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit. > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance > 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder. > 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString > 0.0% - 320 ?s - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey > 0.0% - 61 ?s - 10,000 inv. java.lang.Class.getName > 0.0% - 25 ?s - 10,000 inv. java.util.concurrent.ConcurrentMap.get -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:46:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:46:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-410) implement mixed outcome support for XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087770#comment-13087770 ] Tom Jenkinson commented on JBTM-410: ------------------------------------ Removing affects version as it should affect all versions. Version was 4.4.0.GA if change needs reverting. > implement mixed outcome support for XTS > --------------------------------------- > > Key: JBTM-410 > URL: https://issues.jboss.org/browse/JBTM-410 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: XTS > Affects Versions: 4.4.0.GA > Reporter: Jonathan Halliday > Fix For: 6.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:47:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:47:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-622) Support for crash recovery of tx-inflow with multiple resource managers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-622: ------------------------------- Affects Version/s: (was: 4.2.3.CP06) > Support for crash recovery of tx-inflow with multiple resource managers > ----------------------------------------------------------------------- > > Key: JBTM-622 > URL: https://issues.jboss.org/browse/JBTM-622 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JCA, Recovery, Transaction Core > Reporter: Toshiya Kobayashi > Priority: Minor > Fix For: 6.later > > > JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs. > In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:47:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:47:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1052) Support Web services with a webservices.xml present in TXFramework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1052: -------------------------------- Affects Version/s: (was: 4.17.0.M1/5.0.0.M1) > Support Web services with a webservices.xml present in TXFramework > ------------------------------------------------------------------ > > Key: JBTM-1052 > URL: https://issues.jboss.org/browse/JBTM-1052 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: TXFramework > Reporter: Paul Robinson > Priority: Minor > Fix For: 6.later > > > See: https://community.jboss.org/message/714478#714478 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:48:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:48:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1052) Support Web services with a webservices.xml present in TXFramework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087771#comment-13087771 ] Tom Jenkinson commented on JBTM-1052: ------------------------------------- Is this still required? We could do with a better description to explain the actual motivation or leave this closed as "incomplete description". > Support Web services with a webservices.xml present in TXFramework > ------------------------------------------------------------------ > > Key: JBTM-1052 > URL: https://issues.jboss.org/browse/JBTM-1052 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: TXFramework > Reporter: Paul Robinson > Priority: Minor > Fix For: 6.later > > > See: https://community.jboss.org/message/714478#714478 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:49:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:49:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2296: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Cloud, JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:49:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:49:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2212) Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client, org.jboss.resteasy.spi and tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2212: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client, org.jboss.resteasy.spi and tooling > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2212 > URL: https://issues.jboss.org/browse/JBTM-2212 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.jbossts.star.util has been deprecated\|org.jboss.resteasy.client\|org.jboss.resteasy.spi has been deprecated" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/util/src/main/java/org/jboss/jbossts/star/util/TxSupport.java:[50,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[55,7] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[85,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[128,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[155,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[173,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[198,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[219,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[264,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[273,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[278,16] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[283,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[288,19] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[293,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[339,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[400,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[505,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[587,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[92,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[98,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[102,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[113,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[136,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[183,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[184,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[204,56] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[228,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[229,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[230,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[306,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[307,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[308,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[310,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[311,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[312,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[346,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[366,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[406,22] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[460,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[523,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[538,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[596,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[627,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[651,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[284,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[313,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[317,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[192,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[219,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[218,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[224,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[259,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[258,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[264,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[321,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[323,59] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[328,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[388,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[432,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[27,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[22,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[28,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[177,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[180,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[304,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[335,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[342,42] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[403,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[513,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[621,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[693,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[768,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[70,47] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[104,34] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[54,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[56,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[62,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[398,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[497,38] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[696,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[699,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[704,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[732,26] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[23,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[32,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[5,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[18,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[27,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[8,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[18,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[19,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[20,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[89,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[56,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[79,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[103,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[119,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[127,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[131,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[295,17] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[307,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[309,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[311,52] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[24,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,42] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,41] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,49] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[164,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[15,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[13,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[14,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[20,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[21,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[23,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[38,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[42,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[178,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[205,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[228,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[247,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[266,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[285,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[304,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[321,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[340,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,57] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[83,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[98,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[102,9] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[115,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[118,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[121,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[122,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[136,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[149,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[152,68] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[166,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[169,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[184,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[198,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[213,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[225,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[242,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[254,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[271,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[289,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[301,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[320,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[321,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[324,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[325,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[328,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[330,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[329,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[333,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[335,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[334,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[338,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[340,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[339,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[343,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[345,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[344,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[349,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[350,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[68,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[94,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[113,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[114,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[117,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[119,57] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[118,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[32,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[41,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[75,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[92,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[72,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[104,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[123,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[71,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[79,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[94,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[109,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[124,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[136,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[141,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:50:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2245: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:50:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2409: -------------------------------- Fix Version/s: 5.next (was: 5.later) > XARecoveryModuleHelpersUnitTest hang > ------------------------------------ > > Key: JBTM-2409 > URL: https://issues.jboss.org/browse/JBTM-2409 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: 32287.jstack > > > The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. > The junit test thread: > - starts 2 threads that will remove a recovery helper > - triggers xaRecoveryModule.periodicWorkFirstPass() > - triggers xaRecoveryModule.periodicWorkSecondPass() > - joins with remover threads > The jstack output shows: > - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; > - the junit test thread is waiting to join with these two threads; > Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:50:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2419) Consider reducing the number of JMH perf test forks on PRs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2419: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Consider reducing the number of JMH perf test forks on PRs > ---------------------------------------------------------- > > Key: JBTM-2419 > URL: https://issues.jboss.org/browse/JBTM-2419 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > We run our JMH tests multiple times in order to estimate run-to-run variance. The [JMH docs|http://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/main/java/org/openjdk/jmh/samples/JMHSample_13_RunToRun.java] state: > bq. JVMs are complex systems, and the non-determinism is inherent for them. This requires us to always account the run-to-run variance as the one of the effects in our experiments. Forking aggregates the results across several JVM launches. > Currently we set the number of forks to 10. We run each test 6 times with each run lasting 1 min. Since we have 10 tests this means it takes 10 * 10 * 6 minutes for the benchmarks to complete. In the future we want to keep adding new performance tests and the time taken to run a PR will become prohibitive. I would like to propose one of the following solutions: > - reduce the number of forks; > - run a subset of performance tests on each PR and then run them all once a week or so on the main build > My preference is to reduce the number of forks to 3. Note that the PR requester has the option to disable performance tests for his PR (by including !PERF in the comment section). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:51:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:51:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2454: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:51:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:51:03 -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: -------------------------------- Fix Version/s: 5.next (was: 5.later) > 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: Michael Musgrove > 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.3.15#6346) From issues at jboss.org Wed Jul 8 08:52:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:52:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2234: -------------------------------- Fix Version/s: 5.next (was: 5.later) > out of memory when logging more messages than heap size (surefire issue) > ------------------------------------------------------------------------ > > Key: JBTM-2234 > URL: https://issues.jboss.org/browse/JBTM-2234 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Environment: JTS testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished. > In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:52:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:52:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1965) Add support for XADisk In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1965: -------------------------------- Fix Version/s: (was: 5.later) > Add support for XADisk > ---------------------- > > Key: JBTM-1965 > URL: https://issues.jboss.org/browse/JBTM-1965 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Student project > Affects Versions: 5.0.0.M5 > Reporter: Mark Little > Fix For: 6.later > > > We're unlikely to maintain fileio but there may be a need for supporting some transactional file interactions. XADisk (https://xadisk.java.net/) seems to have a vibrant user community, so we should take a look at this. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:52:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:52:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1965) Add support for XADisk In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1965: -------------------------------- Fix Version/s: 6.later > Add support for XADisk > ---------------------- > > Key: JBTM-1965 > URL: https://issues.jboss.org/browse/JBTM-1965 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Student project > Affects Versions: 5.0.0.M5 > Reporter: Mark Little > Fix For: 6.later > > > We're unlikely to maintain fileio but there may be a need for supporting some transactional file interactions. XADisk (https://xadisk.java.net/) seems to have a vibrant user community, so we should take a look at this. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:53:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:53:06 -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 ] Tom Jenkinson updated JBTM-1804: -------------------------------- Fix Version/s: 5.next (was: 6.later) > 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: Task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > 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.3.15#6346) From issues at jboss.org Wed Jul 8 08:54:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:54:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2270) When expose-all-logs is used with JTS then no participant for transaction is shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2270: -------------------------------- Affects Version/s: (was: 4.17.23) > When expose-all-logs is used with JTS then no participant for transaction is shown > ----------------------------------------------------------------------------------- > > Key: JBTM-2270 > URL: https://issues.jboss.org/browse/JBTM-2270 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Ond?ej Chaloupka > Assignee: Gytis Trikleris > Fix For: 6.later > > > When expose-all-logs is set to true I'm not able to get any participants of the listed transaction. > This is log from operation to get type of transaction and then see all participants. > Reading type of the transaction: > Succesful management operation { > "operation" => "read-attribute", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "name" => "type" > } with result { > "outcome" => "success", > "result" => "CosTransactions/XAResourceRecord" > } > Getting participants: > Succesful management operation { > "operation" => "read-children-names", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "child-type" => "participants" > } with result { > "outcome" => "success", > "result" => [] > } -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:56:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:56:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2305) Incomplete tooling documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2305: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Incomplete tooling documentation > -------------------------------- > > Key: JBTM-2305 > URL: https://issues.jboss.org/browse/JBTM-2305 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Documentation > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. > In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 08:58:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 08:58:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1853) RESTAT does not expose recovery URIs after a crash In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1853: -------------------------------- Fix Version/s: 5.next (was: 6.later) > RESTAT does not expose recovery URIs after a crash > -------------------------------------------------- > > Key: JBTM-1853 > URL: https://issues.jboss.org/browse/JBTM-1853 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > The RESTAT coordinator creates a participant-recovery URI during participant enlistment. This URI should exist for as long as the participant participates in the transaction including during recovery time. After a coordinator crash GET requests return 404 instead of returning the participant resource URI -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 09:04:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 09:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2439) XATMI CSTest failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2439: -------------------------------- Fix Version/s: 5.next (was: 5.later) > XATMI CSTest failed > ------------------- > > Key: JBTM-2439 > URL: https://issues.jboss.org/browse/JBTM-2439 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/863 > {code} > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest > 20:00:30,081 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:30,372 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:30,597 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:41,182 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:41,531 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:41,788 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:44,655 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:55163) Caught an exception: null: java.lang.NullPointerException > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) > at java.lang.Thread.run(Thread.java:744) > 20:00:54,478 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:54,749 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:55,057 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:05,617 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:05,865 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:06,103 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:16,623 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:16,900 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:17,169 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:38,604 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service pending for .testsui1 as consumer count is 0, will check again in 30000ms > 20:02:08,542 WARN [org.jboss.as.ejb3] (EJB default - 3) WFLYEJB0043: A previous execution of timer [id=ec057768-85a2-4e35-ac04-cebbf53ce28e timedObjectId=blacktie-admin-services-ear-5.1.2.Final-SNAPSHOT.blacktie-admin-services-5.1.2.Final-SNAPSHOT.QueueReaperBean auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 3aff5ed3 initialExpiration=Wed Jun 17 18:46:38 BST 2015 intervalDuration(in milli sec)=30000 nextExpiration=Wed Jun 17 20:02:08 BST 2015 timerState=IN_TIMEOUT info=queue reaper] is still in progress, skipping this overlapping scheduled execution at: Wed Jun 17 20:02:08 BST 2015. > 20:02:08,781 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service .testsui1 for consumer is 0 > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:02:23,382 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 5ec536b5 > 20:02:23,550 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:02:23,551 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:02:23,552 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 7642baf0 > 20:02:23,625 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:02:23,626 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:02:23,627 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2ecad1c6 > 20:02:23,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:02:23,743 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:02:23,744 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:02:23,745 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2684d6dd > 20:02:57,766 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 13: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 13 reason: Did not receive a message > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.SocketReceiverImpl.receive(SocketReceiverImpl.java:139) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.receive(ConnectionImpl.java:533) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:183) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:350) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,814 ERROR [org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl] (Thread-36 (HornetQ-client-global-threads-1622216728)) queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > 20:02:57,815 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 6: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 6 reason: queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl.send(StompSenderImpl.java:144) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpacall(ConnectionImpl.java:260) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:181) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:354) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,852 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 127) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,744 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:06,274 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:16,874 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:17,135 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:17,436 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:40,042 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:40,430 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:40,688 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:51,251 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:51,561 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:51,815 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:02,497 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:02,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:02,980 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:13,462 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:13,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:13,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:24,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:24,846 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:25,216 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:33,824 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:04:33,825 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:04:33,825 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 32f599dc > 20:04:33,910 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:04:33,911 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:04:33,911 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4a493aa5 > 20:04:33,989 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:04:33,990 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:04:33,990 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4afb2f0f > 20:04:34,065 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:04:34,098 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:04:34,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:04:34,100 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2d1d86a > 20:04:35,818 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:36,102 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:36,371 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:46,960 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:47,211 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:47,475 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:58,025 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:58,376 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:58,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 279.072 sec <<< FAILURE! > test_211(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest) Time elapsed: 101.173 sec <<< FAILURE! > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSControl.runTest(CSControl.java:153) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest.test_211(CSTest.java:27) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 09:05:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 09:05:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2433: -------------------------------- Fix Version/s: 5.next (was: 5.later) > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/858/PROFILE=XTS,jdk=jdk8.latest,label=linux > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 09:05:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 09:05:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2426) XTS WSTFSC07-interop failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2426: -------------------------------- Fix Version/s: 5.next > XTS WSTFSC07-interop failure > ---------------------------- > > Key: JBTM-2426 > URL: https://issues.jboss.org/browse/JBTM-2426 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.jboss.transaction.wstf.interop.Sc007Test-output.txt > > > junit test failure: > {code} > Running com.jboss.transaction.wstf.interop.Sc007Test > Tests run: 15, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 326.369 sec <<< FAILURE! > test3_10(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 212.002 sec <<< FAILURE! > junit.framework.AssertionFailedError: Conversation did not complete successfully > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_10(Sc007TestCase.java:474) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_10(Sc007Test.java:176) > test3_11(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 1.608 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:65) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_11(Sc007TestCase.java:495) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_11(Sc007Test.java:181) > Results : > Failed tests: > Sc007Test.test3_10:176 Conversation did not complete successfully > Tests in error: > Sc007Test.test3_11:181 ? TransactionRolledBack > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 09:15:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 09:15:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2409: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > XARecoveryModuleHelpersUnitTest hang > ------------------------------------ > > Key: JBTM-2409 > URL: https://issues.jboss.org/browse/JBTM-2409 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.next > > Attachments: 32287.jstack > > > The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. > The junit test thread: > - starts 2 threads that will remove a recovery helper > - triggers xaRecoveryModule.periodicWorkFirstPass() > - triggers xaRecoveryModule.periodicWorkSecondPass() > - joins with remover threads > The jstack output shows: > - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; > - the junit test thread is waiting to join with these two threads; > Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 09:16:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 09:16:02 -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 ] Tom Jenkinson reassigned JBTM-2115: ----------------------------------- Assignee: Amos Feng (was: Michael Musgrove) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Enhancement > 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.3.15#6346) From issues at jboss.org Wed Jul 8 09:16:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 09:16:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2234: ----------------------------------- Assignee: Amos Feng (was: Michael Musgrove) > out of memory when logging more messages than heap size (surefire issue) > ------------------------------------------------------------------------ > > Key: JBTM-2234 > URL: https://issues.jboss.org/browse/JBTM-2234 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Environment: JTS testing > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Optional > Fix For: 5.next > > > Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished. > In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 09:18:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 09:18:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2245: ----------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.next > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 09:19:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 09:19:04 -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 reassigned JBTM-2203: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > 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.3.15#6346) From issues at jboss.org Wed Jul 8 09:20:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 8 Jul 2015 09:20:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite on JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1854: ----------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > Hornetq failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 10:50:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 8 Jul 2015 10:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1310) Store JTS participant records with their parent transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-1310: ----------------------------------- Affects Version/s: (was: 4.17.1) > Store JTS participant records with their parent transaction > ----------------------------------------------------------- > > Key: JBTM-1310 > URL: https://issues.jboss.org/browse/JBTM-1310 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.later > > > In JTA mode participant records are stored together with their owning transaction but this does not happen in JTS mode even when the parent transaction is local. This results in extra log writes thus impacting throughput. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 10:51:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 8 Jul 2015 10:51:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1310) Store JTS participant records with their parent transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087869#comment-13087869 ] Michael Musgrove commented on JBTM-1310: ---------------------------------------- I have removed the affects versions field since it adds new functionality (and therefore affects all versions). > Store JTS participant records with their parent transaction > ----------------------------------------------------------- > > Key: JBTM-1310 > URL: https://issues.jboss.org/browse/JBTM-1310 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.later > > > In JTA mode participant records are stored together with their owning transaction but this does not happen in JTS mode even when the parent transaction is local. This results in extra log writes thus impacting throughput. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 11:03:06 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 8 Jul 2015 11:03:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2456) mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2456 started by Gytis Trikleris. --------------------------------------------- > mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2456 > URL: https://issues.jboss.org/browse/JBTM-2456 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > The workaround is to provide a path on the command line. This will probably be OK but NRP needs updating at least: https://developer.jboss.org/wiki/NarayanaReleaseProcess and provide no default -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 8 11:20:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 8 Jul 2015 11:20:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2456) mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2456: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/documentation/pull/33 > mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2456 > URL: https://issues.jboss.org/browse/JBTM-2456 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > The workaround is to provide a path on the command line. This will probably be OK but NRP needs updating at least: https://developer.jboss.org/wiki/NarayanaReleaseProcess and provide no default -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 04:37:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 9 Jul 2015 04:37:02 -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 reassigned JBTM-2206: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > 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 > > Change usage of Hashtable into synchronized HashMap's instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 04:38:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 9 Jul 2015 04:38:06 -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: -------------------------------- Fix Version/s: 5.next > 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 > Fix For: 5.next > > > Change usage of Hashtable into synchronized HashMap's instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 04:38:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 9 Jul 2015 04:38:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2110: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.jboss.org/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 08:07:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 9 Jul 2015 08:07:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2456) mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reassigned JBTM-2456: -------------------------------------- Assignee: Michael Musgrove (was: Gytis Trikleris) > mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2456 > URL: https://issues.jboss.org/browse/JBTM-2456 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > The workaround is to provide a path on the command line. This will probably be OK but NRP needs updating at least: https://developer.jboss.org/wiki/NarayanaReleaseProcess and provide no default -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 9 08:10:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 9 Jul 2015 08:10:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2456) mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reassigned JBTM-2456: -------------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2456 > URL: https://issues.jboss.org/browse/JBTM-2456 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > The workaround is to provide a path on the command line. This will probably be OK but NRP needs updating at least: https://developer.jboss.org/wiki/NarayanaReleaseProcess and provide no default -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun Jul 12 22:44:02 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Sun, 12 Jul 2015 22:44:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2457) Upgrade the wildfly to 10.0.0.Alpha6-SNAPSHOT In-Reply-To: References: Message-ID: Amos Feng created JBTM-2457: ------------------------------- Summary: Upgrade the wildfly to 10.0.0.Alpha6-SNAPSHOT Key: JBTM-2457 URL: https://issues.jboss.org/browse/JBTM-2457 Project: JBoss Transaction Manager Issue Type: Task Components: Application Server Integration Reporter: Amos Feng Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun Jul 12 22:46:02 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Sun, 12 Jul 2015 22:46:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2457) Upgrade the wildfly to 10.0.0.Alpha6-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2457: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/885 > Upgrade the wildfly to 10.0.0.Alpha6-SNAPSHOT > --------------------------------------------- > > Key: JBTM-2457 > URL: https://issues.jboss.org/browse/JBTM-2457 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 05:17:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 13 Jul 2015 05:17:02 -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: Gytis Trikleris created JBTM-2458: ------------------------------------- Summary: 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 Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 05:24:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 13 Jul 2015 05:24:02 -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: ---------------------------------- Description: 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. > 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 > 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.3.15#6346) From issues at jboss.org Mon Jul 13 05:38:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 13 Jul 2015 05:38:03 -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=13088755#comment-13088755 ] Gytis Trikleris commented on JBTM-2458: --------------------------------------- My first example: {code} public class BankingService { @Inject private AccountManager accountManager; @Compensatable public void transferMoney(String fromAccount, String toAccount, Double amount) { accountManager.debitAccount(fromAccount, amount); accountManager.creditAccount(toAccount, amount); } } @Compensatable public class AccountManager { private static final String DATABASE_NAME = "accounts-database"; private static final String COLLECTION_NAME = "accounts-collection"; @Inject(db = DATABASE_NAME, collection = COLLECTION_NAME) private MongoCollection collection; public void creditAccount(String account, Double amount) { Document filter = new Document("name", account); Document update = new Document("$inc", amount); Document undo = new Document("$inc", -1 * amount); updateCollection(filter, update, undo); } public void debitAccount(String account, Double amount) { Document filter = new Document("name", account); Document update = new Document("$inc", -1 * amount); Document undo = new Document("$inc", amount); updateCollection(filter, update, undo); } private void updateCollection(Document filter, Document update, Document undo) { CompensationHandler compensationHandler = () -> collection.updateOne(filter, undo); ConfirmationHandler confirmationHandler = () -> System.out.println(filter + " was updated"); // v1 collection.onFailure(compensationHandler).onSuccess(confirmationHandler).updateOne(filter, update); // v2 // collection.updateOne(filter, update, compensationHandler, confirmationHandler); } } {code} > 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 > 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.3.15#6346) From issues at jboss.org Mon Jul 13 05:38:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 13 Jul 2015 05:38:03 -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=13088755#comment-13088755 ] Gytis Trikleris edited comment on JBTM-2458 at 7/13/15 5:37 AM: ---------------------------------------------------------------- First example: {code} public class BankingService { @Inject private AccountManager accountManager; @Compensatable public void transferMoney(String fromAccount, String toAccount, Double amount) { accountManager.debitAccount(fromAccount, amount); accountManager.creditAccount(toAccount, amount); } } @Compensatable public class AccountManager { private static final String DATABASE_NAME = "accounts-database"; private static final String COLLECTION_NAME = "accounts-collection"; @Inject(db = DATABASE_NAME, collection = COLLECTION_NAME) private MongoCollection collection; public void creditAccount(String account, Double amount) { Document filter = new Document("name", account); Document update = new Document("$inc", amount); Document undo = new Document("$inc", -1 * amount); updateCollection(filter, update, undo); } public void debitAccount(String account, Double amount) { Document filter = new Document("name", account); Document update = new Document("$inc", -1 * amount); Document undo = new Document("$inc", amount); updateCollection(filter, update, undo); } private void updateCollection(Document filter, Document update, Document undo) { CompensationHandler compensationHandler = () -> collection.updateOne(filter, undo); ConfirmationHandler confirmationHandler = () -> System.out.println(filter + " was updated"); // v1 collection.onFailure(compensationHandler).onSuccess(confirmationHandler).updateOne(filter, update); // v2 // collection.updateOne(filter, update, compensationHandler, confirmationHandler); } } {code} was (Author: gytis): My first example: {code} public class BankingService { @Inject private AccountManager accountManager; @Compensatable public void transferMoney(String fromAccount, String toAccount, Double amount) { accountManager.debitAccount(fromAccount, amount); accountManager.creditAccount(toAccount, amount); } } @Compensatable public class AccountManager { private static final String DATABASE_NAME = "accounts-database"; private static final String COLLECTION_NAME = "accounts-collection"; @Inject(db = DATABASE_NAME, collection = COLLECTION_NAME) private MongoCollection collection; public void creditAccount(String account, Double amount) { Document filter = new Document("name", account); Document update = new Document("$inc", amount); Document undo = new Document("$inc", -1 * amount); updateCollection(filter, update, undo); } public void debitAccount(String account, Double amount) { Document filter = new Document("name", account); Document update = new Document("$inc", -1 * amount); Document undo = new Document("$inc", amount); updateCollection(filter, update, undo); } private void updateCollection(Document filter, Document update, Document undo) { CompensationHandler compensationHandler = () -> collection.updateOne(filter, undo); ConfirmationHandler confirmationHandler = () -> System.out.println(filter + " was updated"); // v1 collection.onFailure(compensationHandler).onSuccess(confirmationHandler).updateOne(filter, update); // v2 // collection.updateOne(filter, update, compensationHandler, confirmationHandler); } } {code} > 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 > 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.3.15#6346) From issues at jboss.org Mon Jul 13 05:44:04 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 13 Jul 2015 05:44:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088764#comment-13088764 ] Gytis Trikleris commented on JBTM-2296: --------------------------------------- [~tomjenkinson], you had a go with it some time ago. Do you think it's usable enough to be merged into our dockerfiles repo? > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Cloud, JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 13 08:34:04 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 13 Jul 2015 08:34:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2456) mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2456: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > mvn executable missing from documentation repo which the default setting on build-release-pkgs.xml expects to be able to find > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2456 > URL: https://issues.jboss.org/browse/JBTM-2456 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > The workaround is to provide a path on the command line. This will probably be OK but NRP needs updating at least: https://developer.jboss.org/wiki/NarayanaReleaseProcess and provide no default -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 03:42:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 14 Jul 2015 03:42:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2426) XTS WSTFSC07-interop failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089118#comment-13089118 ] Gytis Trikleris commented on JBTM-2426: --------------------------------------- This bit seems a bit fishy: {code} 16:25:51,559 ERROR [stderr] (Timer-2) Exception in thread "Timer-2" java.lang.NullPointerException 16:25:51,559 ERROR [stderr] (Timer-2) at com.arjuna.wst11.messaging.engines.CoordinatorEngine.sendPrepare(CoordinatorEngine.java:603) 16:25:51,560 ERROR [stderr] (Timer-2) at com.arjuna.wst11.messaging.engines.CoordinatorEngine.commsTimeout(CoordinatorEngine.java:438) 16:25:51,560 ERROR [stderr] (Timer-2) at com.arjuna.wst11.messaging.engines.CoordinatorEngine.access$000(CoordinatorEngine.java:28) 16:25:51,560 ERROR [stderr] (Timer-2) at com.arjuna.wst11.messaging.engines.CoordinatorEngine$1.run(CoordinatorEngine.java:715) 16:25:51,560 ERROR [stderr] (Timer-2) at java.util.TimerThread.mainLoop(Timer.java:555) 16:25:51,560 ERROR [stderr] (Timer-2) at java.util.TimerThread.run(Timer.java:505) {code} All the logged warnings and errors before this also appear in the successful logs. However, after this NPE unexpected errors appear. > XTS WSTFSC07-interop failure > ---------------------------- > > Key: JBTM-2426 > URL: https://issues.jboss.org/browse/JBTM-2426 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.jboss.transaction.wstf.interop.Sc007Test-output.txt > > > junit test failure: > {code} > Running com.jboss.transaction.wstf.interop.Sc007Test > Tests run: 15, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 326.369 sec <<< FAILURE! > test3_10(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 212.002 sec <<< FAILURE! > junit.framework.AssertionFailedError: Conversation did not complete successfully > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_10(Sc007TestCase.java:474) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_10(Sc007Test.java:176) > test3_11(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 1.608 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:65) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_11(Sc007TestCase.java:495) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_11(Sc007Test.java:181) > Results : > Failed tests: > Sc007Test.test3_10:176 Conversation did not complete successfully > Tests in error: > Sc007Test.test3_11:181 ? TransactionRolledBack > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 04:03:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 14 Jul 2015 04:03:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2426) XTS WSTFSC07-interop failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089125#comment-13089125 ] Gytis Trikleris commented on JBTM-2426: --------------------------------------- The test was waiting for the timer to abort the transaction. However, since the timer failed with NPE, transaction was not aborted. > XTS WSTFSC07-interop failure > ---------------------------- > > Key: JBTM-2426 > URL: https://issues.jboss.org/browse/JBTM-2426 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.jboss.transaction.wstf.interop.Sc007Test-output.txt > > > junit test failure: > {code} > Running com.jboss.transaction.wstf.interop.Sc007Test > Tests run: 15, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 326.369 sec <<< FAILURE! > test3_10(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 212.002 sec <<< FAILURE! > junit.framework.AssertionFailedError: Conversation did not complete successfully > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_10(Sc007TestCase.java:474) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_10(Sc007Test.java:176) > test3_11(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 1.608 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:65) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_11(Sc007TestCase.java:495) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_11(Sc007Test.java:181) > Results : > Failed tests: > Sc007Test.test3_10:176 Conversation did not complete successfully > Tests in error: > Sc007Test.test3_11:181 ? TransactionRolledBack > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 04:13:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 14 Jul 2015 04:13:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2426) XTS WSTFSC07-interop failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089132#comment-13089132 ] Gytis Trikleris commented on JBTM-2426: --------------------------------------- As stated by the comment in the code [1] timerTask field may be set to null by another thread. However, a bit later in the method we do not check for null, only if the value differs [2]. Same thing applies for sendCommit method. [1] https://github.com/jbosstm/narayana/blob/master/XTS/WS-T/dev/src/com/arjuna/wst11/messaging/engines/CoordinatorEngine.java#L578 [2] https://github.com/jbosstm/narayana/blob/master/XTS/WS-T/dev/src/com/arjuna/wst11/messaging/engines/CoordinatorEngine.java#L603 > XTS WSTFSC07-interop failure > ---------------------------- > > Key: JBTM-2426 > URL: https://issues.jboss.org/browse/JBTM-2426 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.jboss.transaction.wstf.interop.Sc007Test-output.txt > > > junit test failure: > {code} > Running com.jboss.transaction.wstf.interop.Sc007Test > Tests run: 15, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 326.369 sec <<< FAILURE! > test3_10(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 212.002 sec <<< FAILURE! > junit.framework.AssertionFailedError: Conversation did not complete successfully > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_10(Sc007TestCase.java:474) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_10(Sc007Test.java:176) > test3_11(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 1.608 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:65) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_11(Sc007TestCase.java:495) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_11(Sc007Test.java:181) > Results : > Failed tests: > Sc007Test.test3_10:176 Conversation did not complete successfully > Tests in error: > Sc007Test.test3_11:181 ? TransactionRolledBack > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 04:36:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 14 Jul 2015 04:36:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2426) XTS WSTFSC07-interop failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2426: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/886 > XTS WSTFSC07-interop failure > ---------------------------- > > Key: JBTM-2426 > URL: https://issues.jboss.org/browse/JBTM-2426 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.jboss.transaction.wstf.interop.Sc007Test-output.txt > > > junit test failure: > {code} > Running com.jboss.transaction.wstf.interop.Sc007Test > Tests run: 15, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 326.369 sec <<< FAILURE! > test3_10(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 212.002 sec <<< FAILURE! > junit.framework.AssertionFailedError: Conversation did not complete successfully > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_10(Sc007TestCase.java:474) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_10(Sc007Test.java:176) > test3_11(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 1.608 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:65) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_11(Sc007TestCase.java:495) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_11(Sc007Test.java:181) > Results : > Failed tests: > Sc007Test.test3_10:176 Conversation did not complete successfully > Tests in error: > Sc007Test.test3_11:181 ? TransactionRolledBack > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 04:54:02 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 14 Jul 2015 04:54:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2457) Upgrade the wildfly to 10.0.0.Alpha6-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2457: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade the wildfly to 10.0.0.Alpha6-SNAPSHOT > --------------------------------------------- > > Key: JBTM-2457 > URL: https://issues.jboss.org/browse/JBTM-2457 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 06:11:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 14 Jul 2015 06:11:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2245: ----------------------------------- Assignee: Tom Jenkinson (was: Gytis Trikleris) > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.next > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 06:11:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 14 Jul 2015 06:11:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2245: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 07:01:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 14 Jul 2015 07:01:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2454: -------------------------------- Priority: Minor (was: Major) > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 08:04:04 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 14 Jul 2015 08:04: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: ---------------------------------- Priority: Minor (was: Major) > 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.3.15#6346) From issues at jboss.org Tue Jul 14 08:12:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 14 Jul 2015 08:12:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2433: ---------------------------------- Description: It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. {code} ------------------------------------------------------------------------------- Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! com.arjuna.wst.TransactionRolledBackException: null at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) {code} was: It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/858/PROFILE=XTS,jdk=jdk8.latest,label=linux {code} ------------------------------------------------------------------------------- Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! com.arjuna.wst.TransactionRolledBackException: null at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) {code} > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 10:15:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 14 Jul 2015 10:15:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17 In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2459: ----------------------------------- Summary: Add an option to allow JBTM-2443 to be enabled in 4.17 Key: JBTM-2459 URL: https://issues.jboss.org/browse/JBTM-2459 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Configuration Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.17.29 JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 10:18:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 14 Jul 2015 10:18:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2459: -------------------------------- Fix Version/s: 4.17.30 (was: 4.17.29) > Add an option to allow JBTM-2443 to be enabled in 4.17 > ------------------------------------------------------ > > Key: JBTM-2459 > URL: https://issues.jboss.org/browse/JBTM-2459 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Configuration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.30 > > > JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 10:36:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 14 Jul 2015 10:36:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2459: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/887 > Add an option to allow JBTM-2443 to be enabled in 4.17 > ------------------------------------------------------ > > Key: JBTM-2459 > URL: https://issues.jboss.org/browse/JBTM-2459 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Configuration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.30 > > > JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 14 11:35:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 14 Jul 2015 11:35:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2245 started by Michael Musgrove. ---------------------------------------------- > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 03:02:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 15 Jul 2015 03:02:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1965) Add support for XADisk In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1965: -------------------------------- Issue Type: Feature Request (was: Task) > Add support for XADisk > ---------------------- > > Key: JBTM-1965 > URL: https://issues.jboss.org/browse/JBTM-1965 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Student project > Affects Versions: 5.0.0.M5 > Reporter: Mark Little > Fix For: 6.later > > > We're unlikely to maintain fileio but there may be a need for supporting some transactional file interactions. XADisk (https://xadisk.java.net/) seems to have a vibrant user community, so we should take a look at this. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 05:19:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 15 Jul 2015 05:19:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2460: -------------------------------------- Summary: Expose TransactionListenerRegistry via the SPI Key: JBTM-2460 URL: https://issues.jboss.org/browse/JBTM-2460 Project: JBoss Transaction Manager Issue Type: Bug Components: SPI Reporter: Michael Musgrove Assignee: Michael Musgrove TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: {code} (TransactionListenerRegistry) getTransactionManager(); {code} So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 05:45:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 15 Jul 2015 05:45:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2460: ----------------------------------- Fix Version/s: 5.next > Expose TransactionListenerRegistry via the SPI > ---------------------------------------------- > > Key: JBTM-2460 > URL: https://issues.jboss.org/browse/JBTM-2460 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: > {code} > (TransactionListenerRegistry) getTransactionManager(); > {code} > So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 06:31:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 15 Jul 2015 06:31:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089628#comment-13089628 ] Tom Jenkinson commented on JBTM-2460: ------------------------------------- Bind in JNDI? > Expose TransactionListenerRegistry via the SPI > ---------------------------------------------- > > Key: JBTM-2460 > URL: https://issues.jboss.org/browse/JBTM-2460 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: > {code} > (TransactionListenerRegistry) getTransactionManager(); > {code} > So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 09:53:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 15 Jul 2015 09:53:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2443) Raise a JTA HeuristicMixed if a one phase commit XAResource raises RMFAIL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089709#comment-13089709 ] Tom Jenkinson commented on JBTM-2443: ------------------------------------- Previously if RMFAIL was returned out of XAResource.commit(true, xid1) we did not return an exception and left it to the database to resolve the issue and potentially leave it to return the Xid during recovery using some assistance from its client side driver for example. The new behaviour would allow the database to do that the same as it does today but an exception would also be thrown to the client to say that there is a HeuristicMixed to be aware the result of the commit may not be reliable. > Raise a JTA HeuristicMixed if a one phase commit XAResource raises RMFAIL > ------------------------------------------------------------------------- > > Key: JBTM-2443 > URL: https://issues.jboss.org/browse/JBTM-2443 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > If a one phase commit is performed on an XAResource and it raises RMFAIL we have no way to know whether the resource committed or rolled back. We currently do not raise an exception in this scenario as an interpretation of the XA spec allows us to. > We have had community feedback that this has an issue for user applications and having consulted with the rest of our community and no negative comments received we will modify the behavior so that this scenario results in the closest exception that JTA allows HeuristicMixed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 10:14:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 15 Jul 2015 10:14:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2459: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add an option to allow JBTM-2443 to be enabled in 4.17 > ------------------------------------------------------ > > Key: JBTM-2459 > URL: https://issues.jboss.org/browse/JBTM-2459 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Configuration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.30 > > > JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 15 10:15:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 15 Jul 2015 10:15:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2459: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Add an option to allow JBTM-2443 to be enabled in 4.17 > ------------------------------------------------------ > > Key: JBTM-2459 > URL: https://issues.jboss.org/browse/JBTM-2459 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Configuration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.30 > > > JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 16 10:19:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 16 Jul 2015 10:19:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2461) Allow multiple configurations of Narayana to execute in the same JVM In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2461: ----------------------------------- Summary: Allow multiple configurations of Narayana to execute in the same JVM Key: JBTM-2461 URL: https://issues.jboss.org/browse/JBTM-2461 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Tom Jenkinson Assignee: Tom Jenkinson A long running feature request that I can't locate in Jira so recording here. Future revisions of the application container WildFly would find it beneficial to run multiple instances of the transaction manager in different configurations (one-per app) and allow the service to be started/stopped/executed in isolation. One of the barriers is that the factory method returns a singleton. The second is that there is static state in classes and so different configs are not viable. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 16 13:27:02 2015 From: issues at jboss.org (David Lloyd (JIRA)) Date: Thu, 16 Jul 2015 13:27:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2461) Allow multiple configurations of Narayana to execute in the same JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090125#comment-13090125 ] David Lloyd commented on JBTM-2461: ----------------------------------- Another use case involves embedded instances of WildFly. In order to fully support embedding, global state is to be avoided. We will likely reach a point where subsystems which either require some control over the JVM itself or otherwise cannot have multiple existence will be excluded from the embedded container configuration. > Allow multiple configurations of Narayana to execute in the same JVM > -------------------------------------------------------------------- > > Key: JBTM-2461 > URL: https://issues.jboss.org/browse/JBTM-2461 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > A long running feature request that I can't locate in Jira so recording here. > Future revisions of the application container WildFly would find it beneficial to run multiple instances of the transaction manager in different configurations (one-per app) and allow the service to be started/stopped/executed in isolation. > One of the barriers is that the factory method returns a singleton. The second is that there is static state in classes and so different configs are not viable. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 17 06:36:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 17 Jul 2015 06:36:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2426) XTS WSTFSC07-interop failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2426: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > XTS WSTFSC07-interop failure > ---------------------------- > > Key: JBTM-2426 > URL: https://issues.jboss.org/browse/JBTM-2426 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.jboss.transaction.wstf.interop.Sc007Test-output.txt > > > junit test failure: > {code} > Running com.jboss.transaction.wstf.interop.Sc007Test > Tests run: 15, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 326.369 sec <<< FAILURE! > test3_10(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 212.002 sec <<< FAILURE! > junit.framework.AssertionFailedError: Conversation did not complete successfully > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_10(Sc007TestCase.java:474) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_10(Sc007Test.java:176) > test3_11(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 1.608 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:65) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_11(Sc007TestCase.java:495) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_11(Sc007Test.java:181) > Results : > Failed tests: > Sc007Test.test3_10:176 Conversation did not complete successfully > Tests in error: > Sc007Test.test3_11:181 ? TransactionRolledBack > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 17 14:06:02 2015 From: issues at jboss.org (Anonymous (JIRA)) Date: Fri, 17 Jul 2015 14:06:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when pull request #7787 was created in GitHub ---------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Expose TransactionListenerRegistry via the SPI > ---------------------------------------------- > > Key: JBTM-2460 > URL: https://issues.jboss.org/browse/JBTM-2460 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: > {code} > (TransactionListenerRegistry) getTransactionManager(); > {code} > So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 20 06:31:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 20 Jul 2015 06:31:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2462) "Too many open files" failure in CI In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2462: ------------------------------------- Summary: "Too many open files" failure in CI Key: JBTM-2462 URL: https://issues.jboss.org/browse/JBTM-2462 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Tom Jenkinson Priority: Critical Many CI builds fail to build WildFly because of too many open files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 20 06:32:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 20 Jul 2015 06:32:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2462) "Too many open files" failure in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090715#comment-13090715 ] Gytis Trikleris commented on JBTM-2462: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana/889/ http://albany.eng.hst.ams2.redhat.com/job/narayana/888/ http://albany.eng.hst.ams2.redhat.com/job/narayana-ibm-jdk/117/ > "Too many open files" failure in CI > ----------------------------------- > > Key: JBTM-2462 > URL: https://issues.jboss.org/browse/JBTM-2462 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Critical > > Many CI builds fail to build WildFly because of too many open files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 20 07:45:04 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 20 Jul 2015 07:45:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2462) "Too many open files" failure in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090740#comment-13090740 ] Michael Musgrove commented on JBTM-2462: ---------------------------------------- My recommendation would be to increase the ulimit for open files in narayana.sh > "Too many open files" failure in CI > ----------------------------------- > > Key: JBTM-2462 > URL: https://issues.jboss.org/browse/JBTM-2462 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Critical > > Many CI builds fail to build WildFly because of too many open files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 20 07:45:05 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 20 Jul 2015 07:45:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2462) "Too many open files" failure in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reassigned JBTM-2462: -------------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > "Too many open files" failure in CI > ----------------------------------- > > Key: JBTM-2462 > URL: https://issues.jboss.org/browse/JBTM-2462 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > > Many CI builds fail to build WildFly because of too many open files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 20 08:13:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 20 Jul 2015 08:13:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2462) "Too many open files" failure in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090755#comment-13090755 ] Gytis Trikleris commented on JBTM-2462: --------------------------------------- Did the configuration change in the CI that it started failing out of nowhere? > "Too many open files" failure in CI > ----------------------------------- > > Key: JBTM-2462 > URL: https://issues.jboss.org/browse/JBTM-2462 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > > Many CI builds fail to build WildFly because of too many open files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 20 08:27:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 20 Jul 2015 08:27:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2462) "Too many open files" failure in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090760#comment-13090760 ] Michael Musgrove commented on JBTM-2462: ---------------------------------------- No, ulimit -n still has the default value (1024) > "Too many open files" failure in CI > ----------------------------------- > > Key: JBTM-2462 > URL: https://issues.jboss.org/browse/JBTM-2462 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > > Many CI builds fail to build WildFly because of too many open files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 21 06:07:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 21 Jul 2015 06:07:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2463) QA suite failure: TestGroup_rawresources01_3 In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2463: ----------------------------------- Summary: QA suite failure: TestGroup_rawresources01_3 Key: JBTM-2463 URL: https://issues.jboss.org/browse/JBTM-2463 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Fix For: 5.later http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/152/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 21 06:35:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 21 Jul 2015 06:35:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2463) QA suite failure: TestGroup_rawresources01_3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2463: -------------------------------- Component/s: Testing > QA suite failure: TestGroup_rawresources01_3 > -------------------------------------------- > > Key: JBTM-2463 > URL: https://issues.jboss.org/browse/JBTM-2463 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-jdbcobjectstore/152/DB_TYPE=db2,jdk=jdk7.latest,slave=linux/console -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 21 09:26:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 21 Jul 2015 09:26:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2464) Upgrade to Artemis journal from HornetQ journal In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2464: ----------------------------------- Summary: Upgrade to Artemis journal from HornetQ journal Key: JBTM-2464 URL: https://issues.jboss.org/browse/JBTM-2464 Project: JBoss Transaction Manager Issue Type: Task Components: Transaction Core Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.next When available -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 21 11:46:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 21 Jul 2015 11:46:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite on JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091391#comment-13091391 ] Gytis Trikleris commented on JBTM-1854: --------------------------------------- [~mmusgrov], so out of all those tests in the description only CurrentTests01_Test036 is expected to work on HornetQ? Or did I misunderstand your comment earlier today about crash recovery test not supporting HornetQ? > Hornetq failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 05:50:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 22 Jul 2015 05:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite on JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091657#comment-13091657 ] Michael Musgrove commented on JBTM-1854: ---------------------------------------- I didn't quite say that. I said that there are a number of tests where we do not test recovery when using the hornetq store and this logic is encoded into the tests themselves. So any failures you are seeing are genuine failures. Take a look at how we set the org.jboss.jbossts.qa.junit.TestGroupBase#isRecoveryManagerNeeded variable. > Hornetq failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 05:58:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 22 Jul 2015 05:58:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite on JDKORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091662#comment-13091662 ] Gytis Trikleris commented on JBTM-1854: --------------------------------------- Ok got you. Just wanted to check, because those crash recovery tests are the only ones which fail for me. CurrentTests01_Test036 passes with and without HQ store. > Hornetq failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 10:35:17 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 22 Jul 2015 10:35:17 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2459: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1245702 > Add an option to allow JBTM-2443 to be enabled in 4.17 > ------------------------------------------------------ > > Key: JBTM-2459 > URL: https://issues.jboss.org/browse/JBTM-2459 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Configuration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.30 > > > JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 10:55:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 22 Jul 2015 10:55:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2464) Upgrade to Artemis journal from HornetQ journal In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2464: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/889 > Upgrade to Artemis journal from HornetQ journal > ----------------------------------------------- > > Key: JBTM-2464 > URL: https://issues.jboss.org/browse/JBTM-2464 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > When available -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 11:07:02 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 22 Jul 2015 11:07:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2459: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1245702, https://bugzilla.redhat.com/show_bug.cgi?id=1245720 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1245702) > Add an option to allow JBTM-2443 to be enabled in 4.17 > ------------------------------------------------------ > > Key: JBTM-2459 > URL: https://issues.jboss.org/browse/JBTM-2459 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Configuration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.30 > > > JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 11:21:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 22 Jul 2015 11:21:09 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2462) "Too many open files" failure in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2462. --------------------------------- Resolution: Done resolution: ulimit increased to 10000 > "Too many open files" failure in CI > ----------------------------------- > > Key: JBTM-2462 > URL: https://issues.jboss.org/browse/JBTM-2462 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > > Many CI builds fail to build WildFly because of too many open files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 11:23:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 22 Jul 2015 11:23:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2440: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Unresolved > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 11:23:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 22 Jul 2015 11:23:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2440) Byteman tests fail when running with the IBM JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2440: --------------------------------- > Byteman tests fail when running with the IBM JVM > ------------------------------------------------ > > Key: JBTM-2440 > URL: https://issues.jboss.org/browse/JBTM-2440 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > Byteman instrumentation does not work with the IBM J9 JVM:- it fails with errors like the following: > {code} > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Exception in thread "Attachment 59984" Agent failed to start! > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} > I will implement a workaround by disabling byteman when testing with this JVM. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 22 12:35:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 22 Jul 2015 12:35:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2465) PR job is missing perf regression output In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2465: -------------------------------------- Summary: PR job is missing perf regression output Key: JBTM-2465 URL: https://issues.jboss.org/browse/JBTM-2465 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.2.0 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later The PERF axis of the CI job https://github.com/jbosstm/narayana/pull/889 did not produce any output because of the following error: {code} Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.performance.Performance1-master.csv': No such file or directory Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest-master.csv': No such file or directory Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/benchmarks.jar cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/jmh/com.arjuna.ats.jta.xa.performance.JTAStoreTests-master.csv': No such file or directory no benchmarks to compare {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 04:13:05 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 23 Jul 2015 04:13:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2465) PR job is missing perf regression output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2465: ----------------------------------- Priority: Minor (was: Major) > PR job is missing perf regression output > ---------------------------------------- > > Key: JBTM-2465 > URL: https://issues.jboss.org/browse/JBTM-2465 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > The PERF axis of the CI job https://github.com/jbosstm/narayana/pull/889 did not produce any output because of the following error: > {code} > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.performance.Performance1-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/jmh/com.arjuna.ats.jta.xa.performance.JTAStoreTests-master.csv': No such file or directory > no benchmarks to compare > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 04:15:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 23 Jul 2015 04:15:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2465) PR job is missing perf regression output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092040#comment-13092040 ] Michael Musgrove commented on JBTM-2465: ---------------------------------------- I have reduced the priority since the job did produce the perf output later on in the run so I think it's just a Jenkins job config issue. > PR job is missing perf regression output > ---------------------------------------- > > Key: JBTM-2465 > URL: https://issues.jboss.org/browse/JBTM-2465 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > The PERF axis of the CI job https://github.com/jbosstm/narayana/pull/889 did not produce any output because of the following error: > {code} > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.performance.Performance1-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/jmh/com.arjuna.ats.jta.xa.performance.JTAStoreTests-master.csv': No such file or directory > no benchmarks to compare > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 23 04:27:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 23 Jul 2015 04:27:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2462) "Too many open files" failure in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2462: ----------------------------------- Forum Reference: https://developer.jboss.org/message/936397 > "Too many open files" failure in CI > ----------------------------------- > > Key: JBTM-2462 > URL: https://issues.jboss.org/browse/JBTM-2462 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > > Many CI builds fail to build WildFly because of too many open files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 24 10:00:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 24 Jul 2015 10:00:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092726#comment-13092726 ] Tom Jenkinson commented on JBTM-2296: ------------------------------------- They looked good to me, thanks. > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Cloud, JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat Jul 25 08:04:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 25 Jul 2015 08:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2466) Upgrade narayana dependency in the performance repository In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2466: -------------------------------------- Summary: Upgrade narayana dependency in the performance repository Key: JBTM-2466 URL: https://issues.jboss.org/browse/JBTM-2466 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Affects Versions: 5.2.0 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The various tests in the performance repo (https://github.com/jbosstm/performance) should test against the latest narayana master so the dependencies need updating to the latest (5.2.1.Final-SNAPSHOT) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat Jul 25 08:16:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 25 Jul 2015 08:16:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2467) REST-AT performance tests fail In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2467: -------------------------------------- Summary: REST-AT performance tests fail Key: JBTM-2467 URL: https://issues.jboss.org/browse/JBTM-2467 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Affects Versions: 5.2.0 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The REST-AT tests in the performance repo fail because the deployment to the undertow server used in the tests is failing -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat Jul 25 08:28:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 25 Jul 2015 08:28:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2466) Upgrade narayana dependency in the performance repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2466: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/performance/pull/16 > Upgrade narayana dependency in the performance repository > --------------------------------------------------------- > > Key: JBTM-2466 > URL: https://issues.jboss.org/browse/JBTM-2466 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The various tests in the performance repo (https://github.com/jbosstm/performance) should test against the latest narayana master so the dependencies need updating to the latest (5.2.1.Final-SNAPSHOT) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat Jul 25 08:30:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 25 Jul 2015 08:30:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2466) Upgrade narayana dependency in the performance repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2466: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade narayana dependency in the performance repository > --------------------------------------------------------- > > Key: JBTM-2466 > URL: https://issues.jboss.org/browse/JBTM-2466 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The various tests in the performance repo (https://github.com/jbosstm/performance) should test against the latest narayana master so the dependencies need updating to the latest (5.2.1.Final-SNAPSHOT) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat Jul 25 08:38:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 25 Jul 2015 08:38:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2467) REST-AT performance tests fail In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092911#comment-13092911 ] Michael Musgrove commented on JBTM-2467: ---------------------------------------- I have temporarily disabled the REST-AT benchmarks (https://github.com/jbosstm/performance/commit/29dc299c93b1fb3cf00344004e89b1f6a61e8bd2) > REST-AT performance tests fail > ------------------------------ > > Key: JBTM-2467 > URL: https://issues.jboss.org/browse/JBTM-2467 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The REST-AT tests in the performance repo fail because the deployment to the undertow server used in the tests is failing -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat Jul 25 09:25:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 25 Jul 2015 09:25:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2468) xts, jts and rts performance comparison job has failures In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2468: -------------------------------------- Summary: xts, jts and rts performance comparison job has failures Key: JBTM-2468 URL: https://issues.jboss.org/browse/JBTM-2468 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Affects Versions: 5.2.0 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The weekly NCL jenkins job for performance comparison of jts/xts/rts has three issues: - the throughput is coming out at 0 (I think it is because its very slow but it needs investigating); - the jts component fails to configure wildfly into jts mode (I have temporarily disabled it in the job config); - it runs against 9.0.0.Alpha2-SNAPSHOT (so it needs updating to run against the wildfly bi weekly builds) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 27 04:23:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 27 Jul 2015 04:23:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2469) BlackTie tests failing due to missing queue/BTR_TestTPConnect In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2469: -------------------------------------- Summary: BlackTie tests failing due to missing queue/BTR_TestTPConnect Key: JBTM-2469 URL: https://issues.jboss.org/browse/JBTM-2469 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Affects Versions: 5.2.0 Reporter: Michael Musgrove Assignee: Amos Feng job http://albany.eng.hst.ams2.redhat.com/job/narayana-catelyn/967 has been running for a couple of days with the repeated failure: bq. javax.naming.NameNotFoundException: queue/BTR_TestTPConnect -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 27 04:41:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 27 Jul 2015 04:41:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2466) Upgrade narayana dependency in the performance repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092977#comment-13092977 ] Tom Jenkinson commented on JBTM-2466: ------------------------------------- Feel free to add a step to https://community.jboss.org/wiki/NarayanaReleaseProcess if you think it useful > Upgrade narayana dependency in the performance repository > --------------------------------------------------------- > > Key: JBTM-2466 > URL: https://issues.jboss.org/browse/JBTM-2466 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The various tests in the performance repo (https://github.com/jbosstm/performance) should test against the latest narayana master so the dependencies need updating to the latest (5.2.1.Final-SNAPSHOT) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jul 27 17:03:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 27 Jul 2015 17:03:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2306) Tooling does not display the type of a heuristic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2306. ------------------------------- > Tooling does not display the type of a heuristic > ------------------------------------------------ > > Key: JBTM-2306 > URL: https://issues.jboss.org/browse/JBTM-2306 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.4 > > > The new JMX based tooling for browsing abstract records does not display the particular type of a heuristic *when it's available*. > There is a comment in the javadoc for AbstractRecord which seems to indicate that the particular kind of heuristic may be available: > {code} > /** > * If this abstract record caused a heuristic then it should return an > * object which implements HeuristicInformation > * > * @return Object to be used to order. > */ > public abstract Object value (); > {code} > HeuristicInformation contains a method getHeuristicType() which looks like it may report the particular kind of heuristic.: > {code} > public interface HeuristicInformation { > /** > * The type of heuristic. > * @return the heuristic type > */ > public int getHeuristicType(); > {code} > This JIRA is asking for value() object to be consulted to see if it contains an instance of HeuristicInformation and if so to report it in the JBX MBean corresponding to the AR. > Note that such a change would only affect 3rd party implementers of ARs (since our own code does not set this field). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 09:58:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 09:58:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1454) Compare performance of REST-AT with JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1454: -------------------------------- Component/s: (was: BlackTie) > Compare performance of REST-AT with JTS > --------------------------------------- > > Key: JBTM-1454 > URL: https://issues.jboss.org/browse/JBTM-1454 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, Performance Testing, REST > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 10:01:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 10:01:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1581) Add support for Ingres XA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1581. ------------------------------- Resolution: Won't Fix > Add support for Ingres XA > ------------------------- > > Key: JBTM-1581 > URL: https://issues.jboss.org/browse/JBTM-1581 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Resource Manager > Reporter: Tom Jenkinson > Attachments: txfooapp.tar.gz > > > Ingres is an open source database and has an XA C driver -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 10:03:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 10:03:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1589) Support build on HP-UX In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1589. ------------------------------- Resolution: Won't Fix > Support build on HP-UX > ---------------------- > > Key: JBTM-1589 > URL: https://issues.jboss.org/browse/JBTM-1589 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Build System > Reporter: Tom Jenkinson > > HP-UX build and instructions -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 10:03:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 10:03:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1587) Support build on Solaris In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1587. ------------------------------- Resolution: Won't Fix > Support build on Solaris > ------------------------ > > Key: JBTM-1587 > URL: https://issues.jboss.org/browse/JBTM-1587 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Build System > Affects Versions: 4.17.0.M1/5.0.0.M1 > Reporter: Michael Musgrove > Attachments: solhowto.txt > > > Make sure BlackTie builds on Solaris -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 10:04:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 10:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1583) Add rest support for applications to access xatmi services over In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1583. ------------------------------- Resolution: Won't Fix > Add rest support for applications to access xatmi services over > --------------------------------------------------------------- > > Key: JBTM-1583 > URL: https://issues.jboss.org/browse/JBTM-1583 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie > Reporter: Tom Jenkinson > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > Allow the xatmi services to be accessed using REST services. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 10:07:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 10:07:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1576) Introduce a JBoss deployable artifact for the C++ XATMI services In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1576: -------------------------------- Description: Currently the XATMI services must be deployed in the standalone "Server" CORBA container It is expected to be advantageous to support the deployment of the services into JBoss for ease of management and performance. It is expected that the user will deploy a .war file containing a btconfig.xml defining the .so/.dll (also contained in the .war). BlackTie java code will read the btconfig.xml and calculate the path of the .so based on the place that AS7 unzips war files to during deployment PLUS the path defined in the users btconfig.xml If AS7 does not explode war files during deployment, it will not be possible for the user to package their .so in their .war file (I don't think - please do investigate this) and so a java.native.library.path will need defining at boot time and the user will need to place all their jni code in there thereby not supporting hot deploy unfortunately but still gaining the benefits of performance (not requiring socket comms between java and C). Cache the JNIEnv* to use to callback on the datasources - Allow C++ XATMI services deployed into the AS to use the existing JCA connections was: Currently the XATMI services must be deployed in the standalone "Server" CORBA container It is expected to be advantageous to support the deployment of the services into JBoss for ease of management and performance. It is expected that the user will deploy a .war file containing a btconfig.xml defining the .so/.dll (also contained in the .war). BlackTie java code will read the btconfig.xml and calculate the path of the .so based on the place that AS7 unzips war files to during deployment PLUS the path defined in the users btconfig.xml If AS7 does not explode war files during deployment, it will not be possible for the user to package their .so in their .war file (I don't think - please do investigate this) and so a java.native.library.path will need defining at boot time and the user will need to place all their jni code in there thereby not supporting hot deploy unfortunately but still gaining the benefits of performance (not requiring socket comms between java and C). > Introduce a JBoss deployable artifact for the C++ XATMI services > ---------------------------------------------------------------- > > Key: JBTM-1576 > URL: https://issues.jboss.org/browse/JBTM-1576 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Tooling > Reporter: Tom Jenkinson > Attachments: onmessage.tgz > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Currently the XATMI services must be deployed in the standalone "Server" CORBA container > It is expected to be advantageous to support the deployment of the services into JBoss for ease of management and performance. > It is expected that the user will deploy a .war file containing a btconfig.xml defining the .so/.dll (also contained in the .war). > BlackTie java code will read the btconfig.xml and calculate the path of the .so based on the place that AS7 unzips war files to during deployment PLUS the path defined in the users btconfig.xml > If AS7 does not explode war files during deployment, it will not be possible for the user to package their .so in their .war file (I don't think - please do investigate this) and so a java.native.library.path will need defining at boot time and the user will need to place all their jni code in there thereby not supporting hot deploy unfortunately but still gaining the benefits of performance (not requiring socket comms between java and C). > Cache the JNIEnv* to use to callback on the datasources - Allow C++ XATMI services deployed into the AS to use the existing JCA connections -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 10:07:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 10:07:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1574) Allow C++ XATMI services deployed into the AS to use the existing JCA connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1574. ------------------------------- Resolution: Duplicate Issue Dup of JBTM-1576 > Allow C++ XATMI services deployed into the AS to use the existing JCA connections > --------------------------------------------------------------------------------- > > Key: JBTM-1574 > URL: https://issues.jboss.org/browse/JBTM-1574 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie > Reporter: Tom Jenkinson > > Cache the JNIEnv* to use to callback on the datasources -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 10:12:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 10:12:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2142) BlackTie does not have a unit test for services that interact with databases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2142. ------------------------------- Resolution: Rejected We are going to use the quickstart txfooapp as an integration test > BlackTie does not have a unit test for services that interact with databases > ---------------------------------------------------------------------------- > > Key: JBTM-2142 > URL: https://issues.jboss.org/browse/JBTM-2142 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > > The only test we have for this is in the quickstarts - we need it in the unit/integration tests so that we pick up issues in a timely fashion. > Perhaps a similar approach to the one we use for JDBCStore testing in ArjunaCore/arjuna/pom.xml might work for BlackTie too. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 10:17:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 10:17:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1666) Investigate "still reachable" valgrind memory errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1666: -------------------------------- Issue Type: Task (was: Bug) > Investigate "still reachable" valgrind memory errors > ---------------------------------------------------- > > Key: JBTM-1666 > URL: https://issues.jboss.org/browse/JBTM-1666 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Tom Jenkinson > > Most of the valgrind logs are full of: > ==9548== 4 bytes in 1 blocks are still reachable in loss record 1 of 51 > ==9548== at 0x4027D17: operator new(unsigned int) (vg_replace_malloc.c:292) > ==9548== by 0x4E633A8: google::protobuf::DescriptorPool::DescriptorPool(google::protobuf::DescriptorDatabase*, google::protobuf::DescriptorPool::ErrorCollector*) (descriptor.cc:770) > ==9548== by 0x4E6346D: google::protobuf::(anonymous namespace)::InitGeneratedPool() (descriptor.cc:816) > ==9548== by 0x546E8DF: pthread_once (in /lib/libpthread-2.12.so) > ==9548== by 0x4E86E3F: google::protobuf::protobuf_AddDesc_google_2fprotobuf_2fdescriptor_2eproto() (descriptor.pb.cc:656) > ==9548== by 0x4E8790C: __static_initialization_and_destruction_0(int, int) (descriptor.pb.cc:705) > ==9548== by 0x4ED2495: ??? (in /home/hudson/workspace/blacktie-linux32/nbf/target/cxx/runtime/lib/libprotobuf.so.7) > ==9548== by 0x4E4538C: ??? (in /home/hudson/workspace/blacktie-linux32/nbf/target/cxx/runtime/lib/libprotobuf.so.7) > ==9548== by 0x400EFCE: _dl_init (in /lib/ld-2.12.so) > ==9548== by 0x400088E: ??? (in /lib/ld-2.12.so) > Please can you explain what this is and whether it is a leak and if so, try to resolve it? -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 10:17:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 10:17:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1667) Investigate "possibly lost" valgrind memory issues In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1667: -------------------------------- Issue Type: Task (was: Bug) > Investigate "possibly lost" valgrind memory issues > -------------------------------------------------- > > Key: JBTM-1667 > URL: https://issues.jboss.org/browse/JBTM-1667 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Tom Jenkinson > > There are "possibly lost" memory issues when running BlackTie under valgrind: > ==26112== 1,234 bytes in 21 blocks are possibly lost in loss record 56 of 58 > ==26112== at 0x4006355: operator new(unsigned int) (vg_replace_malloc.c:214) > ==26112== by 0x1DC13A: std::string::_Rep::_S_create(unsigned int, unsigned int, std::allocator const&) (in /usr/lib/libstdc++.so.6.0.8) > ==26112== by 0x1DCCD7: std::string::_Rep::_M_clone(std::allocator const&, unsigned int) (in /usr/lib/libstdc++.so.6.0.8) > ==26112== by 0x1DD666: std::basic_string, std::allocator >::basic_string(std::string const&) (in /usr/lib/libstdc++.so.6.0.8) > ==26112== by 0x4E00DBE: bool google::protobuf::InsertIfNotPresent, std::less, std::allocator > > >, std::string, std::pair >(std::map, std::less, std::allocator > > >*, std::string const&, std::pair const&) (stl_pair.h:85) > ==26112== by 0x4E01BAF: google::protobuf::SimpleDescriptorDatabase::DescriptorIndex >::AddFile(google::protobuf::FileDescriptorProto const&, std::pair) (descriptor_database.cc:56) > ==26112== by 0x4DFC4E6: google::protobuf::EncodedDescriptorDatabase::Add(void const*, int) (descriptor_database.cc:312) > ==26112== by 0x4DBC1FF: google::protobuf::DescriptorPool::InternalAddGeneratedFile(void const*, int) (descriptor.cc:862) > ==26112== by 0x4DE4E3F: google::protobuf::protobuf_AddDesc_google_2fprotobuf_2fdescriptor_2eproto() (descriptor.pb.cc:656) > ==26112== by 0x4DE590C: __static_initialization_and_destruction_0(int, int) (descriptor.pb.cc:705) > ==26112== by 0x4E30495: ??? (in /home/hudson/workspace/blacktie-linux32/xatmi/target/cxx/runtime/lib/libprotobuf.so.7) > ==26112== by 0x4DA338C: ??? (in /home/hudson/workspace/blacktie-linux32/xatmi/target/cxx/runtime/lib/libprotobuf.so.7) > ==26112== by 0xAA5492: call_init (in /lib/ld-2.5.so) > ==26112== by 0xAA55A2: _dl_init (in /lib/ld-2.5.so) > ==26112== by 0xA9784E: ??? (in /lib/ld-2.5.so) > ==26112== > ==26112== 303,104 bytes in 37 blocks are possibly lost in loss record 58 of 58 > ==26112== at 0x4005B83: malloc (vg_replace_malloc.c:195) > ==26112== by 0x489CBB0: apr_pool_create_ex (in /usr/lib/libapr-1.so.0.2.7) > ==26112== by 0x489CDCE: apr_pool_initialize (in /usr/lib/libapr-1.so.0.2.7) > ==26112== by 0x489DB0E: apr_initialize (in /usr/lib/libapr-1.so.0.2.7) > ==26112== by 0x4C8EE54: log4cxx::helpers::APRInitializer::APRInitializer() (aprinitializer.cpp:41) > ==26112== by 0x4C8EF39: log4cxx::helpers::APRInitializer::getInstance() (aprinitializer.cpp:57) > ==26112== by 0x4C8F000: log4cxx::helpers::APRInitializer::initialize() (aprinitializer.cpp:63) > ==26112== by 0x4C514E9: log4cxx::helpers::ObjectImpl::ObjectImpl() (objectimpl.cpp:30) > ==26112== by 0x4C251EA: log4cxx::helpers::CharsetDecoder::CharsetDecoder() (charsetdecoder.cpp:413) > ==26112== by 0x4C27339: log4cxx::helpers::LocaleCharsetDecoder::LocaleCharsetDecoder() (charsetdecoder.cpp:360) > ==26112== by 0x4C25714: log4cxx::helpers::CharsetDecoder::createDefaultDecoder() (charsetdecoder.cpp:430) > ==26112== by 0x4C25789: log4cxx::helpers::CharsetDecoder::getDefaultDecoder() (charsetdecoder.cpp:435) > ==26112== by 0x4BFC72A: log4cxx::helpers::Transcoder::decode(std::string const&, std::string&) (transcoder.cpp:247) > ==26112== by 0x4C185B7: log4cxx::LogManager::getLogger(std::string const&) (logmanager.cpp:120) > ==26112== by 0x4CBD428: log4cxx::Logger::getLogger(char const*) (logger.cpp:496) > ==26112== by 0x490E768: __static_initialization_and_destruction_0(int, int) (XsdValidator.cxx:21) > ==26112== by 0x490E7A6: global constructors keyed to _ZN12XsdValidator6loggerE (XsdValidator.cxx:205) > ==26112== by 0x4913665: ??? (in /home/hudson/workspace/blacktie-linux32/xatmi/target/cxx/runtime/lib/libblacktie-core.so) > ==26112== by 0x48E4D60: ??? (in /home/hudson/workspace/blacktie-linux32/xatmi/target/cxx/runtime/lib/libblacktie-core.so) > ==26112== by 0xAA5492: call_init (in /lib/ld-2.5.so) > ==26112== by 0xAA55A2: _dl_init (in /lib/ld-2.5.so) > ==26112== by 0xA9784E: ??? (in /lib/ld-2.5.so) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:00:13 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:00:13 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1415) TXFramework: Allow servlet-name to be anything in web.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1415. ------------------------------- Fix Version/s: (was: 6.later) Resolution: Incomplete Description > TXFramework: Allow servlet-name to be anything in web.xml > --------------------------------------------------------- > > Key: JBTM-1415 > URL: https://issues.jboss.org/browse/JBTM-1415 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: TXFramework > Reporter: Paul Robinson > > Removes a restriction imposed by JBTM-1408. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:02:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:02:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1445) Ensure chained exceptions are used throughout XTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1445. ------------------------------- Fix Version/s: (was: 6.later) Resolution: Incomplete Description > Ensure chained exceptions are used throughout XTS > ------------------------------------------------- > > Key: JBTM-1445 > URL: https://issues.jboss.org/browse/JBTM-1445 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Reporter: Paul Robinson > Labels: assign > > There should be a way of automating this, or at least reliably searching for every occurrence. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:03:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:03:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1953) Check other byteman_support scripts support message replay In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1953. ------------------------------- Fix Version/s: (was: 6.later) Resolution: Incomplete Description > Check other byteman_support scripts support message replay > ---------------------------------------------------------- > > Key: JBTM-1953 > URL: https://issues.jboss.org/browse/JBTM-1953 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > > See comments towards end of here: JBTM-1919 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:08:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:08:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-396) Provide one-phase commit optimization for WS-TX In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-396: ---------------------------------- Assignee: (was: Gytis Trikleris) > Provide one-phase commit optimization for WS-TX > ----------------------------------------------- > > Key: JBTM-396 > URL: https://issues.jboss.org/browse/JBTM-396 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: XTS > Affects Versions: 4.4.CR1 > Reporter: Mark Little > > WS-AT does not support 1PC optimization. WS-ACID from WS-CAF does. It would be good to provide a configurable option for WS-AT users to enable 1PC optimization. This obviously breaks interoperability, which is why the default should be to have it disabled. > Discussion currently happening here: https://community.jboss.org/message/831313 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:12:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:12:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-741: ---------------------------------- Assignee: Gytis Trikleris > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:13:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:13:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-741: ------------------------------- Fix Version/s: 5.next > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:17:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:17:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-785) Document configuration of standalone client In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093569#comment-13093569 ] Tom Jenkinson commented on JBTM-785: ------------------------------------ Hi [~paul.robinson], Is there any update on this? We can't understand what is needed here. What is a standalone client in this context? Tom > Document configuration of standalone client > ------------------------------------------- > > Key: JBTM-785 > URL: https://issues.jboss.org/browse/JBTM-785 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation, XTS > Affects Versions: 4.12.0 > Reporter: Andrew Dinn > > Need to explain how to set up standalone client so it can be deployed embedded without the need to expose completion initiator service endpoints. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:21:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:21:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2461) Allow multiple configurations of Narayana to execute in the same JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2461. ------------------------------- Resolution: Duplicate Issue > Allow multiple configurations of Narayana to execute in the same JVM > -------------------------------------------------------------------- > > Key: JBTM-2461 > URL: https://issues.jboss.org/browse/JBTM-2461 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > A long running feature request that I can't locate in Jira so recording here. > Future revisions of the application container WildFly would find it beneficial to run multiple instances of the transaction manager in different configurations (one-per app) and allow the service to be started/stopped/executed in isolation. > One of the barriers is that the factory method returns a singleton. The second is that there is static state in classes and so different configs are not viable. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:23:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:23:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-898) Align quickstart structures with WildFly quickstart pattern In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-898. ------------------------------ Resolution: Done > Align quickstart structures with WildFly quickstart pattern > ----------------------------------------------------------- > > Key: JBTM-898 > URL: https://issues.jboss.org/browse/JBTM-898 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > > https://docs.jboss.org/author/display/AS71/Writing+a+quickstart -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:27:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:27:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-928) ATParticipantCrashAndRecover Crash Recovery test needs completing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093580#comment-13093580 ] Tom Jenkinson commented on JBTM-928: ------------------------------------ Remove the @Ignore from https://github.com/jbosstm/narayana/blob/master/XTS/localjunit/crash-recovery-tests/src/test/java/com/arjuna/qa/junit/TestATParticipantCrashAndRecover.java > ATParticipantCrashAndRecover Crash Recovery test needs completing > ----------------------------------------------------------------- > > Key: JBTM-928 > URL: https://issues.jboss.org/browse/JBTM-928 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Affects Versions: 4.17.0.M1/5.0.0.M1 > Reporter: Paul Robinson > Fix For: 5.next > > > This test was not completed due to a problem with JBossWS that prevented the test case from being possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:27:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:27:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-928) ATParticipantCrashAndRecover Crash Recovery test needs completing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-928: ---------------------------------- Assignee: Gytis Trikleris > ATParticipantCrashAndRecover Crash Recovery test needs completing > ----------------------------------------------------------------- > > Key: JBTM-928 > URL: https://issues.jboss.org/browse/JBTM-928 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Affects Versions: 4.17.0.M1/5.0.0.M1 > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > This test was not completed due to a problem with JBossWS that prevented the test case from being possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:27:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:27:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-928) ATParticipantCrashAndRecover Crash Recovery test needs completing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-928: ------------------------------- Fix Version/s: 5.next > ATParticipantCrashAndRecover Crash Recovery test needs completing > ----------------------------------------------------------------- > > Key: JBTM-928 > URL: https://issues.jboss.org/browse/JBTM-928 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Affects Versions: 4.17.0.M1/5.0.0.M1 > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > This test was not completed due to a problem with JBossWS that prevented the test case from being possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:29:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:29:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-950) Improve XTS crash recvovery tests to cover additional scenarios where coordinator and participant are not colocated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-950: ------------------------------- Summary: Improve XTS crash recvovery tests to cover additional scenarios where coordinator and participant are not colocated (was: Improve XTS crash recvovery tests to use one server per participant) > Improve XTS crash recvovery tests to cover additional scenarios where coordinator and participant are not colocated > ------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-950 > URL: https://issues.jboss.org/browse/JBTM-950 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Reporter: Paul Robinson > > Currently the XTS crash recovery tests locates the client, coordinator and participants in the same server. This results in them all crashing and recovering at the same time. We should improve the tests to run one server each for the client, coordinator and each participant. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:30:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:30:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-950) Improve XTS crash recvovery tests to cover additional scenarios where coordinator and participant are not colocated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093583#comment-13093583 ] Tom Jenkinson commented on JBTM-950: ------------------------------------ Add a new test for non-colocated scenarios, don't refactor existing tests. > Improve XTS crash recvovery tests to cover additional scenarios where coordinator and participant are not colocated > ------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-950 > URL: https://issues.jboss.org/browse/JBTM-950 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Reporter: Paul Robinson > > Currently the XTS crash recovery tests locates the client, coordinator and participants in the same server. This results in them all crashing and recovering at the same time. We should improve the tests to run one server each for the client, coordinator and each participant. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:31:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:31:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-951) Extend XTS crash recovery suite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-951. ------------------------------ Resolution: Incomplete Description > Extend XTS crash recovery suite > ------------------------------- > > Key: JBTM-951 > URL: https://issues.jboss.org/browse/JBTM-951 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Reporter: Paul Robinson > > Once we have code coverage in place we can then spot areas in need of greater coverage. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:38:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:38:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-979) Support REST-JDI protocol in the TXFramework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-979: ------------------------------- Priority: Optional (was: Major) > Support REST-JDI protocol in the TXFramework > --------------------------------------------- > > Key: JBTM-979 > URL: https://issues.jboss.org/browse/JBTM-979 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework > Reporter: Paul Robinson > Priority: Optional > Labels: TXFramework > Fix For: 6.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:39:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:39:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1488) Implement the REST-JDI specification In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1488: -------------------------------- Labels: student (was: ) > Implement the REST-JDI specification > ------------------------------------ > > Key: JBTM-1488 > URL: https://issues.jboss.org/browse/JBTM-1488 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Labels: student > Fix For: 6.later > > > https://community.jboss.org/wiki/CompensatingRESTfulTransactions/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:41:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:41:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1091) TXFramework Quickstart: Protocol Switching, JTS -> WS-AT -> REST-AT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1091. ------------------------------- Resolution: Out of Date TXF is deprecated, please consider raising a Jira for compensations if you still need this > TXFramework Quickstart: Protocol Switching, JTS -> WS-AT -> REST-AT > ------------------------------------------------------------------- > > Key: JBTM-1091 > URL: https://issues.jboss.org/browse/JBTM-1091 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:43:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:43:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1104) XTS support for load-balanced scenarios In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1104: -------------------------------- Fix Version/s: (was: 6.later) > XTS support for load-balanced scenarios > --------------------------------------- > > Key: JBTM-1104 > URL: https://issues.jboss.org/browse/JBTM-1104 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: XTS > Reporter: Paul Robinson > > Enabling session affinity on the load balancer should ensure that all requests for a particular application endpoint, within a particular session, go to the same instance of the web service. > However, XTS advertises a number of endpoint addresses that will not make sense in a load balanced cluster. This is because it would be the internal endpoint address of the particular server that is advertised, rather than the load balancer's external address. > Even if we configured XTS (not yet possible) to offer the address of the LB, we would still have a problem as XTS will use a different session to the application to send protocol messages and thus they will go to a different server that is not aware of this transaction. > h4. Potential Solution > For each web service that is deployed by XTS, we advertises a modified version of the load balancer's address. The modification to the url provides a unique identifier for the particular node in the cluster. The load balancer would then be configured to route messages based on the modification in the url. The LB would also re-write the URL to match that expected by the particular server that receives the message. > This should be configurable per group of services provided by XTS (Client, Coordinator, Participant) as not all of these will, necessarily, be exposed via the LB. > Each Service offered by XTS is deployed via JBossWS. XTS also maintains metadata about the endpoint which it advertises to other participants in the protocol. This metadata is currently kept in sync with the service, but it doesn't have to be. In this situation, the metadata could be configured to advertise the LB address, rather than the actual address of the service. This is also where the URL re-writing would occur to identify the individual node. An example of a class that creates the endpoint metadata is "RegistrationCoordinatorInitialisation". > I don't know what support popular load balancers have for the type of URL re-writing that I mention here. This should be investigated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:43:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:43:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1099) WS-BA to 2xJTA bridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1099: -------------------------------- Fix Version/s: (was: 6.later) > WS-BA to 2xJTA bridge > --------------------- > > Key: JBTM-1099 > URL: https://issues.jboss.org/browse/JBTM-1099 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework > Reporter: Paul Robinson > Labels: assign > Original Estimate: 1 week > Time Spent: 3 hours > Remaining Estimate: 4 days, 5 hours > > It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated. > There may be other windows in Compensate and Close. This needs investigating. > The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close. > This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:43:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:43:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1099) WS-BA to 2xJTA bridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1099: -------------------------------- Component/s: TxBridge XTS (was: TXFramework) > WS-BA to 2xJTA bridge > --------------------- > > Key: JBTM-1099 > URL: https://issues.jboss.org/browse/JBTM-1099 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TxBridge, XTS > Reporter: Paul Robinson > Labels: assign > Original Estimate: 1 week > Time Spent: 3 hours > Remaining Estimate: 4 days, 5 hours > > It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated. > There may be other windows in Compensate and Close. This needs investigating. > The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close. > This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:45:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:45:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1366) Create an XTS plugin for the Arquillian Transaction Extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1366. ------------------------------- Resolution: Won't Fix > Create an XTS plugin for the Arquillian Transaction Extension > ------------------------------------------------------------- > > Key: JBTM-1366 > URL: https://issues.jboss.org/browse/JBTM-1366 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: XTS > Reporter: Paul Robinson > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:46:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:46:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1367) Create a quickstart for the XTS plugin for the Arquillian Transaction Extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1367. ------------------------------- Resolution: Won't Fix > Create a quickstart for the XTS plugin for the Arquillian Transaction Extension > ------------------------------------------------------------------------------- > > Key: JBTM-1367 > URL: https://issues.jboss.org/browse/JBTM-1367 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, XTS > Reporter: Paul Robinson > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:48:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:48:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1441) Update XTS Demo to use new APIs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1441. ------------------------------- Resolution: Out of Date > Update XTS Demo to use new APIs > ------------------------------- > > Key: JBTM-1441 > URL: https://issues.jboss.org/browse/JBTM-1441 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Paul Robinson > Original Estimate: 1 week > Remaining Estimate: 1 week > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:48:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:48:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1467) Create a set of Koans for using Compensations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1467. ------------------------------- Fix Version/s: (was: 6.later) Resolution: Rejected > Create a set of Koans for using Compensations > --------------------------------------------- > > Key: JBTM-1467 > URL: https://issues.jboss.org/browse/JBTM-1467 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework, XTS > Reporter: Paul Robinson > > In the spirit of http://rubykoans.com/, but to learn how to use compensations. > In the long term we should use a Java EE Koan 'runner'. In the short term, try using Arquillian with some broken tests. We could do something to intercept logs for an appropriate error message to present the user. > Might also be worth having Arquillian stop on a failed test to prevent too many failures swamping the user. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:50:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1523) Try to have XTS enabled in standalone-full.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1523. ------------------------------- Fix Version/s: (was: 6.later) Resolution: Won't Fix > Try to have XTS enabled in standalone-full.xml > ---------------------------------------------- > > Key: JBTM-1523 > URL: https://issues.jboss.org/browse/JBTM-1523 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration, XTS > Reporter: Paul Robinson > > The problem is that XTS currently increases boot time by about 50%. Therefore it has to live in its own configuration. > If we can reduce this boot cost, we may be able to get it included in standalone-full.xml. > I think the main problem is the time it takes to register all the XTS Web Service endpoints. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:55:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:55:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1639) Improve XTS Api for looking up Recovery Manager to prevent developer from poling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1639: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Improve XTS Api for looking up Recovery Manager to prevent developer from poling > -------------------------------------------------------------------------------- > > Key: JBTM-1639 > URL: https://issues.jboss.org/browse/JBTM-1639 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently the developer needs to poll for the RecoveryManager as it's possible that the application can be deployed before the XTS subsystem has finished startup. > This issue was worked around in JBTM-1522 and in the TXBridge tests, by having the application poll until the RM was not null. > Two possible solutions: > Have a blocking call to XTSATRecoveryManager.getRecoveryManager() that doesn't return until there is an RM available. if we use the existing java method, we need to analyse all usages to make sure returning null is not a valid outcome. > Another solution is to find out how to delay the application's initialisation until after XTS has started. This puts the burden on the application developer to implement, but requires no changes to the XTS code. See JBTM-1522 for alternative mechanisms for initialising the application. I tried three and none of them fired after the server had booted. > To Reproduce > Put breakpoints on: > Application's usage of: XTSATRecoveryManager.getRecoveryManager(); //Stop all threads > XTSATRecoveryManager.setRecoveryManager() // stop on Thread only > Copy your application to the deploy directory (xtstest.war is a good choice). Now start the server with debugging enabled (suspend=y). To reproduce this you will see the XTSATRecoveryManager.setRecoveryManager() BP fire, and then shortly after the XTSATRecoveryManager.getRecoveryManager() BP will fire. Allow the getRecoveryManager to continue and you will notice it is null. Fix this problem, and the getRecoveryManager will wait until the setRecoveryManager is complete and thus always return a non-null RM. > Once this is fixed, find all occurrence of the polling work-around and have them use the solution to this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:55:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:55:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1688) TXBridge doesn't support "loops" or "diamonds" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1688: -------------------------------- Fix Version/s: (was: 6.later) > TXBridge doesn't support "loops" or "diamonds" > ---------------------------------------------- > > Key: JBTM-1688 > URL: https://issues.jboss.org/browse/JBTM-1688 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > > See here: http://docs.jboss.org/jbosstm/5.0.0.M2/guides/txbridge_guide/index.html#d0e590 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:56:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:56:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1688) TXBridge doesn't support "loops" or "diamonds" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1688: ----------------------------------- Assignee: (was: Gytis Trikleris) > TXBridge doesn't support "loops" or "diamonds" > ---------------------------------------------- > > Key: JBTM-1688 > URL: https://issues.jboss.org/browse/JBTM-1688 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge, XTS > Reporter: Paul Robinson > > See here: http://docs.jboss.org/jbosstm/5.0.0.M2/guides/txbridge_guide/index.html#d0e590 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:57:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:57:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1718) Resolve the ParticipantCompletion race condition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1718: ----------------------------------- Assignee: (was: Gytis Trikleris) > Resolve the ParticipantCompletion race condition > ------------------------------------------------ > > Key: JBTM-1718 > URL: https://issues.jboss.org/browse/JBTM-1718 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Paul Robinson > > This issue is documented here: JBTM-1429 > In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. Therefore it is much more likely to happen in a production environment. > Therefore we need to remove this race condition. It can be done in a proprietary mannor as we are not interoperating with another implementation ion local-only mode. When distributing the transaction we fall back to the standard protocol that is susceptible to the race condition. However, as we stated in the docs, this condition is unlikely to manifest in a distributed environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:57:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:57:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1718) Resolve the ParticipantCompletion race condition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1718: -------------------------------- Fix Version/s: (was: 6.later) > Resolve the ParticipantCompletion race condition > ------------------------------------------------ > > Key: JBTM-1718 > URL: https://issues.jboss.org/browse/JBTM-1718 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Paul Robinson > > This issue is documented here: JBTM-1429 > In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. Therefore it is much more likely to happen in a production environment. > Therefore we need to remove this race condition. It can be done in a proprietary mannor as we are not interoperating with another implementation ion local-only mode. When distributing the transaction we fall back to the standard protocol that is susceptible to the race condition. However, as we stated in the docs, this condition is unlikely to manifest in a distributed environment. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:58:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:58:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1789) Simplify deploy plugin configuration and don't deploy uber (shaded) jars In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1789: -------------------------------- Fix Version/s: 5.next > Simplify deploy plugin configuration and don't deploy uber (shaded) jars > ------------------------------------------------------------------------ > > Key: JBTM-1789 > URL: https://issues.jboss.org/browse/JBTM-1789 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Fix For: 5.next > > > There is currently configuration of the maven deploy plugin in several modules to either deploy or not deploy artifacts and poms to the Maven repo. The configuration could be simplified using properties, and the uber jars (generated by the shade plugin) should not be deployed to the Maven repository. > Here is the current deployment status and proposed for the modules. > ||Module Name||Current Deployment||Proposed|| > | Narayana: all | deployed | deployed | > | Narayana: common | deployed | deployed | > | Narayana: Arjunacore | deployed | deployed | > | Narayana: ArjunaCore arjuna | deployed | deployed | > | Narayana: ArjunaCore txoj | deployed | deployed | > | Narayana: ArjunaCore arjunacore | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTA | deployed | deployed | > | Narayana: ArjunaJTA jta | deployed | deployed | > | Narayana: ArjunaJTA cdi | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA jdbc | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA narayana-jta | deployed | {color:red} skipped {color} | > | Narayana: XTS | deployed | deployed | > | Narayana: XTS byteman_support | deployed | deployed | > | Narayana: XTS WSAS | skipped | skipped | > | Narayana: XTS WSAS xts-test-servlet | skipped | skipped | > | Narayana: XTS WS-C | skipped | skipped | > | Narayana: XTS WSCF | skipped | skipped | > | Narayana: XTS WS-T | skipped | skipped | > | Narayana: XTS WSTX | skipped | skipped | > | Narayana: XTS recovery | skipped | skipped | > | Narayana: XTS bridge | skipped | skipped | > | Narayana: XTS sar | skipped | skipped | > | Narayana: XTS jbossxts | deployed | deployed | > | Narayana: XTS localjunit | skipped | skipped | > | Narayana: XTS localjunit unit | skipped | skipped | > | Narayana: XTS WSTX11-interop | skipped | skipped | > | Narayana: XTS WSTFSC07-interop | skipped | skipped | > | Narayana: XTS localjunit xtstest | skipped | skipped | > | Narayana: XTS localjunit crash-recovery-tests | skipped | skipped | > | Narayana: ArjunaJTS | deployed | deployed | > | Narayana: ArjunaJTS idl | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS idl jacorb | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS orbportability | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jts | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jtax | skipped | {color:red} deployed {color} | > | Narayana: ArjuntaJTS narayana-jts-jacorb | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTS integration | deployed | deployed | > | Narayana: rest-tx | deployed | deployed | > | Narayana: rest-tx util | deployed | deployed | > | Narayana: rest-tx tx (RESTful API for Atomic Transactions) | deployed | deployed | > | Narayana: rest-tx webservice | skipped | skipped | > | Narayana: rest-tx integration | deployed | deployed | > | Narayana: txbridge | deployed | deployed | > | Narayana: fileio | deployed | deployed | > | Narayana: STM | skipped | skipped | > | Narayana: txframework | deployed | deployed | > | Narayana: narayana-full | skipped | skipped | > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 11:58:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 11:58:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1789) Simplify deploy plugin configuration and don't deploy uber (shaded) jars In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1789: ----------------------------------- Assignee: Tom Jenkinson (was: Paul Gier) > Simplify deploy plugin configuration and don't deploy uber (shaded) jars > ------------------------------------------------------------------------ > > Key: JBTM-1789 > URL: https://issues.jboss.org/browse/JBTM-1789 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Reporter: Paul Gier > Assignee: Tom Jenkinson > Fix For: 5.next > > > There is currently configuration of the maven deploy plugin in several modules to either deploy or not deploy artifacts and poms to the Maven repo. The configuration could be simplified using properties, and the uber jars (generated by the shade plugin) should not be deployed to the Maven repository. > Here is the current deployment status and proposed for the modules. > ||Module Name||Current Deployment||Proposed|| > | Narayana: all | deployed | deployed | > | Narayana: common | deployed | deployed | > | Narayana: Arjunacore | deployed | deployed | > | Narayana: ArjunaCore arjuna | deployed | deployed | > | Narayana: ArjunaCore txoj | deployed | deployed | > | Narayana: ArjunaCore arjunacore | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTA | deployed | deployed | > | Narayana: ArjunaJTA jta | deployed | deployed | > | Narayana: ArjunaJTA cdi | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA jdbc | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA narayana-jta | deployed | {color:red} skipped {color} | > | Narayana: XTS | deployed | deployed | > | Narayana: XTS byteman_support | deployed | deployed | > | Narayana: XTS WSAS | skipped | skipped | > | Narayana: XTS WSAS xts-test-servlet | skipped | skipped | > | Narayana: XTS WS-C | skipped | skipped | > | Narayana: XTS WSCF | skipped | skipped | > | Narayana: XTS WS-T | skipped | skipped | > | Narayana: XTS WSTX | skipped | skipped | > | Narayana: XTS recovery | skipped | skipped | > | Narayana: XTS bridge | skipped | skipped | > | Narayana: XTS sar | skipped | skipped | > | Narayana: XTS jbossxts | deployed | deployed | > | Narayana: XTS localjunit | skipped | skipped | > | Narayana: XTS localjunit unit | skipped | skipped | > | Narayana: XTS WSTX11-interop | skipped | skipped | > | Narayana: XTS WSTFSC07-interop | skipped | skipped | > | Narayana: XTS localjunit xtstest | skipped | skipped | > | Narayana: XTS localjunit crash-recovery-tests | skipped | skipped | > | Narayana: ArjunaJTS | deployed | deployed | > | Narayana: ArjunaJTS idl | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS idl jacorb | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS orbportability | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jts | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jtax | skipped | {color:red} deployed {color} | > | Narayana: ArjuntaJTS narayana-jts-jacorb | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTS integration | deployed | deployed | > | Narayana: rest-tx | deployed | deployed | > | Narayana: rest-tx util | deployed | deployed | > | Narayana: rest-tx tx (RESTful API for Atomic Transactions) | deployed | deployed | > | Narayana: rest-tx webservice | skipped | skipped | > | Narayana: rest-tx integration | deployed | deployed | > | Narayana: txbridge | deployed | deployed | > | Narayana: fileio | deployed | deployed | > | Narayana: STM | skipped | skipped | > | Narayana: txframework | deployed | deployed | > | Narayana: narayana-full | skipped | skipped | > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:00:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:00:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1860) Please document AtomicAction and TransactionStatusManager scanner. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1860: -------------------------------- Component/s: Documentation (was: Transaction Core) > Please document AtomicAction and TransactionStatusManager scanner. > ------------------------------------------------------------------ > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Ross > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:00:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:00:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1860) Please document AtomicAction and TransactionStatusManager scanner. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1860: ----------------------------------- Assignee: Tom Jenkinson (was: Tom Ross) > Please document AtomicAction and TransactionStatusManager scanner. > ------------------------------------------------------------------ > > Key: JBTM-1860 > URL: https://issues.jboss.org/browse/JBTM-1860 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Environment: JBoss EAP 5.x and 6.x > Reporter: Tom Ross > Assignee: Tom Jenkinson > > JBossTM provides two scanners AtomicAction and TransactionStatusManager to scan for expired records in transaction object store. There is very little documentation that describes what they do and how to enable them. > Please provide better documentation that describes thier functions, the differences between them and the dangers associated with their usage. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:05:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:05:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2120) Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2120: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2120 > URL: https://issues.jboss.org/browse/JBTM-2120 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Pull https://github.com/jbosstm/narayana/pull/598 added deferred throwables in case the XAR::end fails during commit. It doesn't handle the case of the HEURISTIC_ROLLBACK of a first resource where Narayana rolls back the remaining participants and then clears the failed/heuristic lists (and marks the txn as rolled back). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:07:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:07:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2151: ----------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:07:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:07:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2151: -------------------------------- Fix Version/s: 5.later (was: 6.later) > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Demonstrator, TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:09:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:09:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2180: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.next > > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:09:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:09:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2180: -------------------------------- Fix Version/s: 5.next > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.next > > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:13:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:13:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2225) Provide a BeanManager lookup option for use outside of WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2225: ----------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > Provide a BeanManager lookup option for use outside of WildFly > -------------------------------------------------------------- > > Key: JBTM-2225 > URL: https://issues.jboss.org/browse/JBTM-2225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently the compensations API uses JNDI to lookup the CDI BeanManager. This only works inside an application server. An alternative needs to be provided for when using the API inside standalone Weld container. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:13:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:13:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2225) Provide a BeanManager lookup option for use outside of WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2225: -------------------------------- Fix Version/s: 5.next > Provide a BeanManager lookup option for use outside of WildFly > -------------------------------------------------------------- > > Key: JBTM-2225 > URL: https://issues.jboss.org/browse/JBTM-2225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently the compensations API uses JNDI to lookup the CDI BeanManager. This only works inside an application server. An alternative needs to be provided for when using the API inside standalone Weld container. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:13:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:13:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2225) Provide a BeanManager lookup option for use outside of WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2225: -------------------------------- Component/s: Compensations (was: TXFramework) > Provide a BeanManager lookup option for use outside of WildFly > -------------------------------------------------------------- > > Key: JBTM-2225 > URL: https://issues.jboss.org/browse/JBTM-2225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently the compensations API uses JNDI to lookup the CDI BeanManager. This only works inside an application server. An alternative needs to be provided for when using the API inside standalone Weld container. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:14:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:14:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2270) When expose-all-logs is used with JTS then no participant for transaction is shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2270: ----------------------------------- Assignee: Michael Musgrove (was: Gytis Trikleris) > When expose-all-logs is used with JTS then no participant for transaction is shown > ----------------------------------------------------------------------------------- > > Key: JBTM-2270 > URL: https://issues.jboss.org/browse/JBTM-2270 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Ond?ej Chaloupka > Assignee: Michael Musgrove > > When expose-all-logs is set to true I'm not able to get any participants of the listed transaction. > This is log from operation to get type of transaction and then see all participants. > Reading type of the transaction: > Succesful management operation { > "operation" => "read-attribute", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "name" => "type" > } with result { > "outcome" => "success", > "result" => "CosTransactions/XAResourceRecord" > } > Getting participants: > Succesful management operation { > "operation" => "read-children-names", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "child-type" => "participants" > } with result { > "outcome" => "success", > "result" => [] > } -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:14:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:14:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2270) When expose-all-logs is used with JTS then no participant for transaction is shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2270: -------------------------------- Fix Version/s: (was: 6.later) > When expose-all-logs is used with JTS then no participant for transaction is shown > ----------------------------------------------------------------------------------- > > Key: JBTM-2270 > URL: https://issues.jboss.org/browse/JBTM-2270 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Ond?ej Chaloupka > Assignee: Michael Musgrove > > When expose-all-logs is set to true I'm not able to get any participants of the listed transaction. > This is log from operation to get type of transaction and then see all participants. > Reading type of the transaction: > Succesful management operation { > "operation" => "read-attribute", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "name" => "type" > } with result { > "outcome" => "success", > "result" => "CosTransactions/XAResourceRecord" > } > Getting participants: > Succesful management operation { > "operation" => "read-children-names", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "child-type" => "participants" > } with result { > "outcome" => "success", > "result" => [] > } -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:15:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:15:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2270) When expose-all-logs is used with JTS then no participant for transaction is shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2270: -------------------------------- Component/s: Tooling > When expose-all-logs is used with JTS then no participant for transaction is shown > ----------------------------------------------------------------------------------- > > Key: JBTM-2270 > URL: https://issues.jboss.org/browse/JBTM-2270 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS, Tooling > Reporter: Ond?ej Chaloupka > Assignee: Michael Musgrove > > When expose-all-logs is set to true I'm not able to get any participants of the listed transaction. > This is log from operation to get type of transaction and then see all participants. > Reading type of the transaction: > Succesful management operation { > "operation" => "read-attribute", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "name" => "type" > } with result { > "outcome" => "success", > "result" => "CosTransactions/XAResourceRecord" > } > Getting participants: > Succesful management operation { > "operation" => "read-children-names", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "child-type" => "participants" > } with result { > "outcome" => "success", > "result" => [] > } -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:15:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:15:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2270) When expose-all-logs is used with JTS then no participant for transaction is shown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2270: ----------------------------------- Assignee: (was: Michael Musgrove) > When expose-all-logs is used with JTS then no participant for transaction is shown > ----------------------------------------------------------------------------------- > > Key: JBTM-2270 > URL: https://issues.jboss.org/browse/JBTM-2270 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS, Tooling > Reporter: Ond?ej Chaloupka > > When expose-all-logs is set to true I'm not able to get any participants of the listed transaction. > This is log from operation to get type of transaction and then see all participants. > Reading type of the transaction: > Succesful management operation { > "operation" => "read-attribute", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "name" => "type" > } with result { > "outcome" => "success", > "result" => "CosTransactions/XAResourceRecord" > } > Getting participants: > Succesful management operation { > "operation" => "read-children-names", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff0a280545:2d64af2f:54378290:3c") > ], > "child-type" => "participants" > } with result { > "outcome" => "success", > "result" => [] > } -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:16:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:16:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2328) Deprecate the HeuristicInformation interface In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2328: -------------------------------- Fix Version/s: 5.next > Deprecate the HeuristicInformation interface > -------------------------------------------- > > Key: JBTM-2328 > URL: https://issues.jboss.org/browse/JBTM-2328 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > There exists and HeuristicInformation interface (https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/HeuristicInformation.java) which was intended to allow an AbstractRecord implementor to provide additional details about the heuristic state of the record as well as provide access to tooling to clear the state of the heuristic within the (potentially remove) resource manager. > This has been decoupled from the tooling for many iterations (the ability to resolve the heuristic appears as though it was never wired up) and though Mike is updating the tooling to access the additional context of the heuristic state we do not propose to continue with this as the recommendation of resolving heuristics. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:17:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:17:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2345) Off image storage for docker transaction service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2345: ----------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > Off image storage for docker transaction service > ------------------------------------------------ > > Key: JBTM-2345 > URL: https://issues.jboss.org/browse/JBTM-2345 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System, Cloud, JTS > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Gytis Trikleris > Labels: docker > > Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jul 28 12:21:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 28 Jul 2015 12:21:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2436) Use ManagedThreadFactory, if available, to create PeriodicRecovery thread In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2436. ------------------------------- Resolution: Rejected Not best practice as it adds an extra dependency > Use ManagedThreadFactory, if available, to create PeriodicRecovery thread > ------------------------------------------------------------------------- > > Key: JBTM-2436 > URL: https://issues.jboss.org/browse/JBTM-2436 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 29 04:25:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 29 Jul 2015 04:25:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2298: -------------------------------- Fix Version/s: 5.next > Use Project Atomic for docker image(s) > -------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 29 04:27:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 29 Jul 2015 04:27:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2345) Off image storage for docker transaction service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2345: -------------------------------- Fix Version/s: 5.later > Off image storage for docker transaction service > ------------------------------------------------ > > Key: JBTM-2345 > URL: https://issues.jboss.org/browse/JBTM-2345 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System, Cloud, JTS > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Gytis Trikleris > Labels: docker > Fix For: 5.later > > > Now we have a docker image for JTS we need to look at making the state available after the image(s) go away. Remember that docker produces immutable images, so any state change that occurs within the running instance will be lost when the image dies, is taken out of service etc. Currently the docker image for JTS we have will store all of the transaction log information within the image, which is fine for testing purposes but not for a running deployment. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 29 06:10:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 29 Jul 2015 06:10:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-846) Allow transactional MSC and WildFly EJB container to operate with different configurations for transaction/recovery manager in a single JVM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-846: ---------------------------------- Assignee: Michael Musgrove (was: Gytis Trikleris) > Allow transactional MSC and WildFly EJB container to operate with different configurations for transaction/recovery manager in a single JVM > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-846 > URL: https://issues.jboss.org/browse/JBTM-846 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA, JTS, Recovery, Transaction Core, XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 6.later > > > ** This Jira is a work in progress - I (Paul) will update the details here once the requirements in https://community.jboss.org/message/828391 are clarified. ** > The use case provided for this is to run a separate transaction/recovery manager for Transactional MSC to the one that WildFly is using for its (JTA/JTS) EJB container. > This will require removal of much of the static configuration state such as StateManager references to ObjectStore -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jul 29 08:15:06 2015 From: issues at jboss.org (Paul Robinson (JIRA)) Date: Wed, 29 Jul 2015 08:15:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-785) Document configuration of standalone client In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093890#comment-13093890 ] Paul Robinson commented on JBTM-785: ------------------------------------ I think the idea was to document how to have an XTS client that is not running inside WildFly or JBoss EAP. This could be Tomcat or a plain Java application. > Document configuration of standalone client > ------------------------------------------- > > Key: JBTM-785 > URL: https://issues.jboss.org/browse/JBTM-785 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation, XTS > Affects Versions: 4.12.0 > Reporter: Andrew Dinn > > Need to explain how to set up standalone client so it can be deployed embedded without the need to expose completion initiator service endpoints. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 30 04:21:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jul 2015 04:21:03 -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 ] Tom Jenkinson updated JBTM-1107: -------------------------------- Component/s: Compensations (was: TXFramework) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > 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.3.15#6346) From issues at jboss.org Thu Jul 30 04:23:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jul 2015 04:23:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2151: -------------------------------- Component/s: Compensations (was: TXFramework) > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations, Demonstrator > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 30 04:23:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jul 2015 04:23:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2340) Implement POC of MongoDB extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2340: -------------------------------- Component/s: Compensations (was: TXFramework) > Implement POC of MongoDB extension > ---------------------------------- > > Key: JBTM-2340 > URL: https://issues.jboss.org/browse/JBTM-2340 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 30 04:23:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jul 2015 04:23:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2339) MongoDB extension for Compensations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2339: -------------------------------- Component/s: Compensations (was: TXFramework) > MongoDB extension for Compensations > ----------------------------------- > > Key: JBTM-2339 > URL: https://issues.jboss.org/browse/JBTM-2339 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jul 30 04:23:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 30 Jul 2015 04:23:07 -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 ] Tom Jenkinson updated JBTM-1107: -------------------------------- Forum Reference: https://developer.jboss.org/thread/260723 > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > 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.3.15#6346) From issues at jboss.org Fri Jul 31 05:47:04 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 31 Jul 2015 05:47: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:comment-tabpanel&focusedCommentId=13094555#comment-13094555 ] Gytis Trikleris commented on JBTM-2458: --------------------------------------- One of the Tom's suggestions during the Narayana f2f: {code} BusinessLogic foo = () -> collectionWrapper.updateOne(); tx.begin(); foo(); // annotations on it tx.commit(); tx.begin(); tx.onFailure(compensationHandler).onSuccess(confirmationHandler).enlist(foo); tx.onFailure(compensationHandler2).enlist(foo2); tx.commit() {code} > 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.3.15#6346) From issues at jboss.org Fri Jul 31 06:11:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 31 Jul 2015 06:11:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1639) Improve XTS Api for looking up Recovery Manager to prevent developer from poling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris resolved JBTM-1639. ----------------------------------- Fix Version/s: (was: 5.next) Resolution: Out of Date This was resolved by https://issues.jboss.org/browse/JBTM-1917 > Improve XTS Api for looking up Recovery Manager to prevent developer from poling > -------------------------------------------------------------------------------- > > Key: JBTM-1639 > URL: https://issues.jboss.org/browse/JBTM-1639 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > > Currently the developer needs to poll for the RecoveryManager as it's possible that the application can be deployed before the XTS subsystem has finished startup. > This issue was worked around in JBTM-1522 and in the TXBridge tests, by having the application poll until the RM was not null. > Two possible solutions: > Have a blocking call to XTSATRecoveryManager.getRecoveryManager() that doesn't return until there is an RM available. if we use the existing java method, we need to analyse all usages to make sure returning null is not a valid outcome. > Another solution is to find out how to delay the application's initialisation until after XTS has started. This puts the burden on the application developer to implement, but requires no changes to the XTS code. See JBTM-1522 for alternative mechanisms for initialising the application. I tried three and none of them fired after the server had booted. > To Reproduce > Put breakpoints on: > Application's usage of: XTSATRecoveryManager.getRecoveryManager(); //Stop all threads > XTSATRecoveryManager.setRecoveryManager() // stop on Thread only > Copy your application to the deploy directory (xtstest.war is a good choice). Now start the server with debugging enabled (suspend=y). To reproduce this you will see the XTSATRecoveryManager.setRecoveryManager() BP fire, and then shortly after the XTSATRecoveryManager.getRecoveryManager() BP will fire. Allow the getRecoveryManager to continue and you will notice it is null. Fix this problem, and the getRecoveryManager will wait until the setRecoveryManager is complete and thus always return a non-null RM. > Once this is fixed, find all occurrence of the polling work-around and have them use the solution to this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 31 06:12:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 31 Jul 2015 06:12:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1952) Implement XTSATRecoveryManager and XTSBARecoveryManager injection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-1952: ---------------------------------- Description: Change polling introduced with JBTM-1917 with proper CDI injection. See JBTM-1639 for the detailed background on the issue before JBTM-1917 workaround. was:Change polling introduced with JBTM-1917 with proper CDI injection. > Implement XTSATRecoveryManager and XTSBARecoveryManager injection > ----------------------------------------------------------------- > > Key: JBTM-1952 > URL: https://issues.jboss.org/browse/JBTM-1952 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 6.later > > > Change polling introduced with JBTM-1917 with proper CDI injection. > See JBTM-1639 for the detailed background on the issue before JBTM-1917 workaround. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 31 06:54:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 31 Jul 2015 06:54:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2470) Add attribute to JTS the TransactionServer to start embedded RecoveryManager In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2470: ------------------------------------- Summary: Add attribute to JTS the TransactionServer to start embedded RecoveryManager Key: JBTM-2470 URL: https://issues.jboss.org/browse/JBTM-2470 Project: JBoss Transaction Manager Issue Type: Task Components: JTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next Add -recovery attribute to TransactionService. This is needed for JTS docker file. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 31 06:58:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 31 Jul 2015 06:58:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2470) Add attribute to JTS the TransactionServer to start embedded RecoveryManager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2470: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/890 > Add attribute to JTS the TransactionServer to start embedded RecoveryManager > ---------------------------------------------------------------------------- > > Key: JBTM-2470 > URL: https://issues.jboss.org/browse/JBTM-2470 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Add -recovery attribute to TransactionService. > This is needed for JTS docker file. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jul 31 08:47:04 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 31 Jul 2015 08:47:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094652#comment-13094652 ] Gytis Trikleris commented on JBTM-2296: --------------------------------------- Moved both dockerfiles to jboss-dockerfiles/narayana repo on my account: https://github.com/gytis/jboss-dockerfiles-narayana/tree/master-JBTM-2296-jts-and-jacorb. Now need to wait for the Narayana release with https://issues.jboss.org/browse/JBTM-2470 in it. > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Cloud, JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.15#6346)