From issues at jboss.org Mon Aug 3 05:50:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 3 Aug 2015 05:50: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: [ https://issues.jboss.org/browse/JBTM-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2470: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 Mon Aug 3 09:43:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 09:43:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2471) Provide a mechanism to get stack dumps from the C++ binaries In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2471: ----------------------------------- Summary: Provide a mechanism to get stack dumps from the C++ binaries Key: JBTM-2471 URL: https://issues.jboss.org/browse/JBTM-2471 Project: JBoss Transaction Manager Issue Type: Feature Request Components: BlackTie Reporter: Tom Jenkinson Assignee: Amos Feng Currently debugging BlackTie is problematic as we are reliant on logs to know what was happening on stack dumping the application server to guess what is being called. It would be useful to provide a method to do this. Potentially an open socket to connect to could dump the stacks or understanding how to do this on Windows and Linux natively. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 09:46:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 09:46:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2472) Move the jboss-as checking to BlackTie build part In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2472: ----------------------------------- Summary: Move the jboss-as checking to BlackTie build part Key: JBTM-2472 URL: https://issues.jboss.org/browse/JBTM-2472 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Currently only blacktie uses jboss-as version and requires it to be in sync with the application server. We should move this to that part of the build in order to not prevent other aspects of the build breaking when the version updates: Move the jboss-as.version from /pom.xml to /blacktie/pom.xml Move the checking of the jboss-as version from function jboss-as to function blacktie: https://github.com/jbosstm/narayana/blob/master/scripts/hudson/narayana.sh#L217 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 09:48:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 09:48:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2473) Document qa/ build suite In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2473: ----------------------------------- Summary: Document qa/ build suite Key: JBTM-2473 URL: https://issues.jboss.org/browse/JBTM-2473 Project: JBoss Transaction Manager Issue Type: Task Components: Testing Reporter: Tom Jenkinson Assignee: Tom Jenkinson There is a wealth of testing in the qa/ testsuite but it is not accessible to understand what is being tested by it. * How do we evaluate the impact of running less of the suite * Is it possible to run the suite with other object stores easily? * What is the quantified value of running the whole suite * Can we run with different ORBs -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 09:48:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 09:48:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2471) Provide a mechanism to get stack dumps from the C++ binaries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2471: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Provide a mechanism to get stack dumps from the C++ binaries > ------------------------------------------------------------ > > Key: JBTM-2471 > URL: https://issues.jboss.org/browse/JBTM-2471 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > > Currently debugging BlackTie is problematic as we are reliant on logs to know what was happening on stack dumping the application server to guess what is being called. It would be useful to provide a method to do this. > Potentially an open socket to connect to could dump the stacks or understanding how to do this on Windows and Linux natively. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 09:48:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 09:48:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2472) Move the jboss-as checking to BlackTie build part In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2472: -------------------------------- Issue Type: Task (was: Feature Request) > Move the jboss-as checking to BlackTie build part > ------------------------------------------------- > > Key: JBTM-2472 > URL: https://issues.jboss.org/browse/JBTM-2472 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently only blacktie uses jboss-as version and requires it to be in sync with the application server. We should move this to that part of the build in order to not prevent other aspects of the build breaking when the version updates: > Move the jboss-as.version from /pom.xml to /blacktie/pom.xml > Move the checking of the jboss-as version from function jboss-as to function blacktie: > https://github.com/jbosstm/narayana/blob/master/scripts/hudson/narayana.sh#L217 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 09:55:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 09:55:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095050#comment-13095050 ] Tom Jenkinson commented on JBTM-1820: ------------------------------------- We need to create our own quickstart for this. We could use WildFly-camel: https://github.com/wildfly-extras/wildfly-camel but probably would be easier to just use a main and spring. Maybe sequence it after JBTM-855 if you want to go spring route. > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 6.later > > > From Ning Jiang (njiang at redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 09:56:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 09:56:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-855: ---------------------------------- Assignee: Amos Feng (was: Gytis Trikleris) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 6.later > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Simple example showing TS in use by tomcat and spring -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 10:03:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 10:03:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-855: ------------------------------- Description: The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery (was: Simple example showing TS in use by tomcat and spring) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 6.later > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 10:09:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 10:09:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2476: ----------------------------------- Summary: When a transaction times out, print the stack traces of the threads involved Key: JBTM-2476 URL: https://issues.jboss.org/browse/JBTM-2476 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 10:10:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 10:10:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2477) Measure timed out transactions in TxStats In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2477: ----------------------------------- Summary: Measure timed out transactions in TxStats Key: JBTM-2477 URL: https://issues.jboss.org/browse/JBTM-2477 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Tooling Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.next Will be useful for monitoring according to GSS -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 10:11:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 10:11:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2478) Use Flame Graph tool In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2478: ----------------------------------- Summary: Use Flame Graph tool Key: JBTM-2478 URL: https://issues.jboss.org/browse/JBTM-2478 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Performance Testing Reporter: Tom Jenkinson Assignee: Michael Musgrove Tools and instructions are at: https://github.com/jesperpedersen/perfjava/ <-- CPU sampling https://github.com/jesperpedersen/javamemflame <-- Memory allocation tracking Both use Agent_OnLoad/Agent_OnUnload, so better for smaller tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 11:47:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 11:47:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2478) Use Flame Graph tool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095111#comment-13095111 ] Tom Jenkinson commented on JBTM-2478: ------------------------------------- http://techblog.netflix.com/2015/07/java-in-flames.html > Use Flame Graph tool > -------------------- > > Key: JBTM-2478 > URL: https://issues.jboss.org/browse/JBTM-2478 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > Tools and instructions are at: > https://github.com/jesperpedersen/perfjava/ <-- CPU sampling > https://github.com/jesperpedersen/javamemflame <-- Memory allocation tracking > Both use Agent_OnLoad/Agent_OnUnload, so better for smaller tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 12:09:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 12:09:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2478) Use Flame Graph tool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095118#comment-13095118 ] Tom Jenkinson commented on JBTM-2478: ------------------------------------- a "Tricks" section to the README.md if the SVG file gets too big. Brendan is working on a Python version of FlameGraph https://github.com/brendangregg/FlameGraph/tree/master/dev which has search support: Search -> com/arjuna -> Purple nodes > Use Flame Graph tool > -------------------- > > Key: JBTM-2478 > URL: https://issues.jboss.org/browse/JBTM-2478 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > Tools and instructions are at: > https://github.com/jesperpedersen/perfjava/ <-- CPU sampling > https://github.com/jesperpedersen/javamemflame <-- Memory allocation tracking > Both use Agent_OnLoad/Agent_OnUnload, so better for smaller tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 3 12:58:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 12:58:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2468) xts, jts and rts performance comparison job has failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095139#comment-13095139 ] Tom Jenkinson commented on JBTM-2468: ------------------------------------- Please can you provide a link to the job? Is there a reason it can't be ran on ams2? > 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 Aug 3 13:06:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 13:06:02 -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.later (was: 5.next) > 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.later > > > 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 Mon Aug 3 13:07:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 13:07: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:comment-tabpanel&focusedCommentId=13095143#comment-13095143 ] Tom Jenkinson commented on JBTM-2464: ------------------------------------- Can this be closed? > 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 Mon Aug 3 13:14:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 13:14:04 -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=13095146#comment-13095146 ] Tom Jenkinson commented on JBTM-2460: ------------------------------------- I have a feeling this was fixed in the SPI itself? Is this issue still 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 Aug 3 13:19:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Aug 2015 13:19:02 -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: -------------------------------- Component/s: (was: Documentation) > 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 > 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 Tue Aug 4 05:31:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 4 Aug 2015 05:31: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: Resolved (was: Pull Request Sent) Resolution: Done > 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 Aug 4 05:35:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 4 Aug 2015 05:35: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=13095292#comment-13095292 ] Michael Musgrove commented on JBTM-2460: ---------------------------------------- Scott is seeing an issue with the fix but I am unable to duplicate it: http://brontes.lab.eng.brq.redhat.com/repository/download/WF_PullRequest_Windows/63128:id/testsuite/compat/target/jbossas/standalone/log/server.log > 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 Tue Aug 4 08:25:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Aug 2015 08:25:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2479) Do not run maven rulecheck when -DskipTests is enabled In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2479: ----------------------------------- Summary: Do not run maven rulecheck when -DskipTests is enabled Key: JBTM-2479 URL: https://issues.jboss.org/browse/JBTM-2479 Project: JBoss Transaction Manager Issue Type: Task Reporter: Tom Jenkinson Assignee: Tom Jenkinson If you don't provide clean the rule check can easily fail: {code} [INFO] Checking 3 byteman scripts in C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V CFG.carryForward: unexpected! invalid open enters count for block L242951774 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.shutdown(Z)V exits unaccounted for in block B4 [ERROR] Checking byteman script rules failed with 1 errors [ERROR] ERROR : Unexpected exception transforming class com.arjuna.ats.arjuna.coordinator.TransactionReaper using rule "ReaperTestCase3 unlatch reaper and reaper worker" loaded from C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes\reaper.btm line 326 java.lang.NullPointerException {code} So it is advantageous not to run the rulecheck with skipTests as in: ./build.sh install -DskipTests -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 4 08:26:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Aug 2015 08:26:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2479) Do not run maven rulecheck when -DskipTests is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2479: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/891 > Do not run maven rulecheck when -DskipTests is enabled > ------------------------------------------------------ > > Key: JBTM-2479 > URL: https://issues.jboss.org/browse/JBTM-2479 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > If you don't provide clean the rule check can easily fail: > {code} > [INFO] Checking 3 byteman scripts in C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L242951774 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.shutdown(Z)V > exits unaccounted for in block B4 > [ERROR] Checking byteman script rules failed with 1 errors > [ERROR] ERROR : Unexpected exception transforming class com.arjuna.ats.arjuna.coordinator.TransactionReaper using rule "ReaperTestCase3 unlatch reaper and reaper worker" loaded from C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes\reaper.btm line 326 > java.lang.NullPointerException > {code} > So it is advantageous not to run the rulecheck with skipTests as in: > ./build.sh install -DskipTests -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 4 08:48:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Aug 2015 08:48:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2472) Move the jboss-as checking to BlackTie build part In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2472: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/892 > Move the jboss-as checking to BlackTie build part > ------------------------------------------------- > > Key: JBTM-2472 > URL: https://issues.jboss.org/browse/JBTM-2472 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently only blacktie uses jboss-as version and requires it to be in sync with the application server. We should move this to that part of the build in order to not prevent other aspects of the build breaking when the version updates: > Move the jboss-as.version from /pom.xml to /blacktie/pom.xml > Move the checking of the jboss-as version from function jboss-as to function blacktie: > https://github.com/jbosstm/narayana/blob/master/scripts/hudson/narayana.sh#L217 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 4 09:35:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Aug 2015 09:35:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2480: ----------------------------------- Summary: Provide documentation of how to integrate with Karaf Key: JBTM-2480 URL: https://issues.jboss.org/browse/JBTM-2480 Project: JBoss Transaction Manager Issue Type: Task Components: Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next This should include recovery information -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 4 09:44:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Aug 2015 09:44: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: 6.later (was: 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: Tom Jenkinson > Fix For: 6.later > > > 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 Aug 4 09:44:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Aug 2015 09:44:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2480: ----------------------------------- Assignee: Amos Feng (was: Tom Jenkinson) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 4 09:47:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Aug 2015 09:47:01 -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: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/893 > 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 > 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 Tue Aug 4 09:50:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Aug 2015 09:50:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2479) Do not run maven rulecheck when -DskipTests is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2479: -------------------------------- Component/s: Build System > Do not run maven rulecheck when -DskipTests is enabled > ------------------------------------------------------ > > Key: JBTM-2479 > URL: https://issues.jboss.org/browse/JBTM-2479 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > If you don't provide clean the rule check can easily fail: > {code} > [INFO] Checking 3 byteman scripts in C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L242951774 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.shutdown(Z)V > exits unaccounted for in block B4 > [ERROR] Checking byteman script rules failed with 1 errors > [ERROR] ERROR : Unexpected exception transforming class com.arjuna.ats.arjuna.coordinator.TransactionReaper using rule "ReaperTestCase3 unlatch reaper and reaper worker" loaded from C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes\reaper.btm line 326 > java.lang.NullPointerException > {code} > So it is advantageous not to run the rulecheck with skipTests as in: > ./build.sh install -DskipTests -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 4 09:54:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 4 Aug 2015 09:54:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2481: ----------------------------------- Summary: Automate NRP Key: JBTM-2481 URL: https://issues.jboss.org/browse/JBTM-2481 Project: JBoss Transaction Manager Issue Type: Task Components: Release Process Reporter: Tom Jenkinson Assignee: Gytis Trikleris Fix For: 5.later There are a number of steps on NRP that could be automated using Jira API. Lets try to do that: https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 05:28:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:28:02 -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: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 > 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 Aug 5 05:28:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:28:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2472) Move the jboss-as checking to BlackTie build part In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2472: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Move the jboss-as checking to BlackTie build part > ------------------------------------------------- > > Key: JBTM-2472 > URL: https://issues.jboss.org/browse/JBTM-2472 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently only blacktie uses jboss-as version and requires it to be in sync with the application server. We should move this to that part of the build in order to not prevent other aspects of the build breaking when the version updates: > Move the jboss-as.version from /pom.xml to /blacktie/pom.xml > Move the checking of the jboss-as version from function jboss-as to function blacktie: > https://github.com/jbosstm/narayana/blob/master/scripts/hudson/narayana.sh#L217 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 05:28:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:28:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2479) Do not run maven rulecheck when -DskipTests is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2479: -------------------------------- Fix Version/s: 5.next > Do not run maven rulecheck when -DskipTests is enabled > ------------------------------------------------------ > > Key: JBTM-2479 > URL: https://issues.jboss.org/browse/JBTM-2479 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > If you don't provide clean the rule check can easily fail: > {code} > [INFO] Checking 3 byteman scripts in C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L242951774 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.shutdown(Z)V > exits unaccounted for in block B4 > [ERROR] Checking byteman script rules failed with 1 errors > [ERROR] ERROR : Unexpected exception transforming class com.arjuna.ats.arjuna.coordinator.TransactionReaper using rule "ReaperTestCase3 unlatch reaper and reaper worker" loaded from C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes\reaper.btm line 326 > java.lang.NullPointerException > {code} > So it is advantageous not to run the rulecheck with skipTests as in: > ./build.sh install -DskipTests -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 05:28:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:28:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2479) Do not run maven rulecheck when -DskipTests is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2479: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Do not run maven rulecheck when -DskipTests is enabled > ------------------------------------------------------ > > Key: JBTM-2479 > URL: https://issues.jboss.org/browse/JBTM-2479 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > If you don't provide clean the rule check can easily fail: > {code} > [INFO] Checking 3 byteman scripts in C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L242951774 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.shutdown(Z)V > exits unaccounted for in block B4 > [ERROR] Checking byteman script rules failed with 1 errors > [ERROR] ERROR : Unexpected exception transforming class com.arjuna.ats.arjuna.coordinator.TransactionReaper using rule "ReaperTestCase3 unlatch reaper and reaper worker" loaded from C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes\reaper.btm line 326 > java.lang.NullPointerException > {code} > So it is advantageous not to run the rulecheck with skipTests as in: > ./build.sh install -DskipTests -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2477) Measure timed out transactions in TxStats In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2477: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > Measure timed out transactions in TxStats > ----------------------------------------- > > Key: JBTM-2477 > URL: https://issues.jboss.org/browse/JBTM-2477 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Will be useful for monitoring according to GSS -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2480: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2476: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2468) xts, jts and rts performance comparison job has failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2468: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > 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 Wed Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -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:all-tabpanel ] Tom Jenkinson updated JBTM-2467: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > 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 Wed Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -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 ] Tom Jenkinson updated JBTM-2460: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > 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 Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -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 ] Tom Jenkinson updated JBTM-2458: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > 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 Wed Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -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.2.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.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 Wed Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -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.2.1) > 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 Wed Aug 5 05:30:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:08 -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.2.1) > 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 Aug 5 05:30:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:09 -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.2.1) > 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 Aug 5 05:30:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:09 -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 (was: 5.2.1) > 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 Wed Aug 5 05:30:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:09 -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 (was: 5.2.1) > 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 Aug 5 05:30:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:09 -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.2.1) > 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 Aug 5 05:30:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:09 -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.2.1) > 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 Aug 5 05:30:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:09 -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.2.1) > 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 Aug 5 05:30:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:09 -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 (was: 5.2.1) > 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 Wed Aug 5 05:30:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:09 -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 (was: 5.2.1) > 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 Wed Aug 5 05:30:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:09 -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.2.1) > 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 Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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.2.1) > 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 Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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 (was: 5.2.1) > 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 Wed Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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: 5.2.1) > 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 Wed Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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: 5.2.1) > 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 Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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: 5.2.1) > 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 Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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.2.1) > 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 Wed Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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: 5.2.1) > 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 Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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: 5.2.1) > 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 Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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: 5.2.1) > 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 Aug 5 05:30:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:10 -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: 5.2.1) > 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 Aug 5 05:30:11 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:11 -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 (was: 5.2.1) > 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 Wed Aug 5 05:30:11 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:30:11 -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 (was: 5.2.1) > 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 Wed Aug 5 05:39:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:39:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2482) Update pre-release.sh to update the version of Narayana in the performance repo In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2482: ----------------------------------- Summary: Update pre-release.sh to update the version of Narayana in the performance repo Key: JBTM-2482 URL: https://issues.jboss.org/browse/JBTM-2482 Project: JBoss Transaction Manager Issue Type: Task Components: Release Process Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Currently the version number in the performance repo is a manual step -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 05:41:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 05:41:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2482) Update pre-release.sh to update the version of Narayana in the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2482. --------------------------------- Resolution: Done Fixed in https://github.com/jbosstm/narayana/commit/a72922952f925a96c02405a170c81810649ce184 > Update pre-release.sh to update the version of Narayana in the performance repo > ------------------------------------------------------------------------------- > > Key: JBTM-2482 > URL: https://issues.jboss.org/browse/JBTM-2482 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently the version number in the performance repo is a manual step -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 07:23:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 5 Aug 2015 07:23:02 -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=13095709#comment-13095709 ] Gytis Trikleris commented on JBTM-928: -------------------------------------- [~tomjenkinson], these test still don't work. Shall I investigate further or keep them ignored? > 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 Wed Aug 5 09:33:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 5 Aug 2015 09:33:02 -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=13095778#comment-13095778 ] Tom Jenkinson commented on JBTM-928: ------------------------------------ I think we need to keep them ignored then and schedule the work for some point in the future - at least we know they don't work and should be able to now - thanks > 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 Wed Aug 5 09:40:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 5 Aug 2015 09:40: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:all-tabpanel ] Gytis Trikleris updated JBTM-928: --------------------------------- Fix Version/s: (was: 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 > > 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 Wed Aug 5 10:19:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 5 Aug 2015 10:19: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 ] Gytis Trikleris updated JBTM-2225: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/894 > 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 Wed Aug 5 10:47:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 5 Aug 2015 10:47:03 -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 ] Gytis Trikleris updated JBTM-2296: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jboss-dockerfiles/narayana/pull/2 > 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 Aug 5 11:20:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 5 Aug 2015 11:20:02 -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 ] Gytis Trikleris updated JBTM-2296: ---------------------------------- Git Pull Request: https://github.com/jboss-dockerfiles/narayana/pull/2, https://github.com/jbosstm/quickstart/pull/145 (was: https://github.com/jboss-dockerfiles/narayana/pull/2) > 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 Aug 5 11:24:01 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 5 Aug 2015 11:24:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2483) Investigate ways to test Docker quickstarts In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2483: ------------------------------------- Summary: Investigate ways to test Docker quickstarts Key: JBTM-2483 URL: https://issues.jboss.org/browse/JBTM-2483 Project: JBoss Transaction Manager Issue Type: Task Components: Cloud Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next Currently there is only one quickstart for docker (at the moment in the PR queue), but its tests are disabled by default. However, it would be good to run them in our CI. We'll have the same problem in the future with Kubernetes quickstarts. Maybe Arquillian Cube is something what could help? -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 5 11:54:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 5 Aug 2015 11:54:02 -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 ] Gytis Trikleris updated JBTM-2225: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 Thu Aug 6 08:58:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 6 Aug 2015 08:58: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=13096177#comment-13096177 ] Michael Musgrove commented on JBTM-2454: ---------------------------------------- I am also having issues with the compensations module when I run it manually on lancel: Running org.jboss.narayana.compensations.integration.beanManager.BeanManagerUtilTestWeld Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.457 sec <<< FAILURE! org.jboss.narayana.compensations.integration.beanManager.BeanManagerUtilTestWeld Time elapsed: 4.455 sec <<< ERROR! java.lang.IncompatibleClassChangeError: null at java.security.AccessController.doPrivileged(AccessController.java:503) at org.jboss.weldx.transaction.UserTransaction$1730945462$Proxy$_$$_Weld$Proxy$.(Unknown Source) at java.lang.J9VMInternals.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1932) at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33) at java.security.AccessController.doPrivileged(AccessController.java:559) at org.jboss.weld.bean.proxy.ProxyFactory.create(ProxyFactory.java:303) at org.jboss.weld.bean.builtin.ee.AbstractEEBean.(AbstractEEBean.java:36) at org.jboss.weld.bean.builtin.ee.UserTransactionBean.(UserTransactionBean.java:50) at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:251) at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:386) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.startContainer(TestContainer.java:273) at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer.deploy(WeldEEMockContainer.java:105) 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:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) 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:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) 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:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) 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:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) 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:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:507) 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) > 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 Thu Aug 6 09:14:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 6 Aug 2015 09:14: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=13096192#comment-13096192 ] Gytis Trikleris commented on JBTM-2454: --------------------------------------- [~mmusgrov], that's the new test I've added yesterday. Do you have a link to the build? > 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 Thu Aug 6 09:38:04 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 6 Aug 2015 09:38:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2484) JTSRemote_TimeoutTest from jtsremote tests failed on local cluster In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2484: -------------------------------------- Summary: JTSRemote_TimeoutTest from jtsremote tests failed on local cluster Key: JBTM-2484 URL: https://issues.jboss.org/browse/JBTM-2484 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Affects Versions: 5.2.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 6.later Attachments: JTSRemote_TimeoutTest.tar The only error is is in the client when it tries to rollback the transaction (see attached logs): bq. FATAL: ARJUNA022006: The ORB has not been initialized yet -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 6 09:38:06 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 6 Aug 2015 09:38:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2484) JTSRemote_TimeoutTest from jtsremote tests failed on local cluster In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2484: ----------------------------------- Attachment: JTSRemote_TimeoutTest.tar > JTSRemote_TimeoutTest from jtsremote tests failed on local cluster > ------------------------------------------------------------------ > > Key: JBTM-2484 > URL: https://issues.jboss.org/browse/JBTM-2484 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 6.later > > Attachments: JTSRemote_TimeoutTest.tar > > > The only error is is in the client when it tries to rollback the transaction (see attached logs): > bq. FATAL: ARJUNA022006: The ORB has not been initialized yet -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 6 09:51:05 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 6 Aug 2015 09:51:05 -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 ] Michael Musgrove updated JBTM-2454: ----------------------------------- Attachment: compensations.tar compensations surefire directory > 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 > > Attachments: compensations.tar > > > 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 Thu Aug 6 11:25:04 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 6 Aug 2015 11:25:04 -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=13096263#comment-13096263 ] Michael Musgrove edited comment on JBTM-2454 at 8/6/15 11:24 AM: ----------------------------------------------------------------- Gytis pointed out that the compensations failure is a known weld issue so I will push a commit to upgrade that (https://github.com/jbosstm/narayana/pull/895) was (Author: mmusgrov): Gytis pointed out that the compensations failure is a known weld issue so I will push a commit to upgrade that > 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 > > Attachments: compensations.tar > > > 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 Fri Aug 7 05:39:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Aug 2015 05:39:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2477) Measure timed out transactions in TxStats In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-2477. ---------------------------------- Resolution: Rejected We already have a statistic for this (and it is incremented by the reaper thread): bq. TxStatsMBean#getNumberOfTimedOutTransactions > Measure timed out transactions in TxStats > ----------------------------------------- > > Key: JBTM-2477 > URL: https://issues.jboss.org/browse/JBTM-2477 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Will be useful for monitoring according to GSS -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 05:51:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Aug 2015 05:51:03 -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=13096488#comment-13096488 ] Michael Musgrove commented on JBTM-2460: ---------------------------------------- The fix relies on the transaction manager being bound into JNDI and scotts issue is a race between his subsystem starting and jndi binding. For wildfly usage other subsystems would use service injection (WFLY-5069 will track this) > 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 Fri Aug 7 05:57:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Aug 2015 05:57: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: ----------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/888 > 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 Fri Aug 7 05:57:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Aug 2015 05:57: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: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 Fri Aug 7 06:00:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 06:00:08 -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=13096492#comment-13096492 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- There is someone with a similar issue over here: http://stackoverflow.com/questions/31433475/jenkins-build-with-maven-release-plugin-fails > 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 > > Attachments: compensations.tar > > > 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 Fri Aug 7 06:09:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 06:09:04 -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=13096496#comment-13096496 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- Annoyingly I can't replicate on lancel outside of Jenkins. Perhaps it is some consequence of previous steps in the build: cd tmp/narayana export PATH=/usr/local/ibm-java-x86_64-80/bin:$PATH export JAVA_HOME=/usr/local/ibm-java-x86_64-80/ export JBOSS_HOME=`pwd`/jboss-as/build/target/wildfly-10.0.0.Beta1-SNAPSHOT export TXF_TESTS=0 XTS_TESTS=0 txbridge=0 JTA_CDI_TESTS=0 XTS_AS_TESTS=0 RTS_AS_TESTS=0 RTS_TESTS=0 NARAYANA_TESTS=0 BLACKTIE=0 QA_TESTS=0 export NARAYANA_BUILD=1 AS_BUILD=1 SUN_ORB=0 JAC_ORB=0 IBM_ORB=1 PROFILE=NONE ./scripts/hudson/narayana.sh -Denforcer.skip=true ./build.sh -f XTS/localjunit/pom.xml -Parq [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/tmp/narayana/XTS/localjunit/disabled-context-propagation/target/test-classes [WARNING] bootstrap class path not set in conjunction with -source 1.7 [INFO] Gonna set up a job to test just that to help isolate > 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 > > Attachments: compensations.tar > > > 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 Fri Aug 7 06:12:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 06:12: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=13096498#comment-13096498 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/JBTM-2454-narayana-ibm-jdk/ > 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 > > Attachments: compensations.tar > > > 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 Fri Aug 7 06:12:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Aug 2015 06:12:03 -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:comment-tabpanel&focusedCommentId=13096499#comment-13096499 ] Michael Musgrove commented on JBTM-2328: ---------------------------------------- This functionality will be replaced in favour of JMX MBeans > 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 Fri Aug 7 06:17:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Aug 2015 06:17: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=13096502#comment-13096502 ] Michael Musgrove commented on JBTM-2467: ---------------------------------------- Note - it also needs fixing in the quickstart > 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 Fri Aug 7 06:26:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 06:26:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2485) Close and release nexus deployed artifacts from build script In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2485: ----------------------------------- Summary: Close and release nexus deployed artifacts from build script Key: JBTM-2485 URL: https://issues.jboss.org/browse/JBTM-2485 Project: JBoss Transaction Manager Issue Type: Task Components: Build System, Release Process Reporter: Tom Jenkinson Assignee: Tom Jenkinson Currently we need to visit the nexus site during NRP, it would be nice to be able to execute these steps from the command line as part of the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 07:48:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 07:48:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-855: ------------------------------- Forum Reference: https://developer.jboss.org/message/937423 > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 6.later > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 07:48:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 07:48:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096524#comment-13096524 ] Tom Jenkinson commented on JBTM-855: ------------------------------------ We should consider adding JTS into the example > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 6.later > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 07:56:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 07:56:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-855: ------------------------------- Fix Version/s: 5.next (was: 6.later) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 07:58:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 07:58:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096526#comment-13096526 ] Tom Jenkinson commented on JBTM-1820: ------------------------------------- Amos dis some preliminary work modifying the camel in action book but we should still concentrate on our own example: https://github.com/camelinaction/camelinaction/compare/master...zhfeng:JBTM-1820_Update_to_use_Narayana > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 6.later > > > From Ning Jiang (njiang at redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 09:34:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 09:34:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2486) JDBC object store closes connections after resultset/statements which is incorrect order In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2486: ----------------------------------- Summary: JDBC object store closes connections after resultset/statements which is incorrect order Key: JBTM-2486 URL: https://issues.jboss.org/browse/JBTM-2486 Project: JBoss Transaction Manager Issue Type: Task Reporter: Tom Jenkinson Assignee: Tom Jenkinson As reported by IronJacamar team we should treat the JDBC resources as a stack. Specific case reported: https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L347 https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L352 https://gist.github.com/maeste/835073a1e8ea6e38b9bd -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 10:11:01 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 10:11:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2486) JDBC object store closes connections after resultset/statements which is incorrect order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2486: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/896 > JDBC object store closes connections after resultset/statements which is incorrect order > ---------------------------------------------------------------------------------------- > > Key: JBTM-2486 > URL: https://issues.jboss.org/browse/JBTM-2486 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > As reported by IronJacamar team we should treat the JDBC resources as a stack. > Specific case reported: > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L347 > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L352 > https://gist.github.com/maeste/835073a1e8ea6e38b9bd -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 11:29:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:29:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2486) JDBC object store closes connections after resultset/statements which is incorrect order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2486: -------------------------------- Fix Version/s: 5.next > JDBC object store closes connections after resultset/statements which is incorrect order > ---------------------------------------------------------------------------------------- > > Key: JBTM-2486 > URL: https://issues.jboss.org/browse/JBTM-2486 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > As reported by IronJacamar team we should treat the JDBC resources as a stack. > Specific case reported: > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L347 > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L352 > https://gist.github.com/maeste/835073a1e8ea6e38b9bd -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 11:30:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:30:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2477) Measure timed out transactions in TxStats In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2477: --------------------------------- > Measure timed out transactions in TxStats > ----------------------------------------- > > Key: JBTM-2477 > URL: https://issues.jboss.org/browse/JBTM-2477 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Will be useful for monitoring according to GSS -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 11:31:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:31:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2477) Measure timed out transactions in TxStats In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2477: -------------------------------- Fix Version/s: (was: 5.next) > Measure timed out transactions in TxStats > ----------------------------------------- > > Key: JBTM-2477 > URL: https://issues.jboss.org/browse/JBTM-2477 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > Will be useful for monitoring according to GSS -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 11:31:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:31:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2477) Measure timed out transactions in TxStats In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2477. ------------------------------- Resolution: Rejected > Measure timed out transactions in TxStats > ----------------------------------------- > > Key: JBTM-2477 > URL: https://issues.jboss.org/browse/JBTM-2477 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > Will be useful for monitoring according to GSS -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 11:38:43 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:38:43 -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 ] Tom Jenkinson updated JBTM-2460: -------------------------------- Fix Version/s: 5.2.1 (was: 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.2.1 > > > 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 Fri Aug 7 11:38:52 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:38:52 -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 ] Tom Jenkinson closed JBTM-2460. ------------------------------- > 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.2.1 > > > 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 Fri Aug 7 11:38:53 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:38:53 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2482) Update pre-release.sh to update the version of Narayana in the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2482: -------------------------------- Fix Version/s: 5.2.1 (was: 5.next) > Update pre-release.sh to update the version of Narayana in the performance repo > ------------------------------------------------------------------------------- > > Key: JBTM-2482 > URL: https://issues.jboss.org/browse/JBTM-2482 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.1 > > > Currently the version number in the performance repo is a manual step -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 11:38:54 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:38:54 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2482) Update pre-release.sh to update the version of Narayana in the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2482. ------------------------------- > Update pre-release.sh to update the version of Narayana in the performance repo > ------------------------------------------------------------------------------- > > Key: JBTM-2482 > URL: https://issues.jboss.org/browse/JBTM-2482 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.1 > > > Currently the version number in the performance repo is a manual step -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 11:38:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:38:55 -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 resolved JBTM-2328. --------------------------------- Resolution: Done > 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 Fri Aug 7 11:44:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 11:44: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=13096654#comment-13096654 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- Fortunately (or not) revised CI config now fails in the reproducing job: http://albany.eng.hst.ams2.redhat.com/job/JBTM-2454-narayana-ibm-jdk/2/ {code} java -version export TXF_TESTS=0 XTS_TESTS=0 txbridge=0 JTA_CDI_TESTS=0 XTS_AS_TESTS=0 RTS_AS_TESTS=0 RTS_TESTS=0 NARAYANA_TESTS=0 BLACKTIE=0 QA_TESTS=0 export NARAYANA_BUILD=1 AS_BUILD=1 SUN_ORB=0 JAC_ORB=0 IBM_ORB=1 PROFILE=NONE ./scripts/hudson/narayana.sh -Denforcer.skip=true export JBOSS_HOME=`pwd`/jboss-as/build/target/wildfly-10.0.0.Beta1-SNAPSHOT cp jboss-as/build/target/wildfly-10.0.0.Beta1-SNAPSHOT/docs/examples/configs/standalone-xts.xml jboss-as/build/target/wildfly-10.0.0.Beta1-SNAPSHOT/standalone/configuration/ ./build.sh -f XTS/localjunit/pom.xml -Parq -Dorg.jboss.remoting-jmx.timeout=300 clean install {code} I am going to try to execute each command by hand in the job config instead of lauching localjunit/* and see if that will pass. > 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 > > Attachments: compensations.tar > > > 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 Fri Aug 7 12:15:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 12:15:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2487) Initialize method of JDBC object store driver uses a connection outside of a try with resources In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2487: ----------------------------------- Summary: Initialize method of JDBC object store driver uses a connection outside of a try with resources Key: JBTM-2487 URL: https://issues.jboss.org/browse/JBTM-2487 Project: JBoss Transaction Manager Issue Type: Bug Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Offending code: https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L649 Technique to use: https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 12:17:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 12:17:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2486) JDBC object store closes connections after resultset/statements which is incorrect order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2486: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JDBC object store closes connections after resultset/statements which is incorrect order > ---------------------------------------------------------------------------------------- > > Key: JBTM-2486 > URL: https://issues.jboss.org/browse/JBTM-2486 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > As reported by IronJacamar team we should treat the JDBC resources as a stack. > Specific case reported: > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L347 > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L352 > https://gist.github.com/maeste/835073a1e8ea6e38b9bd -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 12:24:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 7 Aug 2015 12:24:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2487) Initialize method of JDBC object store driver uses a connection outside of a try with resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2487: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/898 > Initialize method of JDBC object store driver uses a connection outside of a try with resources > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2487 > URL: https://issues.jboss.org/browse/JBTM-2487 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Offending code: https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L649 > Technique to use: > https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 12:33:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Aug 2015 12:33:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2488) Fix findbugs issues in rts modules In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2488: -------------------------------------- Summary: Fix findbugs issues in rts modules Key: JBTM-2488 URL: https://issues.jboss.org/browse/JBTM-2488 Project: JBoss Transaction Manager Issue Type: Bug Components: REST Affects Versions: 5.2.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later The relevant issues can be seen by running: bq. mvn site -DskipTests -Pfindbugs -f rts/pom.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 7 12:40:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 7 Aug 2015 12:40:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2489) Create a separate CI job for running findbugs In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2489: -------------------------------------- Summary: Create a separate CI job for running findbugs Key: JBTM-2489 URL: https://issues.jboss.org/browse/JBTM-2489 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Affects Versions: 5.2.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional Fix For: 5.later Set up a job for running the findbugs profile and remove it from the default profile. Also add the site goal so that we can archive the html report. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 10 04:58:02 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Mon, 10 Aug 2015 04:58:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: Hayk Hovsepyan created JBTM-2490: ------------------------------------ Summary: Possibility to run "qa" module with openjdk-orb Key: JBTM-2490 URL: https://issues.jboss.org/browse/JBTM-2490 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Hayk Hovsepyan Assignee: Tom Jenkinson Priority: Blocker In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. "QA_TESTS=1" and "JAC_ORB=1" We need to modify these jobs to run with "openjdk-orb" enabled. So what we request: Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 10 05:22:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 10 Aug 2015 05:22:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096819#comment-13096819 ] Tom Jenkinson commented on JBTM-2490: ------------------------------------- Hi Hayk, Would you have chance to work on this at all? You have marked it as a blocker so trying to work out the priority as you didn't mark a fix version. Thanks, Tom > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Hayk Hovsepyan > Assignee: Tom Jenkinson > Priority: Blocker > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 10 05:36:03 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Mon, 10 Aug 2015 05:36:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hayk Hovsepyan reassigned JBTM-2490: ------------------------------------ Assignee: Michael Musgrove (was: Tom Jenkinson) > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 10 05:38:03 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Mon, 10 Aug 2015 05:38:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hayk Hovsepyan updated JBTM-2490: --------------------------------- Component/s: Testing > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 10 05:38:03 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Mon, 10 Aug 2015 05:38:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hayk Hovsepyan updated JBTM-2490: --------------------------------- Fix Version/s: 5.next > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 10 05:40:03 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Mon, 10 Aug 2015 05:40:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096822#comment-13096822 ] Hayk Hovsepyan commented on JBTM-2490: -------------------------------------- Hi Tom, I have created this task after agreement with Mike via IRC. He agreed to handle this ASAP. Thanks, Hayk > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 10 09:14:01 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 10 Aug 2015 09:14:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2491) JTS and JacORB NS Docker images quickstart with Kubernetes In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2491: ------------------------------------- Summary: JTS and JacORB NS Docker images quickstart with Kubernetes Key: JBTM-2491 URL: https://issues.jboss.org/browse/JBTM-2491 Project: JBoss Transaction Manager Issue Type: Task Components: Cloud, Demonstrator Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next Create example Kubernetes configuration for JTS and JacORB NS Docker images. As well as a test case for them. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 10 11:11:06 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 10 Aug 2015 11:11:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2489) Create a separate CI job for running findbugs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2489. ------------------------------------ Resolution: Done I have added html findbugs generation to the narayana-codeCoverage job and disabled it in the MAIN profile > Create a separate CI job for running findbugs > --------------------------------------------- > > Key: JBTM-2489 > URL: https://issues.jboss.org/browse/JBTM-2489 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.later > > > Set up a job for running the findbugs profile and remove it from the default profile. Also add the site goal so that we can archive the html report. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 08:50:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1820: -------------------------------- Priority: Optional (was: Major) > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Optional > Fix For: 5.later > > > From Ning Jiang (njiang at redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 08:50:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:50:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1820: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Optional > Fix For: 5.later > > > From Ning Jiang (njiang at redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 08:50:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:50:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1820: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Optional > Fix For: 5.later > > > From Ning Jiang (njiang at redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 08:51:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:51:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1856) Provide a transactional driver quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1856: -------------------------------- Fix Version/s: 5.next (was: 6.later) > Provide a transactional driver quickstart > ----------------------------------------- > > Key: JBTM-1856 > URL: https://issues.jboss.org/browse/JBTM-1856 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Provide a simple example of a standalone application using Narayana with Transactional Driver. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 08:51:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:51:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1856) Provide a transactional driver quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1856: -------------------------------- Issue Type: Task (was: Feature Request) > Provide a transactional driver quickstart > ----------------------------------------- > > Key: JBTM-1856 > URL: https://issues.jboss.org/browse/JBTM-1856 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Provide a simple example of a standalone application using Narayana with Transactional Driver. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 08:55:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:55:03 -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:comment-tabpanel&focusedCommentId=13097231#comment-13097231 ] Tom Jenkinson commented on JBTM-1860: ------------------------------------- http://narayana.io/docs/project/index.html#d0e2551 (failure recovery guide online) > 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 > Fix For: 5.later > > > 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 Aug 11 08:55:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:55:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1860) Please document 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: -------------------------------- Summary: Please document TransactionStatusManager scanner. (was: Please document AtomicAction and TransactionStatusManager scanner.) > Please document 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 > Fix For: 5.later > > > 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 Aug 11 08:55:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:55:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1860) Please document 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: -------------------------------- Fix Version/s: 5.later > Please document 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 > Fix For: 5.later > > > 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 Aug 11 08:57:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:57:06 -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 ] Tom Jenkinson updated JBTM-1952: -------------------------------- Fix Version/s: (was: 6.later) > 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 > > 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 Tue Aug 11 08:57:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 08:57:06 -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: 6.later) > 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 > > 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 Tue Aug 11 09:00:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 09:00:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2326: -------------------------------- Fix Version/s: 5.later > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.later > > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 09:01:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 09:01:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2329: -------------------------------- Fix Version/s: 5.later > Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2329 > URL: https://issues.jboss.org/browse/JBTM-2329 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.later > > > If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. > After discussion on the forum, it seems likely the API would be something like: > Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. > Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) > {code} > public interface HeuristicManagement > { > public void resolve() throws CouldNotResolveException; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 09:02:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 09:02:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2329: -------------------------------- Reporter: Michael Musgrove (was: Tom Jenkinson) > Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2329 > URL: https://issues.jboss.org/browse/JBTM-2329 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.later > > > If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. > After discussion on the forum, it seems likely the API would be something like: > Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. > Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) > {code} > public interface HeuristicManagement > { > public void resolve() throws CouldNotResolveException; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 09:18:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 09:18:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1856) Provide a transactional driver quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1856: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Provide a transactional driver quickstart > ----------------------------------------- > > Key: JBTM-1856 > URL: https://issues.jboss.org/browse/JBTM-1856 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > > Provide a simple example of a standalone application using Narayana with Transactional Driver. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 09:20:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 11 Aug 2015 09:20:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2483) Investigate ways to test Docker quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2483: ---------------------------------- Fix Version/s: 5.later (was: 5.next) > Investigate ways to test Docker quickstarts > ------------------------------------------- > > Key: JBTM-2483 > URL: https://issues.jboss.org/browse/JBTM-2483 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > > Currently there is only one quickstart for docker (at the moment in the PR queue), but its tests are disabled by default. However, it would be good to run them in our CI. > We'll have the same problem in the future with Kubernetes quickstarts. > Maybe Arquillian Cube is something what could help? -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 09:26:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Aug 2015 09:26:02 -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 ] Michael Musgrove updated JBTM-2419: ----------------------------------- Fix Version/s: (was: 5.next) > 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 > > 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 Tue Aug 11 09:26:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Aug 2015 09:26:02 -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 ] Michael Musgrove updated JBTM-1853: ----------------------------------- Fix Version/s: (was: 5.next) > 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.later > > 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 Tue Aug 11 09:26:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Aug 2015 09:26:02 -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 ] Michael Musgrove updated JBTM-1853: ----------------------------------- Fix Version/s: 5.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.later > > 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 Tue Aug 11 09:27:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Aug 2015 09:27: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 ] Michael Musgrove updated JBTM-1922: ----------------------------------- Fix Version/s: 5.later (was: 5.next) > 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.later > > 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 Tue Aug 11 09:27:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Aug 2015 09:27: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 ] Michael Musgrove reassigned JBTM-2454: -------------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > 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: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: compensations.tar > > > 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 Aug 11 09:28:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 09:28:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2487) Initialize method of JDBC object store driver uses a connection outside of a try with resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2487: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Initialize method of JDBC object store driver uses a connection outside of a try with resources > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2487 > URL: https://issues.jboss.org/browse/JBTM-2487 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Offending code: https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L649 > Technique to use: > https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 10:48:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 10:48: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: -------------------------------- Issue Type: Task (was: Enhancement) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 10:49:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 10:49:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2490: -------------------------------- Issue Type: Task (was: Feature Request) > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 10:54:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 10:54: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 updated JBTM-2245: -------------------------------- Fix Version/s: 5.later (was: 5.next) > 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.later > > > 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 Aug 11 11:29:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:29:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-809) Replace transactional driver with ironjacamar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-809: ------------------------------- Fix Version/s: (was: 6.later) > Replace transactional driver with ironjacamar > --------------------------------------------- > > Key: JBTM-809 > URL: https://issues.jboss.org/browse/JBTM-809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server. > There are several bugs open against transactional driver that will be resolved by completing this work. > The general approach would be along the lines of: > Startup > ====== > Embedded embedded = EmbeddedFactory.create(); > embedded.startup(); > embedded.deploy(new File("my-rar.rar").toURI().toURL()); > embedded.deploy(new File("my-ds.xml").toURI().toURL()); > In use > ===== > InitialContext initialContext = new InitialContext(); > UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction"); > DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS"); > Shutdown > ======= > embedded.undeploy(new File("my-ds.xml").toURI().toURL()); > embedded.undeploy(new File("my-rar.rar").toURI().toURL()); > embedded.shutdown(); // does not work - some threads don't stop > Problems? > ========= > JCA transitive dependencies? > Accessing ds files from war? > Accessing rar from war? > May have to provide these both upfront. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:30:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:30:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-809) Replace transactional driver with ironjacamar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-809: ------------------------------- Fix Version/s: 6.later > Replace transactional driver with ironjacamar > --------------------------------------------- > > Key: JBTM-809 > URL: https://issues.jboss.org/browse/JBTM-809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 6.later > > > Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server. > There are several bugs open against transactional driver that will be resolved by completing this work. > The general approach would be along the lines of: > Startup > ====== > Embedded embedded = EmbeddedFactory.create(); > embedded.startup(); > embedded.deploy(new File("my-rar.rar").toURI().toURL()); > embedded.deploy(new File("my-ds.xml").toURI().toURL()); > In use > ===== > InitialContext initialContext = new InitialContext(); > UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction"); > DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS"); > Shutdown > ======= > embedded.undeploy(new File("my-ds.xml").toURI().toURL()); > embedded.undeploy(new File("my-rar.rar").toURI().toURL()); > embedded.shutdown(); // does not work - some threads don't stop > Problems? > ========= > JCA transitive dependencies? > Accessing ds files from war? > Accessing rar from war? > May have to provide these both upfront. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:30:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:30:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-809) Provide instructions for using ironjacamar as well as transactional drive In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-809: ------------------------------- Summary: Provide instructions for using ironjacamar as well as transactional drive (was: Replace transactional driver with ironjacamar) > Provide instructions for using ironjacamar as well as transactional drive > ------------------------------------------------------------------------- > > Key: JBTM-809 > URL: https://issues.jboss.org/browse/JBTM-809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 6.later > > > Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server. > There are several bugs open against transactional driver that will be resolved by completing this work. > The general approach would be along the lines of: > Startup > ====== > Embedded embedded = EmbeddedFactory.create(); > embedded.startup(); > embedded.deploy(new File("my-rar.rar").toURI().toURL()); > embedded.deploy(new File("my-ds.xml").toURI().toURL()); > In use > ===== > InitialContext initialContext = new InitialContext(); > UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction"); > DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS"); > Shutdown > ======= > embedded.undeploy(new File("my-ds.xml").toURI().toURL()); > embedded.undeploy(new File("my-rar.rar").toURI().toURL()); > embedded.shutdown(); // does not work - some threads don't stop > Problems? > ========= > JCA transitive dependencies? > Accessing ds files from war? > Accessing rar from war? > May have to provide these both upfront. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:30:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:30:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-809) Provide instructions for using ironjacamar as well as transactional driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-809: ------------------------------- Summary: Provide instructions for using ironjacamar as well as transactional driver (was: Provide instructions for using ironjacamar as well as transactional drive) > Provide instructions for using ironjacamar as well as transactional driver > -------------------------------------------------------------------------- > > Key: JBTM-809 > URL: https://issues.jboss.org/browse/JBTM-809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 6.later > > > Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server. > There are several bugs open against transactional driver that will be resolved by completing this work. > The general approach would be along the lines of: > Startup > ====== > Embedded embedded = EmbeddedFactory.create(); > embedded.startup(); > embedded.deploy(new File("my-rar.rar").toURI().toURL()); > embedded.deploy(new File("my-ds.xml").toURI().toURL()); > In use > ===== > InitialContext initialContext = new InitialContext(); > UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction"); > DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS"); > Shutdown > ======= > embedded.undeploy(new File("my-ds.xml").toURI().toURL()); > embedded.undeploy(new File("my-rar.rar").toURI().toURL()); > embedded.shutdown(); // does not work - some threads don't stop > Problems? > ========= > JCA transitive dependencies? > Accessing ds files from war? > Accessing rar from war? > May have to provide these both upfront. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:32:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:32:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2103) ORB-less JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2103: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > ORB-less JTS > ------------ > > Key: JBTM-2103 > URL: https://issues.jboss.org/browse/JBTM-2103 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.0 > Reporter: Mark Little > Assignee: Michael Musgrove > Fix For: 5.later > > > At some point in the future there's a good chance that the ORB requirement will be removed from EE entirely. If that happens we need to be able to react and ensure that the JTS continues to work because it?s the most complete distributed transaction implementation that we possess. Now there are two ways to do that: > (i) we ship our own ORB, either JacORB or something else, say. > (ii) we remove the dependency on CORBA entirely. > Whilst (i) is a good short term option, I think we need to look at (ii). An old in-house TM that JBoss had which Narayana replaced had a JTS implementation which supported CORBA and JBoss Remoting (I think it was Remoting). Ultimately what we need is a high performance distributed transactions implementation and JTS is it today but it has a dependency on CORBA that we need to try to remove and yet keep most of the non-ORB generated code/dependencies. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:32:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:32:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2103) ORB-less JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2103: -------------------------------- Fix Version/s: 5.later > ORB-less JTS > ------------ > > Key: JBTM-2103 > URL: https://issues.jboss.org/browse/JBTM-2103 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.0 > Reporter: Mark Little > Assignee: Michael Musgrove > Fix For: 5.later > > > At some point in the future there's a good chance that the ORB requirement will be removed from EE entirely. If that happens we need to be able to react and ensure that the JTS continues to work because it?s the most complete distributed transaction implementation that we possess. Now there are two ways to do that: > (i) we ship our own ORB, either JacORB or something else, say. > (ii) we remove the dependency on CORBA entirely. > Whilst (i) is a good short term option, I think we need to look at (ii). An old in-house TM that JBoss had which Narayana replaced had a JTS implementation which supported CORBA and JBoss Remoting (I think it was Remoting). Ultimately what we need is a high performance distributed transactions implementation and JTS is it today but it has a dependency on CORBA that we need to try to remove and yet keep most of the non-ORB generated code/dependencies. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:33:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:33:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2116) SPI: Unique identifier for a transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2116: -------------------------------- Fix Version/s: 5.later > SPI: Unique identifier for a transaction > ---------------------------------------- > > Key: JBTM-2116 > URL: https://issues.jboss.org/browse/JBTM-2116 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Fix For: 5.later > > > The Narayana SPI should provide a method that returns a unique identifier for a transaction that is stable for its entire lifecycle. > {noformat} > public Object getIdentifier(Transaction tx) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:33:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:33:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2124: -------------------------------- Fix Version/s: 5.later > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ond?ej Chaloupka > Assignee: Gytis Trikleris > Fix For: 5.later > > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:35:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:35: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: -------------------------------- Issue Type: Enhancement (was: Task) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Compensations > Reporter: 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 Tue Aug 11 11:36:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:36: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: -------------------------------- Issue Type: Task (was: Feature Request) > 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: Task > 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 Tue Aug 11 11:36:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:36:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2329: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2329 > URL: https://issues.jboss.org/browse/JBTM-2329 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.later > > > If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. > After discussion on the forum, it seems likely the API would be something like: > Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. > Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) > {code} > public interface HeuristicManagement > { > public void resolve() throws CouldNotResolveException; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:37:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:37:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2481: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:38:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:38:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2481: -------------------------------- Priority: Minor (was: Major) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:38:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:38:05 -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: -------------------------------- Issue Type: Bug (was: Task) > 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: Bug > Components: REST > Affects Versions: 5.0.0.M4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > 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 Tue Aug 11 11:41:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:41:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1469) Move TXBridge quickstart into JDF In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1469. ------------------------------- Fix Version/s: (was: 6.later) Resolution: Won't Fix May reconsider it for later > Move TXBridge quickstart into JDF > --------------------------------- > > Key: JBTM-1469 > URL: https://issues.jboss.org/browse/JBTM-1469 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, TxBridge, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > TXBridge is now supported, so we can move one or more of the quickstarts across to JDF. We should first run this by Pete and get a JDF Jira created, then link this one through. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 11:41:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 11:41:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1507) Review the TXBridge tests usage of Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1507: -------------------------------- Fix Version/s: (was: 6.later) > Review the TXBridge tests usage of Arquillian > --------------------------------------------- > > Key: JBTM-1507 > URL: https://issues.jboss.org/browse/JBTM-1507 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Testing, TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > The TXBridge tests don;t seem to be using Arquillian correctly. There is a servlet that is invoked to do things inside the container. As the tests (should) now run in the container, this should not be needed. > The tests also seem to have added complexity due to the recovery tests. As the recovery tests need to be able to kill the container, it mandates manual container lifecycle management for *all* tests. We may want to pull out the recovery tests into a separate module. > We also may want to pull out the DisabledContextPropagationTest into a separate module as they use a modified AS configuration. > We should also take a general look at how the tests are structured and using Arq. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:04:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1802) Consider moving Arquillian profiles to root pom.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1802: -------------------------------- Fix Version/s: (was: 6.later) > Consider moving Arquillian profiles to root pom.xml > --------------------------------------------------- > > Key: JBTM-1802 > URL: https://issues.jboss.org/browse/JBTM-1802 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Build System, Testing > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Minor > > We have three Arquillian profiles (for managed, remote and ipv6-managed) present in the pom of nearly every test that uses Arquillian. I suspect they can all be identical and thus placed int he root pom.xml. This should simplify maintenance and will ensure any fixes to this config are made throughout. > The problem is that we may have legitimate reasons for this config to differ for some tests. Maybe we could use overrides in these cases. > Assigning to Tom for his input. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:04:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1719) Improve test coverage for REST-AT multiplexor. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1719: -------------------------------- Fix Version/s: 5.later (was: 6.later) > Improve test coverage for REST-AT multiplexor. > ---------------------------------------------- > > Key: JBTM-1719 > URL: https://issues.jboss.org/browse/JBTM-1719 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Implement more unit and integration tests to cover more aspects of multiplexor functionality. Especially recovery. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:05:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:05:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1715) NPE when using CompensationManager within an in-flowed WS-BA transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1715: -------------------------------- Fix Version/s: (was: 6.later) > NPE when using CompensationManager within an in-flowed WS-BA transaction > ------------------------------------------------------------------------ > > Key: JBTM-1715 > URL: https://issues.jboss.org/browse/JBTM-1715 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The following error occurs if an injected CompensationManager is invoked within the scope of a compensation-based transaction that was in-flowed via a WS-BA transaction. > {quote} > 16:17:09,879 ERROR [org.jboss.as.ejb3.invocation] (default task-18) JBAS014134: EJB Invocation failed on component TestServiceService for method public void org.jboss.narayana.compensations.functiona[617/9100] > ted.TestServiceService.saveDataCancelOnFailure(java.lang.Boolean): javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:251) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:215) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPS > HOT] > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:05:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:05:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1715) NPE when using CompensationManager within an in-flowed WS-BA transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1715: -------------------------------- Fix Version/s: 5.later > NPE when using CompensationManager within an in-flowed WS-BA transaction > ------------------------------------------------------------------------ > > Key: JBTM-1715 > URL: https://issues.jboss.org/browse/JBTM-1715 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The following error occurs if an injected CompensationManager is invoked within the scope of a compensation-based transaction that was in-flowed via a WS-BA transaction. > {quote} > 16:17:09,879 ERROR [org.jboss.as.ejb3.invocation] (default task-18) JBAS014134: EJB Invocation failed on component TestServiceService for method public void org.jboss.narayana.compensations.functiona[617/9100] > ted.TestServiceService.saveDataCancelOnFailure(java.lang.Boolean): javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:251) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:215) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPS > HOT] > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:05:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:05:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2072) Improve CI timeout handling on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2072: -------------------------------- Fix Version/s: (was: 6.later) > Improve CI timeout handling on Windows > -------------------------------------- > > Key: JBTM-2072 > URL: https://issues.jboss.org/browse/JBTM-2072 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:05:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:05:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2383) Update standalone JCA quickstarts to use IronJacamar test runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2383: -------------------------------- Fix Version/s: (was: 6.later) > Update standalone JCA quickstarts to use IronJacamar test runner > ---------------------------------------------------------------- > > Key: JBTM-2383 > URL: https://issues.jboss.org/browse/JBTM-2383 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > > See this post for the improvements in embedded IronJacamar container: https://groups.google.com/forum/#!topic/ironjacamar-developers/Pat7ixJuX6s -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:05:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:05:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-987) Document Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-987: ------------------------------- Fix Version/s: 5.later (was: 6.later) > Document Compensations API > -------------------------- > > Key: JBTM-987 > URL: https://issues.jboss.org/browse/JBTM-987 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Optional > Labels: TXFramework > Fix For: 5.later > > > Should cover all existing features and provide a skeleton for the final document. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:05:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:05:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2484) JTSRemote_TimeoutTest from jtsremote tests failed on local cluster In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2484: -------------------------------- Fix Version/s: 5.later (was: 6.later) > JTSRemote_TimeoutTest from jtsremote tests failed on local cluster > ------------------------------------------------------------------ > > Key: JBTM-2484 > URL: https://issues.jboss.org/browse/JBTM-2484 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > Attachments: JTSRemote_TimeoutTest.tar > > > The only error is is in the client when it tries to rollback the transaction (see attached logs): > bq. FATAL: ARJUNA022006: The ORB has not been initialized yet -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:05:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:05:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1801) Move all test properties into root pom.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1801: -------------------------------- Fix Version/s: 5.later (was: 6.later) > Move all test properties into root pom.xml > ------------------------------------------ > > Key: JBTM-1801 > URL: https://issues.jboss.org/browse/JBTM-1801 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Trivial > Fix For: 5.later > > > We have these test properties duplicated in many places: > https://github.com/jbosstm/narayana/blob/master/XTS/localjunit/pom.xml#L22 > We should move them up to the root pom.xml to simplify maintenance. As part of this task you need to hunt out all these usages and similar. Then come up with a common set of properties that works in all cases and move to the root pom.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:08:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:08:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2402) Create a quickstart and some docs that show how to use our OSGi bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2402: -------------------------------- Fix Version/s: 5.later > Create a quickstart and some docs that show how to use our OSGi bundle > ---------------------------------------------------------------------- > > Key: JBTM-2402 > URL: https://issues.jboss.org/browse/JBTM-2402 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration, Demonstrator, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.later > > > We should create a quickstart to demonstrate how to install and use our bundle. It should also be described in our project (community) manual. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:08:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:08: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:all-tabpanel ] Tom Jenkinson updated JBTM-928: ------------------------------- Fix Version/s: 5.later > 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.later > > > 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 Aug 11 12:08:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:08:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2485) Close and release nexus deployed artifacts from build script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2485: -------------------------------- Priority: Optional (was: Major) > Close and release nexus deployed artifacts from build script > ------------------------------------------------------------ > > Key: JBTM-2485 > URL: https://issues.jboss.org/browse/JBTM-2485 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.next > > > Currently we need to visit the nexus site during NRP, it would be nice to be able to execute these steps from the command line as part of the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:08:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:08:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2485) Close and release nexus deployed artifacts from build script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2485: -------------------------------- Fix Version/s: 5.next > Close and release nexus deployed artifacts from build script > ------------------------------------------------------------ > > Key: JBTM-2485 > URL: https://issues.jboss.org/browse/JBTM-2485 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently we need to visit the nexus site during NRP, it would be nice to be able to execute these steps from the command line as part of the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:09:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:09:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2312) Wrong logging format of ARJUNA016005 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2312: -------------------------------- Fix Version/s: 5.next > Wrong logging format of ARJUNA016005 > ------------------------------------ > > Key: JBTM-2312 > URL: https://issues.jboss.org/browse/JBTM-2312 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 4.17.24 > Reporter: Ond?ej Chaloupka > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Logging format of warning warn_recovery_failedtorecover is strange or maybe better to say wrong. It looks: > {code} > WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016005: JTS XARecoveryModule.xaRecovery - failed to recover XAResource. status is $2 > {code} > This message came from XAResourceRecord.xaRecoverySecondPass and it's message warn_recovery_failedtorecover. The code with dolar sign seems to me a bit confusing. > I think it would be better first not have the dolar sign there and second rather to print string representation of the error code. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:09:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:09:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by coordinator in CloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2194: -------------------------------- Fix Version/s: 5.later > Activity cancelled by coordinator in CloseTest > ---------------------------------------------- > > Key: JBTM-2194 > URL: https://issues.jboss.org/browse/JBTM-2194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.CloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! > testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 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.CloseTest.testClose(CloseTest.java:64) > {code} > {code} > 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. > 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war > 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war > 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test > 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter > 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called > 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called > 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called > 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 > 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) Default helper activated > 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter > 18:45:39,135 INFO [stdout] (default task-16) create counter execute > 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 > 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 > 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl > 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 > 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called > 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute > 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting > 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 > 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called > 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking > 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken > 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake > 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity > 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl > 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 > 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute > 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter > 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called > 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called > 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated > 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test > 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms > 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:12:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:12:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1359) HA Recovery Manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1359: -------------------------------- Fix Version/s: (was: 6.later) > HA Recovery Manager > ------------------- > > Key: JBTM-1359 > URL: https://issues.jboss.org/browse/JBTM-1359 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, JTS, Recovery, XTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Optional > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > JTA should work, but must consider JTS and XTS too (encoded IP addresses in log records) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:12:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:12:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1494) Produce performance figures to show performance improvements of Compensations over ACID In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1494: -------------------------------- Fix Version/s: (was: 6.later) > Produce performance figures to show performance improvements of Compensations over ACID > --------------------------------------------------------------------------------------- > > Key: JBTM-1494 > URL: https://issues.jboss.org/browse/JBTM-1494 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > > As part of evangelising compensations, it would be useful to show performance comparisons for different classes of applications. > Ideally, these results should show that that, for certain classes of applications, the performance of a compensation-based transaction is a lot better than for an ACID transaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:12:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:12:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-809) Provide instructions for using ironjacamar as well as transactional driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-809: ------------------------------- Fix Version/s: (was: 6.later) > Provide instructions for using ironjacamar as well as transactional driver > -------------------------------------------------------------------------- > > Key: JBTM-809 > URL: https://issues.jboss.org/browse/JBTM-809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server. > There are several bugs open against transactional driver that will be resolved by completing this work. > The general approach would be along the lines of: > Startup > ====== > Embedded embedded = EmbeddedFactory.create(); > embedded.startup(); > embedded.deploy(new File("my-rar.rar").toURI().toURL()); > embedded.deploy(new File("my-ds.xml").toURI().toURL()); > In use > ===== > InitialContext initialContext = new InitialContext(); > UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction"); > DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS"); > Shutdown > ======= > embedded.undeploy(new File("my-ds.xml").toURI().toURL()); > embedded.undeploy(new File("my-rar.rar").toURI().toURL()); > embedded.shutdown(); // does not work - some threads don't stop > Problems? > ========= > JCA transitive dependencies? > Accessing ds files from war? > Accessing rar from war? > May have to provide these both upfront. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:13:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:13:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1906) Improve CI timeout handling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1906: -------------------------------- Fix Version/s: (was: 5.later) > Improve CI timeout handling > --------------------------- > > Key: JBTM-1906 > URL: https://issues.jboss.org/browse/JBTM-1906 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > > We do not timeout the CI runs so that someone can have the opportunity to kill -3 the Java processes when they notice that the run has hung. It is therefore possible for the rogue processes to clog up CI. Also, if we were to move to alternative CI arrangements it may be necessary to set a timeout and in that case we would not have the opportunity to be alerted of the hang. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:14:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:14:02 -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: -------------------------------- Fix Version/s: 5.later (was: 6.later) > 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: 5.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 Tue Aug 11 12:15:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:15:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2318) Too verbose startup? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2318: -------------------------------- Fix Version/s: 5.later > Too verbose startup? > -------------------- > > Key: JBTM-2318 > URL: https://issues.jboss.org/browse/JBTM-2318 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.later > > > At startup of the most basic example we see ... > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService > INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem > INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start > INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > There's a separate conversation to be had about whether the INFO should be there (DEBUG maybe?) but ignoring those why do we print the other lines at all? -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2334) Improve ease of use within Tomcat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2334: ----------------------------------- Assignee: (was: Tom Jenkinson) > Improve ease of use within Tomcat > --------------------------------- > > Key: JBTM-2334 > URL: https://issues.jboss.org/browse/JBTM-2334 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.0.4 > Reporter: Mark Little > > It's still too difficult for people to do. > http://drieselliott.tumblr.com/post/99496743610/integrating-narayana-transaction-manager-with -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1359) HA Recovery Manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1359: ----------------------------------- Assignee: (was: Michael Musgrove) > HA Recovery Manager > ------------------- > > Key: JBTM-1359 > URL: https://issues.jboss.org/browse/JBTM-1359 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, JTS, Recovery, XTS > Reporter: Tom Jenkinson > Priority: Optional > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > JTA should work, but must consider JTS and XTS too (encoded IP addresses in log records) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2266) TransactionReaper is using currentTimeMillis for timeout calculation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2266: ----------------------------------- Assignee: (was: Tom Jenkinson) > TransactionReaper is using currentTimeMillis for timeout calculation > -------------------------------------------------------------------- > > Key: JBTM-2266 > URL: https://issues.jboss.org/browse/JBTM-2266 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Affects Versions: 5.0.3 > Reporter: David Lloyd > Priority: Minor > > Noticed while browsing through some code that the TransactionReaper uses currentTimeMillis() to calculate timeouts. However the timestamp reported by this method can change in an unexpected way if the system clock is changed. > An artificial clock based on System.nanoTime() should be used instead, since while this time may vary slightly between cores, in general it will be highly accurate and, most importantly, monotonic and steady (and unaffected by changes to the system time). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2293) Create a docker file to make web page update easier In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2293: ----------------------------------- Assignee: (was: Gytis Trikleris) > Create a docker file to make web page update easier > --------------------------------------------------- > > Key: JBTM-2293 > URL: https://issues.jboss.org/browse/JBTM-2293 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Cloud > Reporter: Gytis Trikleris > > Awestruct recuires quite a few dependencies to build a web page. Although it is not hard to install them manually, it is time consuming. It would be much easier to use docker for this. > This docker file is a good start: https://github.com/goldmann/dockerfiles/tree/master/awestruct -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1507) Review the TXBridge tests usage of Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1507: ----------------------------------- Assignee: (was: Gytis Trikleris) > Review the TXBridge tests usage of Arquillian > --------------------------------------------- > > Key: JBTM-1507 > URL: https://issues.jboss.org/browse/JBTM-1507 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Testing, TxBridge > Reporter: Paul Robinson > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > The TXBridge tests don;t seem to be using Arquillian correctly. There is a servlet that is invoked to do things inside the container. As the tests (should) now run in the container, this should not be needed. > The tests also seem to have added complexity due to the recovery tests. As the recovery tests need to be able to kill the container, it mandates manual container lifecycle management for *all* tests. We may want to pull out the recovery tests into a separate module. > We also may want to pull out the DisabledContextPropagationTest into a separate module as they use a modified AS configuration. > We should also take a general look at how the tests are structured and using Arq. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1982) Use logger to log all the exception stacktraces instead of several Exception.printStackTrace() calls which uses the stdout In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1982: ----------------------------------- Assignee: (was: Tom Jenkinson) > Use logger to log all the exception stacktraces instead of several Exception.printStackTrace() calls which uses the stdout > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1982 > URL: https://issues.jboss.org/browse/JBTM-1982 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, JTS > Affects Versions: 4.17.10 > Reporter: Ond?ej Chaloupka > Priority: Minor > > The arjuna code uses pattern e.printStackTrace() on several places in the code. This would be better to be changed for a logger would be used. > For ArjunaJTA I counted 28 (excluding tests) places where the logger is not used and I suppose it should be. > Secondary. It would be nice in case of the XAException the error code would be printed together with the exception stacktrace. I have one example where I would appreciated it for example. > It's ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java > method handleOrphan where after the xares.rollback(xid) is called the exception is printed to stdout + log does not contain the error code. > This issue was moved from https://bugzilla.redhat.com/show_bug.cgi?id=1007384. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-731) refactor qa tests to reduce code duplication In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-731: ---------------------------------- Assignee: (was: Ond?ej Chaloupka) > refactor qa tests to reduce code duplication > -------------------------------------------- > > Key: JBTM-731 > URL: https://issues.jboss.org/browse/JBTM-731 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 4.10.0 > Reporter: Jonathan Halliday > Priority: Minor > > The qa tests include a massive about of almost but not quite identical code. Refactor to reduce duplication. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2072) Improve CI timeout handling on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2072: ----------------------------------- Assignee: (was: Gytis Trikleris) > Improve CI timeout handling on Windows > -------------------------------------- > > Key: JBTM-2072 > URL: https://issues.jboss.org/browse/JBTM-2072 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:08 -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 ] Tom Jenkinson reassigned JBTM-1952: ----------------------------------- Assignee: (was: Gytis Trikleris) > 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 > > 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 Tue Aug 11 12:17:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1578) Run a performance benchmark over BlackTie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1578: ----------------------------------- Assignee: (was: Michael Musgrove) > Run a performance benchmark over BlackTie > ----------------------------------------- > > Key: JBTM-1578 > URL: https://issues.jboss.org/browse/JBTM-1578 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Performance Testing > Reporter: Tom Jenkinson > Priority: Minor > > Will BlackTie work with: http://www.infor.uva.es/~diego/tpcc-uva.html it is an opensource TPC-C benchmark -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:09 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-809) Provide instructions for using ironjacamar as well as transactional driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-809: ---------------------------------- Assignee: (was: Tom Jenkinson) > Provide instructions for using ironjacamar as well as transactional driver > -------------------------------------------------------------------------- > > Key: JBTM-809 > URL: https://issues.jboss.org/browse/JBTM-809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Reporter: Tom Jenkinson > > Supporting the transactional driver source code on the face of it duplicates much effort with the IronJacamar team. Supporting IronJacamar for datasource access should be possible as this is the connection manager in the Application Server and it provides an embedded mode for use outside of the application server. > There are several bugs open against transactional driver that will be resolved by completing this work. > The general approach would be along the lines of: > Startup > ====== > Embedded embedded = EmbeddedFactory.create(); > embedded.startup(); > embedded.deploy(new File("my-rar.rar").toURI().toURL()); > embedded.deploy(new File("my-ds.xml").toURI().toURL()); > In use > ===== > InitialContext initialContext = new InitialContext(); > UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction"); > DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS"); > Shutdown > ======= > embedded.undeploy(new File("my-ds.xml").toURI().toURL()); > embedded.undeploy(new File("my-rar.rar").toURI().toURL()); > embedded.shutdown(); // does not work - some threads don't stop > Problems? > ========= > JCA transitive dependencies? > Accessing ds files from war? > Accessing rar from war? > May have to provide these both upfront. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:09 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-845) Cloud ObjectStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-845: ---------------------------------- Assignee: (was: James Brealey) > Cloud ObjectStore > ----------------- > > Key: JBTM-845 > URL: https://issues.jboss.org/browse/JBTM-845 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Reporter: Tom Jenkinson > > Create an objectstore that uses infinispan or jgroups for replication of volatile data -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:09 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2471) Provide a mechanism to get stack dumps from the C++ binaries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2471: ----------------------------------- Assignee: (was: Amos Feng) > Provide a mechanism to get stack dumps from the C++ binaries > ------------------------------------------------------------ > > Key: JBTM-2471 > URL: https://issues.jboss.org/browse/JBTM-2471 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie > Reporter: Tom Jenkinson > > Currently debugging BlackTie is problematic as we are reliant on logs to know what was happening on stack dumping the application server to guess what is being called. It would be useful to provide a method to do this. > Potentially an open socket to connect to could dump the stacks or understanding how to do this on Windows and Linux natively. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:09 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1802) Consider moving Arquillian profiles to root pom.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1802: ----------------------------------- Assignee: (was: Amos Feng) > Consider moving Arquillian profiles to root pom.xml > --------------------------------------------------- > > Key: JBTM-1802 > URL: https://issues.jboss.org/browse/JBTM-1802 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Build System, Testing > Reporter: Paul Robinson > Priority: Minor > > We have three Arquillian profiles (for managed, remote and ipv6-managed) present in the pom of nearly every test that uses Arquillian. I suspect they can all be identical and thus placed int he root pom.xml. This should simplify maintenance and will ensure any fixes to this config are made throughout. > The problem is that we may have legitimate reasons for this config to differ for some tests. Maybe we could use overrides in these cases. > Assigning to Tom for his input. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:09 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1494) Produce performance figures to show performance improvements of Compensations over ACID In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1494: ----------------------------------- Assignee: (was: Gytis Trikleris) > Produce performance figures to show performance improvements of Compensations over ACID > --------------------------------------------------------------------------------------- > > Key: JBTM-1494 > URL: https://issues.jboss.org/browse/JBTM-1494 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing, XTS > Reporter: Paul Robinson > > As part of evangelising compensations, it would be useful to show performance comparisons for different classes of applications. > Ideally, these results should show that that, for certain classes of applications, the performance of a compensation-based transaction is a lot better than for an ACID transaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:10 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-576) update unit tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-576: ---------------------------------- Assignee: (was: Ond?ej Chaloupka) > update unit tests > ----------------- > > Key: JBTM-576 > URL: https://issues.jboss.org/browse/JBTM-576 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 4.7.0 > Reporter: Jonathan Halliday > Priority: Minor > > There are many unit tests that have lain dormant for some time. Convert them from DTF/junit3 to junit4, wire them to the build and make them pass. > This will be done incrementally, one module at a time, following the dependency chain e.g. common, ArjunaCore/arjuna, ArjunaCore/txoj, ... JTA/, .../JTS/... -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:10 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2478) Use Flame Graph tool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2478: ----------------------------------- Assignee: (was: Michael Musgrove) > Use Flame Graph tool > -------------------- > > Key: JBTM-2478 > URL: https://issues.jboss.org/browse/JBTM-2478 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Performance Testing > Reporter: Tom Jenkinson > > Tools and instructions are at: > https://github.com/jesperpedersen/perfjava/ <-- CPU sampling > https://github.com/jesperpedersen/javamemflame <-- Memory allocation tracking > Both use Agent_OnLoad/Agent_OnUnload, so better for smaller tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:10 -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 reassigned JBTM-2419: ----------------------------------- Assignee: (was: Michael Musgrove) > 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 > > 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 Tue Aug 11 12:17:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:10 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1906) Improve CI timeout handling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1906: ----------------------------------- Assignee: (was: Gytis Trikleris) > Improve CI timeout handling > --------------------------- > > Key: JBTM-1906 > URL: https://issues.jboss.org/browse/JBTM-1906 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Priority: Minor > > We do not timeout the CI runs so that someone can have the opportunity to kill -3 the Java processes when they notice that the run has hung. It is therefore possible for the rogue processes to clog up CI. Also, if we were to move to alternative CI arrangements it may be necessary to set a timeout and in that case we would not have the opportunity to be alerted of the hang. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:10 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2383) Update standalone JCA quickstarts to use IronJacamar test runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2383: ----------------------------------- Assignee: (was: Gytis Trikleris) > Update standalone JCA quickstarts to use IronJacamar test runner > ---------------------------------------------------------------- > > Key: JBTM-2383 > URL: https://issues.jboss.org/browse/JBTM-2383 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Gytis Trikleris > Priority: Minor > > See this post for the improvements in embedded IronJacamar container: https://groups.google.com/forum/#!topic/ironjacamar-developers/Pat7ixJuX6s -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:10 -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 reassigned JBTM-1454: ----------------------------------- Assignee: (was: Michael Musgrove) > 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 > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:10 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1266) Upload 2012 version of training material In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-1266: ----------------------------------- Assignee: (was: Tom Jenkinson) > Upload 2012 version of training material > ---------------------------------------- > > Key: JBTM-1266 > URL: https://issues.jboss.org/browse/JBTM-1266 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Affects Versions: 4.16.4 > Reporter: Paul Robinson > Priority: Minor > Attachments: txCompletion > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:17:10 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:17:10 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2473) Document qa/ build suite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2473: ----------------------------------- Assignee: (was: Tom Jenkinson) > Document qa/ build suite > ------------------------ > > Key: JBTM-2473 > URL: https://issues.jboss.org/browse/JBTM-2473 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Attachments: QA Notes (5.1).ppt > > > There is a wealth of testing in the qa/ testsuite but it is not accessible to understand what is being tested by it. > * How do we evaluate the impact of running less of the suite > * Is it possible to run the suite with other object stores easily? > * What is the quantified value of running the whole suite > * Can we run with different ORBs -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:20:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:20:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-870) Add more XTS quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-870: ------------------------------- Fix Version/s: (was: 6.later) > Add more XTS quickstarts > ------------------------ > > Key: JBTM-870 > URL: https://issues.jboss.org/browse/JBTM-870 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, XTS > Reporter: Paul Robinson > > See the individual sub tasks for more information. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:20:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:20:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-886) Simple WS-BA recovery quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-886: ------------------------------- Fix Version/s: (was: 6.later) > Simple WS-BA recovery quickstart > -------------------------------- > > Key: JBTM-886 > URL: https://issues.jboss.org/browse/JBTM-886 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, XTS > Reporter: Paul Robinson > > This quickstart will show what happens when a participant crashes at various key points in the protocol. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:20:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:20:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-887) Simple WS-AT recovery quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-887: ------------------------------- Fix Version/s: (was: 6.later) > Simple WS-AT recovery quickstart > -------------------------------- > > Key: JBTM-887 > URL: https://issues.jboss.org/browse/JBTM-887 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, XTS > Reporter: Paul Robinson > > This quickstart shows what happens when a participant fails at various points in the protocol. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:20:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:20:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1449) Transactions in the browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1449: -------------------------------- Fix Version/s: (was: 6.later) > Transactions in the browser > --------------------------- > > Key: JBTM-1449 > URL: https://issues.jboss.org/browse/JBTM-1449 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Student project > Reporter: jhalli > Labels: student > > Student project that we are not currently offering: > {quote} > Recent developments in web standards (HTML5, specifically Web Storage a.k.a. DOM Storage) indicates a move towards widespread availability of client (i.e. web browser) side persistent storage accessible by web applications. Initially useful for making content and applications available offline, this also open up the possibility of object replication between client and server. In this project you will explore the applicability of transaction concepts to applications built on this model. In particular, you will focus on identifying and exploiting new opportunities made available by the existence of persistent storage on the browser, a vital pre-requisite for recoverable transactions. > To undertake this project you should have a strong interest in web based applications, some javascript programming experience and a basic understanding of transactions concepts. Previous experience of at least one javascript framework would be an advantage. The work will be open source. > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:21:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:21:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1450) Transaction processing in javascript In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1450: -------------------------------- Fix Version/s: (was: 6.later) > Transaction processing in javascript > ------------------------------------ > > Key: JBTM-1450 > URL: https://issues.jboss.org/browse/JBTM-1450 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Student project > Reporter: jhalli > Labels: student > > Student project that we are not currently offering: > {quote} > Increasingly sophisticated applications are being implemented using the javascript language. Initially popular for browser based environments, the language is also gaining traction on the server side (NodeJS, etc). A single threaded model promotes use of callbacks and asynchronous I/O operations. Ongoing standardization work is starting to provide APIs for enterprise functionality (commonJS, IndexedDB, etc). The Rhino javascript engine allows javascript to run on any JVM. These factors lead to situations where distributed business applications may be written wholly or partially in javascript and may need to interact with existing business logic or services implemented in Java. In this project you will consider how to provide transaction management capabilities to such applications. > This project will require a good knowledge of javascript programming, ideally encompassing a server side javascript environment. Candidates should also possess some knowledge of Java and transaction concepts. The work will be open source. > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:21:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:21:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1515) Investigate the overhead of bridging JTA to WS-AT when not needed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1515: -------------------------------- Fix Version/s: (was: 6.later) > Investigate the overhead of bridging JTA to WS-AT when not needed > ----------------------------------------------------------------- > > Key: JBTM-1515 > URL: https://issues.jboss.org/browse/JBTM-1515 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Paul Robinson > > When using default context propagation, a subordinate WS-AT transaction will be created for Web service calls made within a JTA transaction. This is wasteful if the target service does not enlist any participants in this transaction. > We should measure the overhead that this imposes and take steps to reduce/remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:21:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 11 Aug 2015 12:21:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-974) Allow callback invocation for multiple business method invocations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-974: ------------------------------- Component/s: Compensations (was: TXFramework) > Allow callback invocation for multiple business method invocations > ------------------------------------------------------------------ > > Key: JBTM-974 > URL: https://issues.jboss.org/browse/JBTM-974 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Paul Robinson > Labels: TXFramework > Fix For: 6.later > > > By setting the 'single' attribute on a Lifecycle Handler Annotation (such as @Prepare or @Compensate) identifies whether more than one callback can be registered for the lifecycle method in response to multiple invocations of the ServiceRequest method. If it is true then the lifecycle method will be called once to the ServiceRequest method. If it is false then the lifecycle method will be called once in response to each (non-read only) call to the ServiceRequest method. The default is 'false'. > Annotation: > {code} > @Retention(RetentionPolicy.RUNTIME) > @Target(ElementType.METHOD) > public @interface Compensate > { > public boolean single() default false; > } > {code} > Example: > {code} > @ServiceRequest > public void addToBasket() > { > //Add another item to the basket. > } > @Compensate(single=true) > public void emptyBasket() > { > //Empty every item from the basket > } > {code} > In this example the @ServiceRequest may be invoked many times to add many items to the basket. The @Compensate method is only needed to be invoked once as the basket can be emptied in one operation. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:23:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Aug 2015 12:23:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2490. ------------------------------------ Resolution: Done To enable qa testing (via the narayana.sh script) with the openjdk orb you can either use: bq. PROFILE=QA_JTS_OPENJDKORB or bq. PROFILE=NONE together with OPENJDK_ORB=1 and QA_TESTS=1 The git commit id for the feature is 7fd2dbd > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 11 12:26:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Aug 2015 12:26:03 -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 ] Michael Musgrove updated JBTM-2212: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/897 > 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 Tue Aug 11 12:28:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Aug 2015 12:28:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2212) Minimize deprecation warnings for the RTS modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2212: ----------------------------------- Summary: Minimize deprecation warnings for the RTS modules (was: Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client, org.jboss.resteasy.spi and tooling) > Minimize deprecation warnings for the RTS modules > ------------------------------------------------- > > 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 Tue Aug 11 12:30:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 11 Aug 2015 12:30:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2212) Minimize deprecation warnings for the RTS modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2212: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done I only updated the RTS modules: * rts/at/bridge * rts/at/integration * rts/at/tx * rts/at/util * rts/at/webservice > Minimize deprecation warnings for the RTS modules > ------------------------------------------------- > > 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 Aug 12 01:43:02 2015 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Wed, 12 Aug 2015 01:43: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:comment-tabpanel&focusedCommentId=13097496#comment-13097496 ] Hayk Hovsepyan commented on JBTM-2245: -------------------------------------- Hi Tom, Mike, What is the planned fixed version of this task? Is there already a support of shutdown(timeout) in Narayana? I am asking as we have RFE https://issues.jboss.org/browse/EAP7-86 resolved and ready for QA. Thanks, Hayk. > 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.later > > > 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 Aug 12 03:01:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 03:01: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:comment-tabpanel&focusedCommentId=13097508#comment-13097508 ] Tom Jenkinson commented on JBTM-2245: ------------------------------------- Hi Hayk, Transactions were descoped from EAP7-86 if you look through the comments. We are delivering in WFLY 11. Thanks, Tom > 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.later > > > 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 Aug 12 07:05:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:05:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097569#comment-13097569 ] Tom Jenkinson commented on JBTM-2490: ------------------------------------- I had to add aef07f0cb507bb469343195bee11df38c7bcc73a as the openjdk jar is looked for before the dist is unzipped > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.2.2 > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:06:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2491) JTS and JacORB NS Docker images quickstart with Kubernetes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2491: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > JTS and JacORB NS Docker images quickstart with Kubernetes > ---------------------------------------------------------- > > Key: JBTM-2491 > URL: https://issues.jboss.org/browse/JBTM-2491 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create example Kubernetes configuration for JTS and JacORB NS Docker images. As well as a test case for them. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:06:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2485) Close and release nexus deployed artifacts from build script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2485: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > Close and release nexus deployed artifacts from build script > ------------------------------------------------------------ > > Key: JBTM-2485 > URL: https://issues.jboss.org/browse/JBTM-2485 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.next > > > Currently we need to visit the nexus site during NRP, it would be nice to be able to execute these steps from the command line as part of the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:06:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2481: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:06:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2480: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:06:06 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2476: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:06:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:07 -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:all-tabpanel ] Tom Jenkinson updated JBTM-2467: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > 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 Wed Aug 12 07:06:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:07 -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 ] Tom Jenkinson updated JBTM-2458: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > 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 Wed Aug 12 07:06:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:07 -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.2.2) > 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: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: compensations.tar > > > 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 Aug 12 07:06:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2468) xts, jts and rts performance comparison job has failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2468: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > 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 Wed Aug 12 07:06:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06: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 updated JBTM-2409: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > 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 Aug 12 07:06:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:07 -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.2.2) > 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 Wed Aug 12 07:06:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2312) Wrong logging format of ARJUNA016005 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2312: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > Wrong logging format of ARJUNA016005 > ------------------------------------ > > Key: JBTM-2312 > URL: https://issues.jboss.org/browse/JBTM-2312 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 4.17.24 > Reporter: Ond?ej Chaloupka > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Logging format of warning warn_recovery_failedtorecover is strange or maybe better to say wrong. It looks: > {code} > WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016005: JTS XARecoveryModule.xaRecovery - failed to recover XAResource. status is $2 > {code} > This message came from XAResourceRecord.xaRecoverySecondPass and it's message warn_recovery_failedtorecover. The code with dolar sign seems to me a bit confusing. > I think it would be better first not have the dolar sign there and second rather to print string representation of the error code. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:06:07 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:07 -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 (was: 5.2.2) > 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 Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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.2.2) > 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 Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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.2.2) > 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 Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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 (was: 5.2.2) > 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 Wed Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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.2.2) > 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 Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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 (was: 5.2.2) > 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 Wed Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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: 5.2.2) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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: 5.2.2) > 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 Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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: 5.2.2) > 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 Wed Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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.2.2) > 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 Wed Aug 12 07:06:08 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:08 -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: 5.2.2) > 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 Aug 12 07:06:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:09 -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: 5.2.2) > 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 Aug 12 07:06:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:09 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-855: ------------------------------- Fix Version/s: 5.next (was: 5.2.2) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:06:09 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:06:09 -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 (was: 5.2.2) > 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 Wed Aug 12 07:10:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:10:04 -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 closed JBTM-2328. ------------------------------- > 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.2.2 > > > 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 Wed Aug 12 07:10:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:10:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2487) Initialize method of JDBC object store driver uses a connection outside of a try with resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2487. ------------------------------- > Initialize method of JDBC object store driver uses a connection outside of a try with resources > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2487 > URL: https://issues.jboss.org/browse/JBTM-2487 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.2 > > > Offending code: https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L649 > Technique to use: > https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:10:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:10:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2212) Minimize deprecation warnings for the RTS modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2212. ------------------------------- > Minimize deprecation warnings for the RTS modules > ------------------------------------------------- > > 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.2.2 > > > 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 Aug 12 07:10:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:10:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2490. ------------------------------- > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.2.2 > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:10:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:10:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2486) JDBC object store closes connections after resultset/statements which is incorrect order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2486. ------------------------------- > JDBC object store closes connections after resultset/statements which is incorrect order > ---------------------------------------------------------------------------------------- > > Key: JBTM-2486 > URL: https://issues.jboss.org/browse/JBTM-2486 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.2 > > > As reported by IronJacamar team we should treat the JDBC resources as a stack. > Specific case reported: > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L347 > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L352 > https://gist.github.com/maeste/835073a1e8ea6e38b9bd -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:10:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:10:04 -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 closed JBTM-2225. ------------------------------- > 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.2.2 > > > 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 Wed Aug 12 07:15:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:15:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2486) JDBC object store closes connections after resultset/statements which is incorrect order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2486: --------------------------------- > JDBC object store closes connections after resultset/statements which is incorrect order > ---------------------------------------------------------------------------------------- > > Key: JBTM-2486 > URL: https://issues.jboss.org/browse/JBTM-2486 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.2 > > > As reported by IronJacamar team we should treat the JDBC resources as a stack. > Specific case reported: > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L347 > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L352 > https://gist.github.com/maeste/835073a1e8ea6e38b9bd -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:15:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:15:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2486) JDBC object store closes connections after resultset/statements which is incorrect order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2486: -------------------------------- Issue Type: Bug (was: Task) > JDBC object store closes connections after resultset/statements which is incorrect order > ---------------------------------------------------------------------------------------- > > Key: JBTM-2486 > URL: https://issues.jboss.org/browse/JBTM-2486 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.2 > > > As reported by IronJacamar team we should treat the JDBC resources as a stack. > Specific case reported: > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L347 > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L352 > https://gist.github.com/maeste/835073a1e8ea6e38b9bd -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 07:15:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 07:15:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2486) JDBC object store closes connections after resultset/statements which is incorrect order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2486. ------------------------------- Resolution: Done > JDBC object store closes connections after resultset/statements which is incorrect order > ---------------------------------------------------------------------------------------- > > Key: JBTM-2486 > URL: https://issues.jboss.org/browse/JBTM-2486 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.2 > > > As reported by IronJacamar team we should treat the JDBC resources as a stack. > Specific case reported: > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L347 > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/jdbc/JDBCImple_driver.java#L352 > https://gist.github.com/maeste/835073a1e8ea6e38b9bd -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 08:11:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Aug 2015 08:11:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2491) JTS and JacORB NS Docker images quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2491: ---------------------------------- Summary: JTS and JacORB NS Docker images quickstart (was: JTS and JacORB NS Docker images quickstart with Kubernetes) > JTS and JacORB NS Docker images quickstart > ------------------------------------------ > > Key: JBTM-2491 > URL: https://issues.jboss.org/browse/JBTM-2491 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create example Kubernetes configuration for JTS and JacORB NS Docker images. As well as a test case for them. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 08:11:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Aug 2015 08:11:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2491) JTS and JacORB NS Docker images quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2491: ---------------------------------- Description: Create a quickstart for JTS and JacORB Name Server Docker images. Additionally, add Kubernetes pod configuration for that. was:Create example Kubernetes configuration for JTS and JacORB NS Docker images. As well as a test case for them. > JTS and JacORB NS Docker images quickstart > ------------------------------------------ > > Key: JBTM-2491 > URL: https://issues.jboss.org/browse/JBTM-2491 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create a quickstart for JTS and JacORB Name Server Docker images. > Additionally, add Kubernetes pod configuration for that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 08:16:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 08:16:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2490: --------------------------------- OpenJDK jar was not defined in attempted fix > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.2.2 > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 08:18:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 08:18:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2490: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.2.2 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 08:18:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 08:18:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2490: -------------------------------- Affects Version/s: 5.2.2 > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.2.2 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 08:18:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 08:18:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097612#comment-13097612 ] Tom Jenkinson commented on JBTM-2490: ------------------------------------- Fixed here https://github.com/jbosstm/narayana/commit/1fd84b5189641e751845f73c7c00ecd8deb2fead > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.2.2 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 08:18:05 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 08:18:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2490) Possibility to run "qa" module with openjdk-orb In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2490. --------------------------------- Resolution: Done > Possibility to run "qa" module with openjdk-orb > ----------------------------------------------- > > Key: JBTM-2490 > URL: https://issues.jboss.org/browse/JBTM-2490 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.2.2 > Reporter: Hayk Hovsepyan > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > In QA testing suites we have several jenkins jobs which are running Narayana's "qa" module tests with "jacorb" enabled. > The run of "qa" module is done via "scripts/hudson/narayana.sh" script with having appropriate environment variables. > "QA_TESTS=1" and "JAC_ORB=1" > We need to modify these jobs to run with "openjdk-orb" enabled. > So what we request: > Adjust "scripts/hudson/narayana.sh" script to be able to provide "OPENJDK_ORB=1" variable so it will run "qa" tests with "openjdk-orb". -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 08:35:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 08:35:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2492) Build and deploy Blacktie as part of BRP.xml In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2492: ----------------------------------- Summary: Build and deploy Blacktie as part of BRP.xml Key: JBTM-2492 URL: https://issues.jboss.org/browse/JBTM-2492 Project: JBoss Transaction Manager Issue Type: Task Components: Release Process Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next We only update the Blacktie java artifacts so these should be able to be done from any machine: {code} call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" build.bat -f blacktie\wildfly-blacktie\pom.xml install -DskipTests build.bat -f blacktie\pom.xml install -DskipTests build.bat -f blacktie\pom.xml deploy -DskipTests {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 08:35:02 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Aug 2015 08:35:02 -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 ] Gytis Trikleris updated JBTM-2296: ---------------------------------- Git Pull Request: https://github.com/jboss-dockerfiles/narayana/pull/2 (was: https://github.com/jboss-dockerfiles/narayana/pull/2, https://github.com/jbosstm/quickstart/pull/145) > 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 Aug 12 08:41:03 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Aug 2015 08:41:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2491) JTS and JacORB NS Docker images quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2491: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/146 > JTS and JacORB NS Docker images quickstart > ------------------------------------------ > > Key: JBTM-2491 > URL: https://issues.jboss.org/browse/JBTM-2491 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create a quickstart for JTS and JacORB Name Server Docker images. > Additionally, add Kubernetes pod configuration for that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 10:45:05 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Aug 2015 10:45:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2481 started by Gytis Trikleris. --------------------------------------------- > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 11:08:03 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 11:08:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097711#comment-13097711 ] Tom Jenkinson commented on JBTM-2481: ------------------------------------- JBTM-2485 is the issue related to the Nexus upload > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 11:09:04 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 12 Aug 2015 11:09:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097712#comment-13097712 ] Tom Jenkinson commented on JBTM-2481: ------------------------------------- I updated NRP today with todays release. I think we could merge this lot into one command: {code} export PREVIOUS= export CURRENT= export NEXT= export WFLYISSUE= (cd scripts; ./pre-release.sh $CURRENT $NEXT) git fetch upstream; git checkout $CURRENT; MAVEN_OPTS="-XX:MaxPermSize=512m" ant -f build-release-pkgs.xml -Dmvn.executable="tools/maven/bin/mvn[.bat]" -Dawestruct.executable="awestruct[.bat]" all # if the rsync of the site hangs, ctrl-c the hang and: rsync -Pr --protocol=28 --delete-after _site/* jbosstm at filemgmt.jboss.org:www_htdocs/jbosstm/ (cd jboss-as; git fetch jbosstm; git checkout 5_BRANCH; git reset --hard jbosstm/5_BRANCH; sed -i "s/narayana>$CURRENT/narayana>$NEXT/g" pom.xml; git add pom.xml; git commit --amend -m "Update to latest version of Narayana"; git push -f) (cd jboss-as; git fetch wildfly; git checkout -b ${WFLYISSUE} wildfly/master; git branch -u jbosstm/${WFLYISSUE}; sed -i "s/narayana>$PREVIOUS/narayana>$CURRENT/g" pom.xml; git commit -am "${WFLYISSUE} Upgrade Narayana to $CURRENT"; git push) {code} It's probably something to do with my machine but you will note that the narayana.io upload sometimes hangs for me. > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 12 11:16:01 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 12 Aug 2015 11:16:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097717#comment-13097717 ] Gytis Trikleris commented on JBTM-2481: --------------------------------------- I've created this Jenkins view to experiment what could be useful for us: http://albany.eng.hst.ams2.redhat.com/view/Release%20Pipeline/ > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 13 07:54:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 13 Aug 2015 07:54: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: -------------------------------- Comment: was deleted (was: 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.2.0 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: compensations.tar > > > 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 Thu Aug 13 07:54:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 13 Aug 2015 07:54: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: -------------------------------- Comment: was deleted (was: 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.2.0 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: compensations.tar > > > 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 Thu Aug 13 07:55:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 13 Aug 2015 07:55: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: -------------------------------- Comment: was deleted (was: http://albany.eng.hst.ams2.redhat.com/job/JBTM-2454-narayana-ibm-jdk/) > 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: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: compensations.tar > > > 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 Thu Aug 13 07:55:02 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 13 Aug 2015 07:55: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=13097984#comment-13097984 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- Added a work around to code base such that we execute the localjunit sub modules by hand in narayana.sh rather than the parent pom > 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: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: compensations.tar > > > 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 Thu Aug 13 12:46:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 13 Aug 2015 12:46: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:all-tabpanel ] Michael Musgrove updated JBTM-2467: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/147, https://github.com/jbosstm/performance/pull/17 > 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 Thu Aug 13 12:47:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 13 Aug 2015 12:47:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2467) REST-AT undertow performance tests and quickstart fail In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2467: ----------------------------------- Summary: REST-AT undertow performance tests and quickstart fail (was: REST-AT performance tests fail) > REST-AT undertow performance tests and quickstart 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 Fri Aug 14 04:28:02 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 14 Aug 2015 04:28:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-855: --------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/148 update to add the jta example > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 04:57:02 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 14 Aug 2015 04:57: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:comment-tabpanel&focusedCommentId=13098263#comment-13098263 ] Amos Feng commented on JBTM-2234: --------------------------------- [~mmusgrov], can you show me how to start these jts performance tests ? > 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 Fri Aug 14 05:30:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 14 Aug 2015 05:30:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2467) REST-AT undertow performance tests and quickstart fail In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2467: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > REST-AT undertow performance tests and quickstart 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 Fri Aug 14 16:00:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 14 Aug 2015 16:00:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2488) Fix findbugs issues in rts modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2488: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/899 > Fix findbugs issues in rts modules > ---------------------------------- > > Key: JBTM-2488 > URL: https://issues.jboss.org/browse/JBTM-2488 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > The relevant issues can be seen by running: > bq. mvn site -DskipTests -Pfindbugs -f rts/pom.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 16:00:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 14 Aug 2015 16:00:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2488) Fix findbugs issues in rts modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2488: ----------------------------------- Description: The relevant issues can be seen by running: bq. mvn clean site -DskipTests -Pfindbugs -f rts/pom.xml was: The relevant issues can be seen by running: bq. mvn site -DskipTests -Pfindbugs -f rts/pom.xml > Fix findbugs issues in rts modules > ---------------------------------- > > Key: JBTM-2488 > URL: https://issues.jboss.org/browse/JBTM-2488 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > The relevant issues can be seen by running: > bq. mvn clean site -DskipTests -Pfindbugs -f rts/pom.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 17 11:40:27 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Aug 2015 11:40:27 -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: -------------------------------- Component/s: Transaction Core > 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 > Components: Transaction Core > 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 Mon Aug 17 11:59:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Aug 2015 11:59:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2312) Wrong logging format of ARJUNA016005 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2312: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/900 > Wrong logging format of ARJUNA016005 > ------------------------------------ > > Key: JBTM-2312 > URL: https://issues.jboss.org/browse/JBTM-2312 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 4.17.24 > Reporter: Ond?ej Chaloupka > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Logging format of warning warn_recovery_failedtorecover is strange or maybe better to say wrong. It looks: > {code} > WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016005: JTS XARecoveryModule.xaRecovery - failed to recover XAResource. status is $2 > {code} > This message came from XAResourceRecord.xaRecoverySecondPass and it's message warn_recovery_failedtorecover. The code with dolar sign seems to me a bit confusing. > I think it would be better first not have the dolar sign there and second rather to print string representation of the error code. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 17 12:00:28 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Aug 2015 12:00:28 -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=13098992#comment-13098992 ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- Workaround succeeded - moving out to later release > 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: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: compensations.tar > > > 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 Mon Aug 17 12:00:28 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Aug 2015 12:00:28 -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 reassigned JBTM-2454: ----------------------------------- Assignee: (was: Tom Jenkinson) > 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 > Priority: Minor > Fix For: 5.next > > Attachments: compensations.tar > > > 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 Mon Aug 17 12:01:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Aug 2015 12:01:26 -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: (was: 5.next) > 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 > Priority: Minor > Attachments: compensations.tar > > > 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 Mon Aug 17 12:01:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Aug 2015 12:01:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS [workaround implemented] 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: -------------------------------- Summary: Internal IBM J9 compiler error building XTS [workaround implemented] (was: Internal IBM J9 compiler error building XTS) > Internal IBM J9 compiler error building XTS [workaround implemented] > -------------------------------------------------------------------- > > 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 > Priority: Minor > Attachments: compensations.tar > > > 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 Mon Aug 17 14:55:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 17 Aug 2015 14:55:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2485) Close and release nexus deployed artifacts from build script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2485: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/901 > Close and release nexus deployed artifacts from build script > ------------------------------------------------------------ > > Key: JBTM-2485 > URL: https://issues.jboss.org/browse/JBTM-2485 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.next > > > Currently we need to visit the nexus site during NRP, it would be nice to be able to execute these steps from the command line as part of the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 18 08:51:27 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Aug 2015 08:51:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-846) Allow 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 updated JBTM-846: ------------------------------- Summary: Allow different configurations for transaction/recovery manager in a single JVM (was: Allow transactional MSC and WildFly EJB container to operate with different configurations for transaction/recovery manager in a single JVM) > Allow 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 Tue Aug 18 08:53:29 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Aug 2015 08:53:29 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1558) Prune redundant code from jboss-transaction-spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1558: -------------------------------- Priority: Optional (was: Major) > Prune redundant code from jboss-transaction-spi > ----------------------------------------------- > > Key: JBTM-1558 > URL: https://issues.jboss.org/browse/JBTM-1558 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.later > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started > There is much old code in jboss-transaction-spi that does not get used in AS7 and does not apply to Narayana. > Run tattletale over AS8, identify redundant methods and add new SPI functions if necessary -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 18 08:59:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Aug 2015 08:59:26 -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: -------------------------------- Priority: Optional (was: Major) > 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 > Priority: Optional > 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 Aug 18 09:15:32 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Aug 2015 09:15:32 -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: -------------------------------- Priority: Major (was: Minor) > 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 > 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 Tue Aug 18 09:16:27 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Aug 2015 09:16:27 -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=13099386#comment-13099386 ] Tom Jenkinson commented on JBTM-1854: ------------------------------------- Upped to Major as we are now targetting JDKORB > 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 > 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 Tue Aug 18 10:06:28 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 18 Aug 2015 10:06:28 -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:comment-tabpanel&focusedCommentId=13099456#comment-13099456 ] Michael Musgrove commented on JBTM-2234: ---------------------------------------- ./build.sh -f ArjunaJTS/jts/pom.xml -Dtest=com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 but you don't need to duplicate it since the issue is that the logger stores the messages in memory and only dumps them to a file at the end of the test. So you just need to reduce the JacORB logging level from INFO to just WARN and to verify the fix check that the log file does not contain any INFO messages. > 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 Tue Aug 18 10:47:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Aug 2015 10:47:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1699) Changes to the transaction SPI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1699: -------------------------------- Fix Version/s: 5.later (was: 6.later) > Changes to the transaction SPI > ------------------------------ > > Key: JBTM-1699 > URL: https://issues.jboss.org/browse/JBTM-1699 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > Original Estimate: 1 week, 3 days > Remaining Estimate: 1 week, 3 days > > wildfly is using a number of our internal com.arjuna interfaces which we would like to resolve by providing the same functionality in the transactions SPI. > Additionally the current SPI contains a number of unused classes which need removing. > I have created https://github.com/jbosstm/jboss-transaction-spi to manage the changes. To avoid any potential confusion and to make it clear who is responsible for the SPI we will be changing the package names. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 18 10:49:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 18 Aug 2015 10:49:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2103) ORB-less JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2103: -------------------------------- Fix Version/s: 6.later (was: 5.later) > ORB-less JTS > ------------ > > Key: JBTM-2103 > URL: https://issues.jboss.org/browse/JBTM-2103 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.0 > Reporter: Mark Little > Assignee: Michael Musgrove > Fix For: 6.later > > > At some point in the future there's a good chance that the ORB requirement will be removed from EE entirely. If that happens we need to be able to react and ensure that the JTS continues to work because it?s the most complete distributed transaction implementation that we possess. Now there are two ways to do that: > (i) we ship our own ORB, either JacORB or something else, say. > (ii) we remove the dependency on CORBA entirely. > Whilst (i) is a good short term option, I think we need to look at (ii). An old in-house TM that JBoss had which Narayana replaced had a JTS implementation which supported CORBA and JBoss Remoting (I think it was Remoting). Ultimately what we need is a high performance distributed transactions implementation and JTS is it today but it has a dependency on CORBA that we need to try to remove and yet keep most of the non-ORB generated code/dependencies. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 18 12:15:29 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 18 Aug 2015 12:15:29 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2493) REST-AT integration API silently ignores non persistable participants In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2493: -------------------------------------- Summary: REST-AT integration API silently ignores non persistable participants Key: JBTM-2493 URL: https://issues.jboss.org/browse/JBTM-2493 Project: JBoss Transaction Manager Issue Type: Bug Components: REST Affects Versions: 5.2.2 Reporter: Michael Musgrove Assignee: Gytis Trikleris The RESTAT integration API Participant interface is serialized during commit processing (in the method org.jboss.narayana.rest.integration.RecoveryManager#persistParticipantInformation) but the interface does not document this responsibility. The javadoc should say something like: {code} * Participant implementations must be implement either {@link java.io.Serializable} or {@link PersistableParticipant} } Secondly, during commit processing RecoveryManager#persistParticipantInformation needs to throw an exception if the participant cannot be written to the object store. At the moment it just writes a TRACE message. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 02:07:27 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 19 Aug 2015 02:07:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-855: --------------------------- Priority: Major (was: Minor) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 06:55:26 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 19 Aug 2015 06:55:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2494) Product Comparison Benchmark failure In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2494: -------------------------------------- Summary: Product Comparison Benchmark failure Key: JBTM-2494 URL: https://issues.jboss.org/browse/JBTM-2494 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.2.2 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The benchmark CI job (narayana-benchmarks) fails when doing a product comparison test: {code} java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:203) at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:185) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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:745) Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.arjuna.ats.arjuna.coordinator.TxControl at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:94) at io.narayana.perf.product.ProductWorker.doWork(ProductWorker.java:48) at io.narayana.perf.product.ProductComparison.testNarayana(ProductComparison.java:69) at io.narayana.perf.product.generated.ProductComparison_testNarayana.testNarayana_Throughput(ProductComparison_testNarayana.java:68) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 07:12:26 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 19 Aug 2015 07:12:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2494) Product Comparison Benchmark failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2494: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/performance/pull/18 > Product Comparison Benchmark failure > ------------------------------------ > > Key: JBTM-2494 > URL: https://issues.jboss.org/browse/JBTM-2494 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The benchmark CI job (narayana-benchmarks) fails when doing a product comparison test: > {code} > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:203) > at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:185) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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:745) > Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.arjuna.ats.arjuna.coordinator.TxControl > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:94) > at io.narayana.perf.product.ProductWorker.doWork(ProductWorker.java:48) > at io.narayana.perf.product.ProductComparison.testNarayana(ProductComparison.java:69) > at io.narayana.perf.product.generated.ProductComparison_testNarayana.testNarayana_Throughput(ProductComparison_testNarayana.java:68) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 09:46:27 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 19 Aug 2015 09:46:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2488) Fix findbugs issues in rts modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2488: ----------------------------------- Description: The relevant issues can be seen by running: bq. mvn clean install -DskipTests bq. mvn site -DskipTests -Pfindbugs -f rts/pom.xml was: The relevant issues can be seen by running: bq. mvn clean site -DskipTests -Pfindbugs -f rts/pom.xml > Fix findbugs issues in rts modules > ---------------------------------- > > Key: JBTM-2488 > URL: https://issues.jboss.org/browse/JBTM-2488 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > The relevant issues can be seen by running: > bq. mvn clean install -DskipTests > bq. mvn site -DskipTests -Pfindbugs -f rts/pom.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 12:02:28 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 19 Aug 2015 12:02:28 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2488) Fix findbugs issues in rts modules In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2488: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Fix findbugs issues in rts modules > ---------------------------------- > > Key: JBTM-2488 > URL: https://issues.jboss.org/browse/JBTM-2488 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > The relevant issues can be seen by running: > bq. mvn clean install -DskipTests > bq. mvn site -DskipTests -Pfindbugs -f rts/pom.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 12:11:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Aug 2015 12:11:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson moved BLACKTIE-450 to JBTM-2495: ---------------------------------------------- Project: JBoss Transaction Manager (was: Blacktie) Key: JBTM-2495 (was: BLACKTIE-450) Affects Version/s: 5.0.0.M2 (was: 5.0.0.M2) Component/s: Documentation (was: Documentation) > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Tom Jenkinson > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 12:11:27 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Aug 2015 12:11:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099895#comment-13099895 ] Tom Jenkinson commented on JBTM-2495: ------------------------------------- Also, please note we are tracking under Narayana (JBTM) ITS now. I have moved the issue for you, if you got an old reference please let me know where from and I will update it. > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Tom Jenkinson > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 12:11:27 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 19 Aug 2015 12:11:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2495: -------------------------------- Component/s: BlackTie > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Tom Jenkinson > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 22:44:27 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 19 Aug 2015 22:44:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng reassigned JBTM-2495: ------------------------------- Assignee: Amos Feng (was: Tom Jenkinson) > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 22:44:27 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 19 Aug 2015 22:44:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2495: ---------------------------- Fix Version/s: 5.next > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 23:05:26 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 19 Aug 2015 23:05:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099998#comment-13099998 ] Amos Feng commented on JBTM-2495: --------------------------------- The failures related to the upgrading to the activemq artimes in WFLY 10. Also in the Step 5, you should run with standalone-blacktie.xml {code} copy docs/examples/configs/standalone-blacktie.xml wildfly-/standalone/configurations bin/standalone.sh -c standalone-blacktie.xml {code} I'm sorry that I can not find in the QS to say use WFLY 9 but I will update the README.md to say it should integrate with the master from WFLY. can you show me where you find the information to run with WFLY 9 ? > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 20 01:52:26 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 20 Aug 2015 01:52:26 -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:comment-tabpanel&focusedCommentId=13100036#comment-13100036 ] Amos Feng commented on JBTM-2234: --------------------------------- Thanks Mike, I create the jacorb.properties in the ArjunaJTS/jts/src/test/resource and add "jacorb.log.default.verbosity=2". But it looks like there are still INFO messages in the surefire-report/com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2-output.txt > 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 Thu Aug 20 02:01:26 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 20 Aug 2015 02:01:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2496) Investigate using of camel for content based routing in the Blacktie In-Reply-To: References: Message-ID: Amos Feng created JBTM-2496: ------------------------------- Summary: Investigate using of camel for content based routing in the Blacktie Key: JBTM-2496 URL: https://issues.jboss.org/browse/JBTM-2496 Project: JBoss Transaction Manager Issue Type: Task Components: BlackTie, Demonstrator Reporter: Amos Feng Assignee: Amos Feng Priority: Minor Fix For: 5.later The current cbr quickstart is out-of-date by using the jboss-esb and it needs to investigate the camel -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 20 05:22:26 2015 From: issues at jboss.org (Joice Joy (JIRA)) Date: Thu, 20 Aug 2015 05:22:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100110#comment-13100110 ] Joice Joy commented on JBTM-2495: --------------------------------- I have tried using Wildfly 10 and it worked. THanks for the help. I used Wildfly 9 as 10 was a beta and was not sure it was stable. Also there was no mention that Blacktie only integrates with master from WFLY. > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 20 05:25:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 20 Aug 2015 05:25:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100111#comment-13100111 ] Tom Jenkinson commented on JBTM-2495: ------------------------------------- Yes, sorry about that. BlackTie has some quite tight integration with WFLY for subsystem stuff and so when major upgrades of WFLY occur we sometimes lose compatibility with the older version. > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 20 06:13:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 20 Aug 2015 06:13:26 -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:comment-tabpanel&focusedCommentId=13100139#comment-13100139 ] Tom Jenkinson commented on JBTM-2234: ------------------------------------- I had a look at this too and can't seem to influence the JacORB logger. Is it possible its not reading those settings because the logger is not set? I tried to add: jacorb.log.loggerFactory=org.jboss.util.Log4jLoggerFactory But that didn't seem to make a difference - maybe we don't have log4j in the classpath so some default not controllable logger is being used? > 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 Thu Aug 20 06:37:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 20 Aug 2015 06:37:26 -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:comment-tabpanel&focusedCommentId=13100147#comment-13100147 ] Tom Jenkinson commented on JBTM-2234: ------------------------------------- Just a note that I think the logging is going to System.err so I really think it could be that the log implementation is not found and some default is being used.... > 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 Thu Aug 20 08:09:26 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 20 Aug 2015 08:09:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2494) Product Comparison Benchmark failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2494: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Product Comparison Benchmark failure > ------------------------------------ > > Key: JBTM-2494 > URL: https://issues.jboss.org/browse/JBTM-2494 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The benchmark CI job (narayana-benchmarks) fails when doing a product comparison test: > {code} > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:203) > at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:185) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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:745) > Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.arjuna.ats.arjuna.coordinator.TxControl > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:94) > at io.narayana.perf.product.ProductWorker.doWork(ProductWorker.java:48) > at io.narayana.perf.product.ProductComparison.testNarayana(ProductComparison.java:69) > at io.narayana.perf.product.generated.ProductComparison_testNarayana.testNarayana_Throughput(ProductComparison_testNarayana.java:68) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 20 08:14:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 20 Aug 2015 08:14:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2497) Update or remove references of HornetQ to Artemis In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2497: ----------------------------------- Summary: Update or remove references of HornetQ to Artemis Key: JBTM-2497 URL: https://issues.jboss.org/browse/JBTM-2497 Project: JBoss Transaction Manager Issue Type: Feature Request Components: BlackTie, Demonstrator, Documentation Reporter: Tom Jenkinson Assignee: Amos Feng Fix For: 5.next There were reports of HornetQ still in at least the fooapp QS. We should try to remove references to the specific implementation unless necessary and in those cases use the correct name which is now Artemis. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 20 09:11:26 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 20 Aug 2015 09:11:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2498: -------------------------------------- Summary: Incomplete BlackTie quickstart documentation Key: JBTM-2498 URL: https://issues.jboss.org/browse/JBTM-2498 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie, Demonstrator, Documentation Affects Versions: 5.2.2 Reporter: Michael Musgrove Assignee: Amos Feng The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 20 13:19:26 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 20 Aug 2015 13:19:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2497) Update or remove references of HornetQ to Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100366#comment-13100366 ] Michael Musgrove commented on JBTM-2497: ---------------------------------------- The reference you refer to was only in the README.md which was correct when we were using old versions of the app server. Since moving to the later version all the BlackTie README.md files need updating so the Hornetq reference would disappear as a consequence of that update. So this JIRA needs rejecting and the correct JIRA for the README updates is JBTM-2498 > Update or remove references of HornetQ to Artemis > ------------------------------------------------- > > Key: JBTM-2497 > URL: https://issues.jboss.org/browse/JBTM-2497 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: BlackTie, Demonstrator, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > There were reports of HornetQ still in at least the fooapp QS. We should try to remove references to the specific implementation unless necessary and in those cases use the correct name which is now Artemis. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 21 11:14:26 2015 From: issues at jboss.org (Johnathon Lee (JIRA)) Date: Fri, 21 Aug 2015 11:14:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS). In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johnathon Lee updated JBTM-223: ------------------------------- > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Fix For: 6.later > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 24 06:45:27 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Aug 2015 06:45:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100977#comment-13100977 ] Tom Jenkinson commented on JBTM-2498: ------------------------------------- I think the quickstart should "wget https://raw.githubusercontent.com/jbosstm/narayana/5.2.3.Final-SNAPSHOT/blacktie/scripts/hudson/initializeJBoss.xml" rather than using a copy paste from: https://github.com/jbosstm/quickstart/blob/master/blacktie/test/initializeBlackTie.xml > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 24 06:46:26 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Aug 2015 06:46:26 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100978#comment-13100978 ] Tom Jenkinson commented on JBTM-2498: ------------------------------------- I made a minor tweak: https://github.com/jbosstm/narayana/commit/68797e32582c365cc0f1248b67eead097e39093f > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 24 07:32:29 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Aug 2015 07:32:29 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2499) Race condition between BlackTie subsystem and Artemis starting up In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2499: ----------------------------------- Summary: Race condition between BlackTie subsystem and Artemis starting up Key: JBTM-2499 URL: https://issues.jboss.org/browse/JBTM-2499 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Occasionally TcpServer tries to lookup ConnectionFactory before Artemis has started that component. Solution is to delay the lookup until the subsystem is accessed which should work and at least will not bork the TcpServer thread and fail the entire subsystem until reboot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 24 08:46:27 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 24 Aug 2015 08:46:27 -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 ] Gytis Trikleris updated JBTM-2296: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 Aug 24 09:09:27 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Aug 2015 09:09:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101041#comment-13101041 ] Tom Jenkinson commented on JBTM-2498: ------------------------------------- More minor tweaks: https://github.com/jbosstm/narayana/commit/d859990733d9530502358b87e92713e4ab95febe > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 24 10:02:28 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 24 Aug 2015 10:02:28 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2499) Race condition between BlackTie subsystem and Artemis starting up In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2499: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/903/files > Race condition between BlackTie subsystem and Artemis starting up > ----------------------------------------------------------------- > > Key: JBTM-2499 > URL: https://issues.jboss.org/browse/JBTM-2499 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Occasionally TcpServer tries to lookup ConnectionFactory before Artemis has started that component. > Solution is to delay the lookup until the subsystem is accessed which should work and at least will not bork the TcpServer thread and fail the entire subsystem until reboot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 07:57:42 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 25 Aug 2015 07:57:42 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2468) xts, jts and rts performance comparison job has failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris reassigned JBTM-2468: ------------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > 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: Gytis Trikleris > 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 Tue Aug 25 09:24:43 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 25 Aug 2015 09:24:43 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2312) Wrong logging format of ARJUNA016005 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2312: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Wrong logging format of ARJUNA016005 > ------------------------------------ > > Key: JBTM-2312 > URL: https://issues.jboss.org/browse/JBTM-2312 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 4.17.24 > Reporter: Ond?ej Chaloupka > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Logging format of warning warn_recovery_failedtorecover is strange or maybe better to say wrong. It looks: > {code} > WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016005: JTS XARecoveryModule.xaRecovery - failed to recover XAResource. status is $2 > {code} > This message came from XAResourceRecord.xaRecoverySecondPass and it's message warn_recovery_failedtorecover. The code with dolar sign seems to me a bit confusing. > I think it would be better first not have the dolar sign there and second rather to print string representation of the error code. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:23:42 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 25 Aug 2015 10:23:42 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2485) Close and release nexus deployed artifacts from build script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2485: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Close and release nexus deployed artifacts from build script > ------------------------------------------------------------ > > Key: JBTM-2485 > URL: https://issues.jboss.org/browse/JBTM-2485 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.next > > > Currently we need to visit the nexus site during NRP, it would be nice to be able to execute these steps from the command line as part of the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:25:43 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 25 Aug 2015 10:25:43 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2494) Product Comparison Benchmark missing dependency on Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2494: -------------------------------- Summary: Product Comparison Benchmark missing dependency on Artemis (was: Product Comparison Benchmark failure) > Product Comparison Benchmark missing dependency on Artemis > ---------------------------------------------------------- > > Key: JBTM-2494 > URL: https://issues.jboss.org/browse/JBTM-2494 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The benchmark CI job (narayana-benchmarks) fails when doing a product comparison test: > {code} > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:203) > at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:185) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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:745) > Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.arjuna.ats.arjuna.coordinator.TxControl > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:94) > at io.narayana.perf.product.ProductWorker.doWork(ProductWorker.java:48) > at io.narayana.perf.product.ProductComparison.testNarayana(ProductComparison.java:69) > at io.narayana.perf.product.generated.ProductComparison_testNarayana.testNarayana_Throughput(ProductComparison_testNarayana.java:68) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:25:43 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 25 Aug 2015 10:25:43 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2494) Product Comparison Benchmark missing dependency on Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2494: -------------------------------- Component/s: Performance Testing > Product Comparison Benchmark missing dependency on Artemis > ---------------------------------------------------------- > > Key: JBTM-2494 > URL: https://issues.jboss.org/browse/JBTM-2494 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The benchmark CI job (narayana-benchmarks) fails when doing a product comparison test: > {code} > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:203) > at org.openjdk.jmh.runner.LoopBenchmarkHandler$BenchmarkTask.call(LoopBenchmarkHandler.java:185) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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:745) > Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.arjuna.ats.arjuna.coordinator.TxControl > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:94) > at io.narayana.perf.product.ProductWorker.doWork(ProductWorker.java:48) > at io.narayana.perf.product.ProductComparison.testNarayana(ProductComparison.java:69) > at io.narayana.perf.product.generated.ProductComparison_testNarayana.testNarayana_Throughput(ProductComparison_testNarayana.java:68) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 26 05:57:44 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 26 Aug 2015 05:57:44 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2500) Update version of jboss-logging to 3.1.4.GA In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2500: ----------------------------------- Summary: Update version of jboss-logging to 3.1.4.GA Key: JBTM-2500 URL: https://issues.jboss.org/browse/JBTM-2500 Project: JBoss Transaction Manager Issue Type: Component Upgrade Components: SPI Reporter: Tom Jenkinson Assignee: Michael Musgrove Upgrade the version of jboss-logging to latest version. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 26 06:01:42 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 26 Aug 2015 06:01:42 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2500) Update version of jboss-logging to 3.1.4.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101911#comment-13101911 ] Tom Jenkinson commented on JBTM-2500: ------------------------------------- Done: https://github.com/jbosstm/jboss-transaction-spi/commit/49ffd6e8c7b2d0b99f68702c9788dcaa7ecd8750 > Update version of jboss-logging to 3.1.4.GA > ------------------------------------------- > > Key: JBTM-2500 > URL: https://issues.jboss.org/browse/JBTM-2500 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: SPI > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > Upgrade the version of jboss-logging to latest version. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 26 06:02:43 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 26 Aug 2015 06:02:43 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2500) Update version of jboss-logging to 3.1.4.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2500: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1238927 > Update version of jboss-logging to 3.1.4.GA > ------------------------------------------- > > Key: JBTM-2500 > URL: https://issues.jboss.org/browse/JBTM-2500 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: SPI > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > Upgrade the version of jboss-logging to latest version. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 26 06:02:44 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 26 Aug 2015 06:02:44 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2500) Update version of jboss-logging to 3.1.4.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2500. --------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) Resolution: Done > Update version of jboss-logging to 3.1.4.GA > ------------------------------------------- > > Key: JBTM-2500 > URL: https://issues.jboss.org/browse/JBTM-2500 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: SPI > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Upgrade the version of jboss-logging to latest version. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 26 06:02:44 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 26 Aug 2015 06:02:44 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2485) Close and release nexus deployed artifacts from build script In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101913#comment-13101913 ] Tom Jenkinson commented on JBTM-2485: ------------------------------------- Also added to SPI: https://github.com/jbosstm/jboss-transaction-spi/commit/bc91bcdbe049fdb6af38d034b989192a5d618ef7 > Close and release nexus deployed artifacts from build script > ------------------------------------------------------------ > > Key: JBTM-2485 > URL: https://issues.jboss.org/browse/JBTM-2485 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.next > > > Currently we need to visit the nexus site during NRP, it would be nice to be able to execute these steps from the command line as part of the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 26 06:10:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 26 Aug 2015 06:10:49 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2500) Update version of jboss-logging to 3.1.4.GA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101916#comment-13101916 ] Tom Jenkinson commented on JBTM-2500: ------------------------------------- Released in jboss-transaction-spi 7.3.1.Final > Update version of jboss-logging to 3.1.4.GA > ------------------------------------------- > > Key: JBTM-2500 > URL: https://issues.jboss.org/browse/JBTM-2500 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: SPI > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Upgrade the version of jboss-logging to latest version. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 28 04:51:05 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 28 Aug 2015 04:51:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2501) JTA 1.2 quickstart fails to start container In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2501: ------------------------------------- Summary: JTA 1.2 quickstart fails to start container Key: JBTM-2501 URL: https://issues.jboss.org/browse/JBTM-2501 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Blocker Fix For: 5.next All quickstart CI jobs currently fail because "JTA 1.2 in Wildfly" example fails to start a container. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 28 04:58:05 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 28 Aug 2015 04:58:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2501) JTA 1.2 quickstart fails to start container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2501 started by Gytis Trikleris. --------------------------------------------- > JTA 1.2 quickstart fails to start container > ------------------------------------------- > > Key: JBTM-2501 > URL: https://issues.jboss.org/browse/JBTM-2501 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > All quickstart CI jobs currently fail because "JTA 1.2 in Wildfly" example fails to start a container. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 28 05:43:06 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 28 Aug 2015 05:43:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2501) Update quickstarts to use org.wildfly.arquillian instead of org.wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2501: ---------------------------------- Summary: Update quickstarts to use org.wildfly.arquillian instead of org.wildfly (was: JTA 1.2 quickstart fails to start container) > Update quickstarts to use org.wildfly.arquillian instead of org.wildfly > ----------------------------------------------------------------------- > > Key: JBTM-2501 > URL: https://issues.jboss.org/browse/JBTM-2501 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > All quickstart CI jobs currently fail because "JTA 1.2 in Wildfly" example fails to start a container. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 28 05:45:05 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 28 Aug 2015 05:45:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2501) Update quickstarts to use org.wildfly.arquillian instead of org.wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2501: ---------------------------------- Description: Currently quickstarts use org.wildfly group to get managed and remote containers. This imposes dependency on the specific WildFly version. org.wildfly.arquillian had separate versioning from WildFly, thus it is easier to keep up. (was: All quickstart CI jobs currently fail because "JTA 1.2 in Wildfly" example fails to start a container.) > Update quickstarts to use org.wildfly.arquillian instead of org.wildfly > ----------------------------------------------------------------------- > > Key: JBTM-2501 > URL: https://issues.jboss.org/browse/JBTM-2501 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > Currently quickstarts use org.wildfly group to get managed and remote containers. This imposes dependency on the specific WildFly version. org.wildfly.arquillian had separate versioning from WildFly, thus it is easier to keep up. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 28 06:59:05 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 28 Aug 2015 06:59:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2501) Remove quickstart dependency on WildFly version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2501: ---------------------------------- Summary: Remove quickstart dependency on WildFly version (was: Update quickstarts to use org.wildfly.arquillian instead of org.wildfly) > Remove quickstart dependency on WildFly version > ----------------------------------------------- > > Key: JBTM-2501 > URL: https://issues.jboss.org/browse/JBTM-2501 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > Currently quickstarts use org.wildfly group to get managed and remote containers. This imposes dependency on the specific WildFly version. org.wildfly.arquillian had separate versioning from WildFly, thus it is easier to keep up. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 28 07:04:05 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 28 Aug 2015 07:04:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2501) Remove quickstart dependency on WildFly version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2501: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/quickstart/pull/149 > Remove quickstart dependency on WildFly version > ----------------------------------------------- > > Key: JBTM-2501 > URL: https://issues.jboss.org/browse/JBTM-2501 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > Currently quickstarts use org.wildfly group to get managed and remote containers. This imposes dependency on the specific WildFly version. org.wildfly.arquillian had separate versioning from WildFly, thus it is easier to keep up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)