From issues at jboss.org Mon Jan 2 07:07:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 07:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2766) Implement pooling for transactional driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2766: ---------------------------------- Description: Transactional driver does not provide connection pooling. We should either implement it ourselves or find a third party implementation. In case of the second option we should test it and provide a demonstration and blog post of its usage. > Implement pooling for transactional driver > ------------------------------------------ > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > Transactional driver does not provide connection pooling. We should either implement it ourselves or find a third party implementation. In case of the second option we should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 2 07:08:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 07:08:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2765) Document Narayana Tomcat module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2765: ---------------------------------- Description: Tomcat module is not documented in http://narayana.io//docs/project/index.html. > Document Narayana Tomcat module > ------------------------------- > > Key: JBTM-2765 > URL: https://issues.jboss.org/browse/JBTM-2765 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > Tomcat module is not documented in http://narayana.io//docs/project/index.html. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 2 07:11:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 07:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2764) Simple Narayana and Tomcat quickstart to demonstrate new module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2764: ---------------------------------- Description: We should provide one or more examples of Narayana Tomcat module. E.g. one simple example, one more complex example with crash scenario, one example with pooling (depending on the outcome of https://issues.jboss.org/browse/JBTM-2766). > Simple Narayana and Tomcat quickstart to demonstrate new module > --------------------------------------------------------------- > > Key: JBTM-2764 > URL: https://issues.jboss.org/browse/JBTM-2764 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > We should provide one or more examples of Narayana Tomcat module. E.g. one simple example, one more complex example with crash scenario, one example with pooling (depending on the outcome of https://issues.jboss.org/browse/JBTM-2766). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 2 07:16:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 07:16:00 -0500 (EST) 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: ---------------------------------- Description: Currently there is only one quickstart for docker (https://github.com/jbosstm/quickstart/tree/master/jts-docker), 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? was: 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? > 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 (https://github.com/jbosstm/quickstart/tree/master/jts-docker), 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 (v7.2.3#72005) From issues at jboss.org Mon Jan 2 07:48:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 07:48:00 -0500 (EST) 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 ] Gytis Trikleris updated JBTM-1719: ---------------------------------- Description: Implement more unit and integration tests to cover more aspects of multiplexor functionality (https://github.com/jbosstm/narayana/tree/master/rts/at/integration). Especially recovery. (was: Implement more unit and integration tests to cover more aspects of multiplexor functionality. Especially recovery.) > 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 (https://github.com/jbosstm/narayana/tree/master/rts/at/integration). Especially recovery. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 2 07:52:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 07:52:00 -0500 (EST) 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:comment-tabpanel&focusedCommentId=13342238#comment-13342238 ] Gytis Trikleris commented on JBTM-1856: --------------------------------------- There is an example with Hibernate available on Github: https://github.com/jbosstm/quickstart/tree/master/jta-and-hibernate-standalone. But still a simple standalone example would be useful. > 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 (v7.2.3#72005) From issues at jboss.org Mon Jan 2 08:16:01 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 08:16:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1864) Implement volatile participant interface for REST-AT integration API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-1864. --------------------------------- Resolution: Duplicate Issue > Implement volatile participant interface for REST-AT integration API > -------------------------------------------------------------------- > > Key: JBTM-1864 > URL: https://issues.jboss.org/browse/JBTM-1864 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 6.later > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 2 08:32:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 08:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2340) Implement POC of MongoDB extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2340. --------------------------------- Fix Version/s: (was: 5.later) Resolution: Won't Do > Implement POC of MongoDB extension > ---------------------------------- > > Key: JBTM-2340 > URL: https://issues.jboss.org/browse/JBTM-2340 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 2 08:32:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 08:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2340) Implement POC of MongoDB extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris deleted JBTM-2340: ---------------------------------- > Implement POC of MongoDB extension > ---------------------------------- > > Key: JBTM-2340 > URL: https://issues.jboss.org/browse/JBTM-2340 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 2 08:33:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 08:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2339) MongoDB extension for Compensations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2339: ---------------------------------- Description: Investigate the feasibility of MongoDB compensations patent implementation. > MongoDB extension for Compensations > ----------------------------------- > > Key: JBTM-2339 > URL: https://issues.jboss.org/browse/JBTM-2339 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > > Investigate the feasibility of MongoDB compensations patent implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 2 08:37:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 2 Jan 2017 08:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2339) MongoDB extension for Compensations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13342249#comment-13342249 ] Gytis Trikleris commented on JBTM-2339: --------------------------------------- I've looked into this issue a while back, but it didn't go far because compensations framework update was necessary. It should be possible to get back to the issue now, because now it is possible to register compensation/confirmation handers by instance rather than by class name. It allows having specific database information in the object instance. In addition, a wider conversation on possible API changes might be needed. > MongoDB extension for Compensations > ----------------------------------- > > Key: JBTM-2339 > URL: https://issues.jboss.org/browse/JBTM-2339 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > > Investigate the feasibility of MongoDB compensations patent implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 3 06:32:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 3 Jan 2017 06:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2833) Move deprecated tooling classes into an internal package In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2833: -------------------------------------- Summary: Move deprecated tooling classes into an internal package Key: JBTM-2833 URL: https://issues.jboss.org/browse/JBTM-2833 Project: JBoss Transaction Manager Issue Type: Task Components: Tooling Affects Versions: 5.5.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next commit 66a9291f56f (JBTM-2308]) "Mark classes deprecated since we need to rejig package names" marked many/most of the tooling instrumentation classes deprecated - these need to be moved to internal packages and the then marked as not deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 9 04:39:00 2017 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Mon, 9 Jan 2017 04:39:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS In-Reply-To: References: Message-ID: Daniel Simko created JBTM-2834: ---------------------------------- Summary: Delete a tx participant - XAResource#forget(xid) is not called for JTS Key: JBTM-2834 URL: https://issues.jboss.org/browse/JBTM-2834 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Daniel Simko Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 9 04:39:00 2017 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Mon, 9 Jan 2017 04:39:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Simko updated JBTM-2834: ------------------------------- Affects Version/s: 5.5.0.Final > Delete a tx participant - XAResource#forget(xid) is not called for JTS > ---------------------------------------------------------------------- > > Key: JBTM-2834 > URL: https://issues.jboss.org/browse/JBTM-2834 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > > Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 9 06:00:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 9 Jan 2017 06:00:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka reassigned JBTM-2834: ------------------------------------- Assignee: Michael Musgrove > Delete a tx participant - XAResource#forget(xid) is not called for JTS > ---------------------------------------------------------------------- > > Key: JBTM-2834 > URL: https://issues.jboss.org/browse/JBTM-2834 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Michael Musgrove > > Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 04:57:02 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 11 Jan 2017 04:57:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2822) Add suppressed exceptions for failures during prepare In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13345966#comment-13345966 ] Ondra Chaloupka commented on JBTM-2822: --------------------------------------- Hi [~tomjenkinson], during the check ups JBEAP issues I got to this issue and when applying the same test as I have for JBTM-2636 I found out that there is a branch in code where deffered exception is not added - that's when heuristic happens. Is it intentional? This kind of update fixes the issue that I refer to: https://github.com/ochaloup/narayana/commit/cb2ab4252a6c2e1106751d28103daefea42e86f6 > Add suppressed exceptions for failures during prepare > ----------------------------------------------------- > > Key: JBTM-2822 > URL: https://issues.jboss.org/browse/JBTM-2822 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > JBTM-2636 added support for adding suppressed exceptions for issues reported during commit. It would be useful to do the same for prepare exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 05:59:00 2017 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Wed, 11 Jan 2017 05:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start In-Reply-To: References: Message-ID: Daniel Simko created JBTM-2835: ---------------------------------- Summary: NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start Key: JBTM-2835 URL: https://issues.jboss.org/browse/JBTM-2835 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Common Affects Versions: 5.5.0.Final Reporter: Daniel Simko Priority: Minor 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) 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.NullPointerException at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.(CommitMarkableResourceRecordRecoveryModule.java:156) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.(PeriodicRecovery.java:121) at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.(RecoveryManagerImple.java:107) at com.arjuna.ats.arjuna.recovery.RecoveryManager.(RecoveryManager.java:477) at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 06:03:00 2017 From: issues at jboss.org (Anonymous (JIRA)) Date: Wed, 11 Jan 2017 06:03:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Dan Simko created pull request #1117 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start > ----------------------------------------------------------------------------------------- > > Key: JBTM-2835 > URL: https://issues.jboss.org/browse/JBTM-2835 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Priority: Minor > > 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.(CommitMarkableResourceRecordRecoveryModule.java:156) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) > at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.(PeriodicRecovery.java:121) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.(RecoveryManagerImple.java:107) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.(RecoveryManager.java:477) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) > ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 06:13:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 11 Jan 2017 06:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13346055#comment-13346055 ] Tom Jenkinson commented on JBTM-2835: ------------------------------------- What does the error look like with your patch? What is the effect of the NPE? > NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start > ----------------------------------------------------------------------------------------- > > Key: JBTM-2835 > URL: https://issues.jboss.org/browse/JBTM-2835 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Priority: Minor > > 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.(CommitMarkableResourceRecordRecoveryModule.java:156) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) > at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.(PeriodicRecovery.java:121) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.(RecoveryManagerImple.java:107) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.(RecoveryManager.java:477) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) > ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 06:15:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 11 Jan 2017 06:15:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2822) Add suppressed exceptions for failures during prepare In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13346059#comment-13346059 ] Tom Jenkinson commented on JBTM-2822: ------------------------------------- Sorry Ondra - I don't quite follow. Which branch does not have this commit in? > Add suppressed exceptions for failures during prepare > ----------------------------------------------------- > > Key: JBTM-2822 > URL: https://issues.jboss.org/browse/JBTM-2822 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > JBTM-2636 added support for adding suppressed exceptions for issues reported during commit. It would be useful to do the same for prepare exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 06:54:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 11 Jan 2017 06:54:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2822) Add suppressed exceptions for failures during prepare In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13346088#comment-13346088 ] Ondra Chaloupka commented on JBTM-2822: --------------------------------------- Sorry [~tomjenkinson], wrong wording. I mean `if branch` in `doPrepare` method that refers about heuristics which happened. I think there is missing handling of suppressed exception - it's not added to exception which will be thrown. My change could adjust it https://github.com/ochaloup/narayana/commit/cb2ab4252a6c2e1106751d28103daefea42e86f6 > Add suppressed exceptions for failures during prepare > ----------------------------------------------------- > > Key: JBTM-2822 > URL: https://issues.jboss.org/browse/JBTM-2822 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > JBTM-2636 added support for adding suppressed exceptions for issues reported during commit. It would be useful to do the same for prepare exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 06:57:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 11 Jan 2017 06:57:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2822) Add suppressed exceptions for failures during prepare In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13346091#comment-13346091 ] Tom Jenkinson commented on JBTM-2822: ------------------------------------- Ah yes, that sounds useful. Perhaps you can add a unit test to ExceptionDeferrerTests and we can look to merge it? This is the type of test to add: https://github.com/jbosstm/narayana/pull/1116/files I think you should raise a new issue though because it will be confusing to track the change against the resolved one. > Add suppressed exceptions for failures during prepare > ----------------------------------------------------- > > Key: JBTM-2822 > URL: https://issues.jboss.org/browse/JBTM-2822 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > JBTM-2636 added support for adding suppressed exceptions for issues reported during commit. It would be useful to do the same for prepare exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 07:00:01 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 11 Jan 2017 07:00:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2822) Add suppressed exceptions for failures during prepare In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13346094#comment-13346094 ] Ondra Chaloupka commented on JBTM-2822: --------------------------------------- Ok, I see. I will do so. > Add suppressed exceptions for failures during prepare > ----------------------------------------------------- > > Key: JBTM-2822 > URL: https://issues.jboss.org/browse/JBTM-2822 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > JBTM-2636 added support for adding suppressed exceptions for issues reported during commit. It would be useful to do the same for prepare exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 09:59:01 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 11 Jan 2017 09:59:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2836) Add suppressed exceptions for failures during prepare for XA spec non-compliant cases In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-2836: ------------------------------------- Summary: Add suppressed exceptions for failures during prepare for XA spec non-compliant cases Key: JBTM-2836 URL: https://issues.jboss.org/browse/JBTM-2836 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Transaction Core Affects Versions: 5.5.0.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor There was a request for include causing exceptions to list of suppressed ones when an error happens during 2PC prepare call. That was fixed by JBTM-2822. The fix left aside a branch of code under {{doPrepare}} method which handles cases when {{XAResourceRecord#topLevelPrepare}} ends in situation which is not compliant with XA specification (https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAResourceRecord.java#L280) Then there is taken code to https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/BasicAction.java#L2742 This enhancement follows the fix JBTM-2822 and saves deferred exception at that case as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 10:11:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 11 Jan 2017 10:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2836) Add suppressed exceptions for failures during prepare for XA spec non-compliant cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1118 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Add suppressed exceptions for failures during prepare for XA spec non-compliant cases > ------------------------------------------------------------------------------------- > > Key: JBTM-2836 > URL: https://issues.jboss.org/browse/JBTM-2836 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > There was a request for include causing exceptions to list of suppressed ones when an error happens during 2PC prepare call. That was fixed by JBTM-2822. > The fix left aside a branch of code under {{doPrepare}} method which handles cases when {{XAResourceRecord#topLevelPrepare}} ends in situation which is not compliant with XA specification (https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAResourceRecord.java#L280) > Then there is taken code to > https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/BasicAction.java#L2742 > This enhancement follows the fix JBTM-2822 and saves deferred exception at that case as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 11:00:00 2017 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Wed, 11 Jan 2017 11:00:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Simko updated JBTM-2835: ------------------------------- Attachment: before_patch.log > NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start > ----------------------------------------------------------------------------------------- > > Key: JBTM-2835 > URL: https://issues.jboss.org/browse/JBTM-2835 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Priority: Minor > Attachments: after_patch.log, before_patch.log > > > 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.(CommitMarkableResourceRecordRecoveryModule.java:156) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) > at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.(PeriodicRecovery.java:121) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.(RecoveryManagerImple.java:107) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.(RecoveryManager.java:477) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) > ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 11:00:03 2017 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Wed, 11 Jan 2017 11:00:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Simko updated JBTM-2835: ------------------------------- Attachment: after_patch.log > NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start > ----------------------------------------------------------------------------------------- > > Key: JBTM-2835 > URL: https://issues.jboss.org/browse/JBTM-2835 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Priority: Minor > Attachments: after_patch.log, before_patch.log > > > 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.(CommitMarkableResourceRecordRecoveryModule.java:156) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) > at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.(PeriodicRecovery.java:121) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.(RecoveryManagerImple.java:107) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.(RecoveryManager.java:477) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) > ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 11 11:01:00 2017 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Wed, 11 Jan 2017 11:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13346647#comment-13346647 ] Daniel Simko commented on JBTM-2835: ------------------------------------ I forgot to mention that jdbc object store is also needed to reproduce this. I have uploaded logs "before_patch.log" and "after_patch.log". IMHO the log after patch looks better because NPE is caught earlier and user gets better info about what happened - "ARJUNA012135: Could not create Store type: com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore". But the result is same in both cases - server won't start. > NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start > ----------------------------------------------------------------------------------------- > > Key: JBTM-2835 > URL: https://issues.jboss.org/browse/JBTM-2835 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Priority: Minor > Attachments: after_patch.log, before_patch.log > > > 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.(CommitMarkableResourceRecordRecoveryModule.java:156) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) > at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.(PeriodicRecovery.java:121) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.(RecoveryManagerImple.java:107) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.(RecoveryManager.java:477) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) > ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 12 07:42:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 12 Jan 2017 07:42:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-2837: ------------------------------------- Summary: Server being stuck during shudown when transaction probe op is called Key: JBTM-2837 URL: https://issues.jboss.org/browse/JBTM-2837 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Ondra Chaloupka I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. >From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 Now when shutdown of container is being run (you can check attached {{server.log}}) the periodic recovery is stopped and the {{scanState}} is left as it is. At that point call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. [1] {code} Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) owns: XARecoveryModule (id=219) owns: AtomicAction (id=844) owns: ObjStoreBrowser (id=845) XARecoveryModule.periodicWorkFirstPass() line: 149 XARecoveryModule.getNewXAResource(Xid) line: 272 XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 XAResourceRecord.getNewXAResource() line: 1303 XAResourceRecord.restore_state(InputObjectState, int) line: 1054 AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 AtomicAction(BasicAction).activate(String) line: 488 AtomicAction(BasicAction).activate() line: 451 ActionBean$GenericAtomicActionWrapper.activate() line: 391 ActionBean.createWrapper(UidWrapper, boolean) line: 107 ActionBean.(UidWrapper) line: 93 NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 Constructor.newInstance(Object...) line: 423 UidWrapper.createMBean() line: 196 ObjStoreBrowser.createBean(Uid, String) line: 481 ObjStoreBrowser.probe() line: 435 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 Method.invoke(Object, Object...) line: 498 Trampoline.invoke(Method, Object, Object[]) line: 71 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 Method.invoke(Object, Object...) line: 498 MethodUtil.invoke(Method, Object, Object[]) line: 275 StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 OperationContextImpl(AbstractOperationContext).processStages() line: 664 OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 OperationContextImpl.executeOperation() line: 1390 ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 277244299.run() line: not available SecurityIdentity.runAs(PrivilegedAction) line: 193 ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 ManagementRequestContextImpl$1.doExecute() line: 70 ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 ThreadPoolExecutor$Worker.run() line: 617 JBossThread(Thread).run() line: 745 JBossThread.run() line: 320 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 12 07:43:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 12 Jan 2017 07:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2837: ---------------------------------- Affects Version/s: 5.5.0.Final > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 12 07:43:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 12 Jan 2017 07:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka reassigned JBTM-2837: ------------------------------------- Assignee: Tom Jenkinson > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 12 07:43:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 12 Jan 2017 07:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2837: ---------------------------------- Component/s: Recovery > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 12 07:44:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 12 Jan 2017 07:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2837: ---------------------------------- Attachment: server.log stacktrace1.log > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 12 08:07:00 2017 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Thu, 12 Jan 2017 08:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2835) NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Simko closed JBTM-2835. ------------------------------ Resolution: Rejected > NPE when CommitMarkableResourceRecordRecoveryModule cannot connect DB during server start > ----------------------------------------------------------------------------------------- > > Key: JBTM-2835 > URL: https://issues.jboss.org/browse/JBTM-2835 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Priority: Minor > Attachments: after_patch.log, before_patch.log > > > 12:49:24,796 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) > at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.(CommitMarkableResourceRecordRecoveryModule.java:156) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192) > at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.(PeriodicRecovery.java:121) > at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.(RecoveryManagerImple.java:107) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.(RecoveryManager.java:477) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132) > at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112) > at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54) > at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:124) > ... 5 more -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 13 06:13:00 2017 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Fri, 13 Jan 2017 06:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2838) Please give back IPv6 profile for raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: Daniel Simko created JBTM-2838: ---------------------------------- Summary: Please give back IPv6 profile for raw-xts-api-demo quickstart Key: JBTM-2838 URL: https://issues.jboss.org/browse/JBTM-2838 Project: JBoss Transaction Manager Issue Type: Enhancement Components: XTS Affects Versions: 5.5.0.Final Reporter: Daniel Simko Assignee: Gytis Trikleris Priority: Minor This profile was removed by https://github.com/jbosstm/quickstart/commit/033d521bc78d80cedb36d1d085635edea6df303f#diff-150d8375c28d69d9eb53270d79389a41L275 and our IPv6 tests are failing because of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 13 08:12:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 13 Jan 2017 08:12:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2636) Backport deferred exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13347924#comment-13347924 ] Tom Jenkinson commented on JBTM-2636: ------------------------------------- only applies to invocations in made in the same JVM - if you need to pass this back to callers you need to get EJB remoting changes. It is not possible to do with JTS because CosTransactions.idl does not allow the reporting > Backport deferred exceptions > ---------------------------- > > Key: JBTM-2636 > URL: https://issues.jboss.org/browse/JBTM-2636 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.32 > > > Includes > * JBTM-2120 > * https://github.com/jbosstm/narayana/pull/598/commits -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 13 08:46:01 2017 From: issues at jboss.org (David Lloyd (JIRA)) Date: Fri, 13 Jan 2017 08:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2839) Add ability to retrieve suppressed exceptions from org.jboss.tm.ImportedTransaction In-Reply-To: References: Message-ID: David Lloyd created JBTM-2839: --------------------------------- Summary: Add ability to retrieve suppressed exceptions from org.jboss.tm.ImportedTransaction Key: JBTM-2839 URL: https://issues.jboss.org/browse/JBTM-2839 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Application Server Integration Reporter: David Lloyd Assignee: Amos Feng In order to propagate complete failure information from subordinate to parent, we need a method on {{org.jboss.tm.ImportedTransaction}} which allows us to get the suppressed exceptions which occurred as a result of doPrepare and possibly also doOnePhaseCommit so we can attach the cause to the message returned to the master. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 16 07:01:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 16 Jan 2017 07:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2837: ---------------------------------- Steps to Reproduce: I'm able to reproduce it when running whole crash recovery testcase {{JPAProxyCrashRecoveryTestCase}} which contains several test scenarios and normally one of them hit it. Each test scenario run about 3 min and getting it could be a little bit timeconsuming {code} git clone http://git.app.eng.bos.redhat.com/git/jbossqe-eap-tests-transactions.gitexport JBOSS_HOME=... (downloadable at http://download.eng.brq.redhat.com/devel/candidates/JBEAP/) DS_PROPS="-Dds0.db=postgresql -Dds0.jdbc.driver.url=http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.1.0/postgresql94/jdbc4/postgresql-9.4.1209.jar -Dds0.jdbc.xa-class=org.postgresql.xa.PGXADataSource -Dds0.jdbc.url=jdbc:postgresql://gen-vm006.mw.lab.eng.bos.redhat.com:5432/crashrec -Dds0.db.name=crashrec -Dds0.user=crashrec -Dds0.pass=crashrec -Dds0.jdbc.driver.jar=postgresql-driver.jar" mvn clean verify -am -pl jbossts -DfailIfNoTests=false -fn -Djbossts.noJTS $DS_PROPS -Dtest=JPAProxyCrashRecoveryTestCase {code} was: I'm able to reproduce it when running whole crash recovery testcase {{JPAProxyCrashRecoveryTestCase}} which contains several test scenarios and normally one of them hit it. Each test scenario run about 3 min and getting it could be a little bit timeconsuming {code} git clone http://git.app.eng.bos.redhat.com/git/jbossqe-eap-tests-transactions.gitexport JBOSS_HOME=... (downloadable at http://download.eng.brq.redhat.com/devel/candidates/JBEAP/) DS_PROPS="-Dds0.db=oracle -Dds0.jdbc.driver.url=http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.1.0/postgresql94/jdbc4/postgresql-9.4.1209.jar -Dds0.jdbc.xa-class=org.postgresql.xa.PGXADataSource -Dds0.jdbc.url=jdbc:postgresql://gen-vm006.mw.lab.eng.bos.redhat.com:5432/crashrec -Dds0.db.name=crashrec -Dds0.user=crashrec -Dds0.pass=crashrec -Dds0.jdbc.driver.jar=postgresql-driver.jar" mvn clean verify -am -pl jbossts -DfailIfNoTests=false -fn -Djbossts.noJTS $DS_PROPS -Dtest=JPAProxyCrashRecoveryTestCase {code} > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 16 08:13:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 16 Jan 2017 08:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reassigned JBTM-2837: -------------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 16 08:36:01 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 16 Jan 2017 08:36:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13348642#comment-13348642 ] Michael Musgrove commented on JBTM-2837: ---------------------------------------- Thanks for the thorough analysis [~ochaloup] As ondrej has discovered after periodicWorkFirstPass if periodic recovery has been asked to terminate we skip periodicWorkSecondPass so we do not get the opportunity to update the XARecoveryModule#scanState. There are two alternative fixes: # notify each recovery module that periodic recovery has finished (and therefore periodicWorkSecondPass will not be called); # if periodicWorkFirstPass has been called then always call periodicWorkSecondPass and only then check to see whether periodic recovery has finished My preference is option 2) (the only drawback is that it will delay shutdown). Ideally we would call it immediately and also pass an argument to periodicWorkSecondPass indicating the operating mode of scanning process (https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/recovery/PeriodicRecovery.java#L90) which recovery modules would use to optimise the second pass. This is an interface change so we would need to use java 8 default methods feature ( https://docs.oracle.com/javase/tutorial/java/IandI/defaultmethods.html) so we should do that in the next major release. If nobody has any objections I will implement option 2) > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 16 08:45:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 16 Jan 2017 08:45:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13348651#comment-13348651 ] Tom Jenkinson commented on JBTM-2837: ------------------------------------- Regarding option 2, unless necessary we should avoid upgrading to Narayana 6 in EAP 7.1 just to resolve this issue. What would happen if we called periodicWorkSecondPass during shutdown with the normal interface (rather than the new interface)? > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 16 11:30:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 16 Jan 2017 11:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2840) Add new suppressed exception test In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2840: ----------------------------------- Summary: Add new suppressed exception test Key: JBTM-2840 URL: https://issues.jboss.org/browse/JBTM-2840 Project: JBoss Transaction Manager Issue Type: Task Reporter: Tom Jenkinson Priority: Minor Show that initCause messages in the XAException can be read and show how integration code could access them. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 16 11:31:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 16 Jan 2017 11:31:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2840) Add new suppressed exception test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2840: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1116 > Add new suppressed exception test > --------------------------------- > > Key: JBTM-2840 > URL: https://issues.jboss.org/browse/JBTM-2840 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Show that initCause messages in the XAException can be read and show how integration code could access them. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 16 11:31:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 16 Jan 2017 11:31:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2840) Add new suppressed exception test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2840: ----------------------------------- Assignee: Tom Jenkinson > Add new suppressed exception test > --------------------------------- > > Key: JBTM-2840 > URL: https://issues.jboss.org/browse/JBTM-2840 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Show that initCause messages in the XAException can be read and show how integration code could access them. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 16 11:31:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 16 Jan 2017 11:31:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2840) Add new suppressed exception test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2840: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add new suppressed exception test > --------------------------------- > > Key: JBTM-2840 > URL: https://issues.jboss.org/browse/JBTM-2840 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > > Show that initCause messages in the XAException can be read and show how integration code could access them. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 16 11:31:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 16 Jan 2017 11:31:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2840) Add new suppressed exception test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2840: -------------------------------- Fix Version/s: 5.next > Add new suppressed exception test > --------------------------------- > > Key: JBTM-2840 > URL: https://issues.jboss.org/browse/JBTM-2840 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Show that initCause messages in the XAException can be read and show how integration code could access them. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 07:42:00 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 Jan 2017 07:42:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2575) When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349468#comment-13349468 ] RH Bugzilla Integration commented on JBTM-2575: ----------------------------------------------- Petr Penicka changed the Status of [bug 1289386|https://bugzilla.redhat.com/show_bug.cgi?id=1289386] from VERIFIED to CLOSED > When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2575 > URL: https://issues.jboss.org/browse/JBTM-2575 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.31, 5.2.9.Final > > > There is a check in the subordinate orphan detection that not only checks for matching gtrid but also for matching subordinate name. This will not match correctly for an intermediary node. E.g. > a->b b->c > When b scans c the xid it gets back will have subordinate name of c, b will look in its object store and match the subordinate on gtrid but the subordinate node ID in b subordinateatomicaction will be "b". > This check is actually superfluous anyway. We already know that the Xid returned from c was for b because of transport level checks. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 07:59:01 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 Jan 2017 07:59:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349492#comment-13349492 ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Petr Penicka changed the Status of [bug 1329142|https://bugzilla.redhat.com/show_bug.cgi?id=1329142] from VERIFIED to CLOSED > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 08:00:03 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 Jan 2017 08:00:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349512#comment-13349512 ] RH Bugzilla Integration commented on JBTM-2583: ----------------------------------------------- Petr Penicka changed the Status of [bug 1310603|https://bugzilla.redhat.com/show_bug.cgi?id=1310603] from VERIFIED to CLOSED > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.34, 5.2.17.Final, 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 08:02:00 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 Jan 2017 08:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2550) If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349519#comment-13349519 ] RH Bugzilla Integration commented on JBTM-2550: ----------------------------------------------- Petr Penicka changed the Status of [bug 1333245|https://bugzilla.redhat.com/show_bug.cgi?id=1333245] from VERIFIED to CLOSED > If a class cannot be deserialized safely, try to fallback and use the XARecoveryModule to locate an appropriate XAResource > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Affects Versions: 5.2.8.Final > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.33, 5.2.10.Final > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR > We can catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 08:15:01 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 Jan 2017 08:15:01 -0500 (EST) 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=13349599#comment-13349599 ] RH Bugzilla Integration commented on JBTM-2500: ----------------------------------------------- Petr Penicka changed the Status of [bug 1238927|https://bugzilla.redhat.com/show_bug.cgi?id=1238927] from VERIFIED to CLOSED > 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 (v7.2.3#72005) From issues at jboss.org Tue Jan 17 08:15:02 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 Jan 2017 08:15:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2708) Test does not close FileInputStream In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349606#comment-13349606 ] RH Bugzilla Integration commented on JBTM-2708: ----------------------------------------------- Petr Penicka changed the Status of [bug 1356589|https://bugzilla.redhat.com/show_bug.cgi?id=1356589] from VERIFIED to CLOSED > Test does not close FileInputStream > ----------------------------------- > > Key: JBTM-2708 > URL: https://issues.jboss.org/browse/JBTM-2708 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.35, 5.3.4.Final > > > {code} > public XARRTestResource(String xarrHelper, File file) throws IOException { > this.xarrHelper = xarrHelper; > this.file = file; > DataInputStream fis = new DataInputStream(new FileInputStream(file)); > final int formatId = fis.readInt(); > final int gtrid_length = fis.readInt(); > final byte[] gtrid = new byte[gtrid_length]; > fis.read(gtrid, 0, gtrid_length); > final int bqual_length = fis.readInt(); > final byte[] bqual = new byte[bqual_length]; > fis.read(bqual, 0, bqual_length); > xids.put(file, new Xid() { > @Override > public byte[] getGlobalTransactionId() { > return gtrid; > } > @Override > public int getFormatId() { > return formatId; > } > @Override > public byte[] getBranchQualifier() { > return bqual; > } > }); > fis.close(); > } > {code} > Spotted while working on JBTM-2614 backport -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 09:22:00 2017 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 17 Jan 2017 09:22:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2841) HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send() In-Reply-To: References: Message-ID: Amos Feng created JBTM-2841: ------------------------------- Summary: HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send() Key: JBTM-2841 URL: https://issues.jboss.org/browse/JBTM-2841 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next tpreturn() seems to non-block send without checking tranfer length. It needs a wrapper of looping apr_socket_send() until all of the data write to the socket. similar like [stomp_write_buffer|https://github.com/jbosstm/narayana/blob/c035f66960d189a5b96d1940c9d251a4e2d7b113/blacktie/hybrid/src/main/cpp/stomp.c] -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 11:50:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Jan 2017 11:50:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349865#comment-13349865 ] Michael Musgrove commented on JBTM-2837: ---------------------------------------- Other than timeliness, I do not foresee any issues with calling periodicWorkSecondPass during shutdown. However, that said, my analysis indicates that this is a test issue - I added a comment on [https://issues.jboss.org/browse/JBEAP-8237|http://example.com] explaining my rationale. > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 12:46:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Jan 2017 12:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349917#comment-13349917 ] Michael Musgrove commented on JBTM-2837: ---------------------------------------- I have been unable to reproduce the issue on my laptop but code analysis does show: # the hang is possible; # the linked jira contains a stacktrace that shows removeXAResourceRecoveryHelper waiting for the scanState to change to IDLE So, I will go ahead and apply the fix mentioned above > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 12:46:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Jan 2017 12:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349917#comment-13349917 ] Michael Musgrove edited comment on JBTM-2837 at 1/17/17 12:45 PM: ------------------------------------------------------------------ I have been unable to reproduce the issue on my laptop but code analysis does show: # the hang is possible; # the linked jira contains a stacktrace that shows removeXAResourceRecoveryHelper waiting for the scanState to change to IDLE So, I will go ahead and apply the fix mentioned above was (Author: mmusgrov): I have been unable to reproduce the issue on my laptop but code analysis does show: # the hang is possible; # the linked jira contains a stacktrace that shows removeXAResourceRecoveryHelper waiting for the scanState to change to IDLE So, I will go ahead and apply the fix mentioned above > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 13:17:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 17 Jan 2017 13:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1119 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 13:32:00 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 Jan 2017 13:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2709) ObjectStoreBrowser cannot cope with JDBC store on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349953#comment-13349953 ] RH Bugzilla Integration commented on JBTM-2709: ----------------------------------------------- Petr Penicka changed the Status of [bug 1356589|https://bugzilla.redhat.com/show_bug.cgi?id=1356589] from VERIFIED to CLOSED > ObjectStoreBrowser cannot cope with JDBC store on Windows > --------------------------------------------------------- > > Key: JBTM-2709 > URL: https://issues.jboss.org/browse/JBTM-2709 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.35, 5.3.4.Final > > > While testing backport of JBTM-2614 I came across the ObjStoreBrowser test. This was failing on Windows. On looking into it I saw it was because the Browser map swaps the "/" in the type name to the system file separator path. This is likely because of the file system store. I have a fix that puts the entry in both ways but it will likely need some more work so providing as an example. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 17 21:32:00 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 17 Jan 2017 21:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13350069#comment-13350069 ] RH Bugzilla Integration commented on JBTM-2614: ----------------------------------------------- Petr Penicka changed the Status of [bug 1356589|https://bugzilla.redhat.com/show_bug.cgi?id=1356589] from VERIFIED to CLOSED > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.35, 5.2.13.Final > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 06:14:00 2017 From: issues at jboss.org (Romain Pelisse (JIRA)) Date: Wed, 18 Jan 2017 06:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2842) missing jboss logging internationalization In-Reply-To: References: Message-ID: Romain Pelisse created JBTM-2842: ------------------------------------ Summary: missing jboss logging internationalization Key: JBTM-2842 URL: https://issues.jboss.org/browse/JBTM-2842 Project: JBoss Transaction Manager Issue Type: Enhancement Components: XTS Affects Versions: 5.5.0.Final Reporter: Romain Pelisse Assignee: Romain Pelisse Priority: Minor There is one log warning message which is not properly internationalized in Wildfly 'xts' submodule: ./src/xts/src/main/java/org/jboss/as/xts/GracefulShutdownRejectionRule.java:45: XTSLogger.logger.warnf("rejecting call because it is not part of any XTS transaction") All logs of level WARN and higher should be internationalized. The message above needs to be added to be added to the following file: ./XTS/sar/src/org/jboss/jbossts/xts/logging/xtsI18NLogger.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 06:14:00 2017 From: issues at jboss.org (Romain Pelisse (JIRA)) Date: Wed, 18 Jan 2017 06:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2826) JBoss Transactions SPI is missing TwoPhaseOutcome constants In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2826 started by Romain Pelisse. -------------------------------------------- > JBoss Transactions SPI is missing TwoPhaseOutcome constants > ----------------------------------------------------------- > > Key: JBTM-2826 > URL: https://issues.jboss.org/browse/JBTM-2826 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: David Lloyd > Assignee: Romain Pelisse > Priority: Minor > > The jboss-transaction-spi allows applications to be decoupled from Narayana's implementation details, however the {{ImportedTransaction#doPrepare}} method returns an integer that is defined by constants in a class inside of {{com.arjuna.ats.arjuna.coordinator}}. These constants should be copied into the SPI. > The workaround is to copy the constant values. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 06:16:00 2017 From: issues at jboss.org (Romain Pelisse (JIRA)) Date: Wed, 18 Jan 2017 06:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2826) JBoss Transactions SPI is missing TwoPhaseOutcome constants In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Pelisse reassigned JBTM-2826: ------------------------------------ Assignee: David Lloyd (was: Romain Pelisse) > JBoss Transactions SPI is missing TwoPhaseOutcome constants > ----------------------------------------------------------- > > Key: JBTM-2826 > URL: https://issues.jboss.org/browse/JBTM-2826 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Minor > > The jboss-transaction-spi allows applications to be decoupled from Narayana's implementation details, however the {{ImportedTransaction#doPrepare}} method returns an integer that is defined by constants in a class inside of {{com.arjuna.ats.arjuna.coordinator}}. These constants should be copied into the SPI. > The workaround is to copy the constant values. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 06:20:00 2017 From: issues at jboss.org (Romain Pelisse (JIRA)) Date: Wed, 18 Jan 2017 06:20:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2842) missing jboss logging internationalization In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2842 started by Romain Pelisse. -------------------------------------------- > missing jboss logging internationalization > ------------------------------------------ > > Key: JBTM-2842 > URL: https://issues.jboss.org/browse/JBTM-2842 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > > There is one log warning message which is not properly internationalized in Wildfly 'xts' submodule: > ./src/xts/src/main/java/org/jboss/as/xts/GracefulShutdownRejectionRule.java:45: XTSLogger.logger.warnf("rejecting call because it is not part of any XTS transaction") > All logs of level WARN and higher should be internationalized. > The message above needs to be added to be added to the following file: > ./XTS/sar/src/org/jboss/jbossts/xts/logging/xtsI18NLogger.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 06:21:00 2017 From: issues at jboss.org (Romain Pelisse (JIRA)) Date: Wed, 18 Jan 2017 06:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2842) missing a jboss logging internationalization In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Pelisse updated JBTM-2842: --------------------------------- Summary: missing a jboss logging internationalization (was: missing jboss logging internationalization) > missing a jboss logging internationalization > -------------------------------------------- > > Key: JBTM-2842 > URL: https://issues.jboss.org/browse/JBTM-2842 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > > There is one log warning message which is not properly internationalized in Wildfly 'xts' submodule: > ./src/xts/src/main/java/org/jboss/as/xts/GracefulShutdownRejectionRule.java:45: XTSLogger.logger.warnf("rejecting call because it is not part of any XTS transaction") > All logs of level WARN and higher should be internationalized. > The message above needs to be added to be added to the following file: > ./XTS/sar/src/org/jboss/jbossts/xts/logging/xtsI18NLogger.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 06:25:00 2017 From: issues at jboss.org (Anonymous (JIRA)) Date: Wed, 18 Jan 2017 06:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2842) missing a jboss logging internationalization In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Pelisse Romain created pull request #1120 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > missing a jboss logging internationalization > -------------------------------------------- > > Key: JBTM-2842 > URL: https://issues.jboss.org/browse/JBTM-2842 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > > There is one log warning message which is not properly internationalized in Wildfly 'xts' submodule: > ./src/xts/src/main/java/org/jboss/as/xts/GracefulShutdownRejectionRule.java:45: XTSLogger.logger.warnf("rejecting call because it is not part of any XTS transaction") > All logs of level WARN and higher should be internationalized. > The message above needs to be added to be added to the following file: > ./XTS/sar/src/org/jboss/jbossts/xts/logging/xtsI18NLogger.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 06:26:00 2017 From: issues at jboss.org (Romain Pelisse (JIRA)) Date: Wed, 18 Jan 2017 06:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2842) missing a jboss logging internationalization In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Pelisse updated JBTM-2842: --------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1120 > missing a jboss logging internationalization > -------------------------------------------- > > Key: JBTM-2842 > URL: https://issues.jboss.org/browse/JBTM-2842 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > > There is one log warning message which is not properly internationalized in Wildfly 'xts' submodule: > ./src/xts/src/main/java/org/jboss/as/xts/GracefulShutdownRejectionRule.java:45: XTSLogger.logger.warnf("rejecting call because it is not part of any XTS transaction") > All logs of level WARN and higher should be internationalized. > The message above needs to be added to be added to the following file: > ./XTS/sar/src/org/jboss/jbossts/xts/logging/xtsI18NLogger.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 06:57:00 2017 From: issues at jboss.org (Romain Pelisse (JIRA)) Date: Wed, 18 Jan 2017 06:57:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2842) missing a jboss logging internationalization In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Pelisse closed JBTM-2842. -------------------------------- Resolution: Rejected No need to add the message to JBossTS, it can lives only in XTS. > missing a jboss logging internationalization > -------------------------------------------- > > Key: JBTM-2842 > URL: https://issues.jboss.org/browse/JBTM-2842 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > > There is one log warning message which is not properly internationalized in Wildfly 'xts' submodule: > ./src/xts/src/main/java/org/jboss/as/xts/GracefulShutdownRejectionRule.java:45: XTSLogger.logger.warnf("rejecting call because it is not part of any XTS transaction") > All logs of level WARN and higher should be internationalized. > The message above needs to be added to be added to the following file: > ./XTS/sar/src/org/jboss/jbossts/xts/logging/xtsI18NLogger.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 07:08:00 2017 From: issues at jboss.org (David Lloyd (JIRA)) Date: Wed, 18 Jan 2017 07:08:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2826) JBoss Transactions SPI is missing TwoPhaseOutcome constants In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13350336#comment-13350336 ] David Lloyd commented on JBTM-2826: ----------------------------------- Why assign it back to me? > JBoss Transactions SPI is missing TwoPhaseOutcome constants > ----------------------------------------------------------- > > Key: JBTM-2826 > URL: https://issues.jboss.org/browse/JBTM-2826 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Minor > > The jboss-transaction-spi allows applications to be decoupled from Narayana's implementation details, however the {{ImportedTransaction#doPrepare}} method returns an integer that is defined by constants in a class inside of {{com.arjuna.ats.arjuna.coordinator}}. These constants should be copied into the SPI. > The workaround is to copy the constant values. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 08:33:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 Jan 2017 08:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2826) JBoss Transactions SPI is missing TwoPhaseOutcome constants In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13350393#comment-13350393 ] Tom Jenkinson commented on JBTM-2826: ------------------------------------- Not sure, I think [~rpelisse] assigned it? > JBoss Transactions SPI is missing TwoPhaseOutcome constants > ----------------------------------------------------------- > > Key: JBTM-2826 > URL: https://issues.jboss.org/browse/JBTM-2826 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Minor > > The jboss-transaction-spi allows applications to be decoupled from Narayana's implementation details, however the {{ImportedTransaction#doPrepare}} method returns an integer that is defined by constants in a class inside of {{com.arjuna.ats.arjuna.coordinator}}. These constants should be copied into the SPI. > The workaround is to copy the constant values. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 08:33:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 18 Jan 2017 08:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2826) JBoss Transactions SPI is missing TwoPhaseOutcome constants In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2826: ----------------------------------- Assignee: (was: David Lloyd) > JBoss Transactions SPI is missing TwoPhaseOutcome constants > ----------------------------------------------------------- > > Key: JBTM-2826 > URL: https://issues.jboss.org/browse/JBTM-2826 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: David Lloyd > Priority: Minor > > The jboss-transaction-spi allows applications to be decoupled from Narayana's implementation details, however the {{ImportedTransaction#doPrepare}} method returns an integer that is defined by constants in a class inside of {{com.arjuna.ats.arjuna.coordinator}}. These constants should be copied into the SPI. > The workaround is to copy the constant values. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 08:53:00 2017 From: issues at jboss.org (Romain Pelisse (JIRA)) Date: Wed, 18 Jan 2017 08:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2826) JBoss Transactions SPI is missing TwoPhaseOutcome constants In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13350420#comment-13350420 ] Romain Pelisse commented on JBTM-2826: -------------------------------------- Sorry, I never meant to took it in the first place. I created an other issue, click on what thought to be it (but turned out to be this issue). So sorry for the annoyance. > JBoss Transactions SPI is missing TwoPhaseOutcome constants > ----------------------------------------------------------- > > Key: JBTM-2826 > URL: https://issues.jboss.org/browse/JBTM-2826 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: David Lloyd > Priority: Minor > > The jboss-transaction-spi allows applications to be decoupled from Narayana's implementation details, however the {{ImportedTransaction#doPrepare}} method returns an integer that is defined by constants in a class inside of {{com.arjuna.ats.arjuna.coordinator}}. These constants should be copied into the SPI. > The workaround is to copy the constant values. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 18 10:20:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 18 Jan 2017 10:20:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2836) Add suppressed exceptions for failures during prepare for XA spec non-compliant cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2836: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add suppressed exceptions for failures during prepare for XA spec non-compliant cases > ------------------------------------------------------------------------------------- > > Key: JBTM-2836 > URL: https://issues.jboss.org/browse/JBTM-2836 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > There was a request for include causing exceptions to list of suppressed ones when an error happens during 2PC prepare call. That was fixed by JBTM-2822. > The fix left aside a branch of code under {{doPrepare}} method which handles cases when {{XAResourceRecord#topLevelPrepare}} ends in situation which is not compliant with XA specification (https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAResourceRecord.java#L280) > Then there is taken code to > https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/BasicAction.java#L2742 > This enhancement follows the fix JBTM-2822 and saves deferred exception at that case as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 19 05:35:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 19 Jan 2017 05:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1121 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Delete a tx participant - XAResource#forget(xid) is not called for JTS > ---------------------------------------------------------------------- > > Key: JBTM-2834 > URL: https://issues.jboss.org/browse/JBTM-2834 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Michael Musgrove > > Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 13:29:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 13:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2829) Avoid null pointer exception when comparing JDBC connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2829. ------------------------------- > Avoid null pointer exception when comparing JDBC connections > ------------------------------------------------------------ > > Key: JBTM-2829 > URL: https://issues.jboss.org/browse/JBTM-2829 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.5.1.Final > > > Spring Boot extension for the transactional driver doesn't know database URL and uses provided XADataSource to create connection. However, ConnectionImpl expects URL, username and password to not be null https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/ConnectionManager.java#L91. As a result NullPointerException is thrown if connection is reused. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 13:29:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 13:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2833) Move deprecated tooling classes into an internal package In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2833: -------------------------------- Fix Version/s: 5.next (was: 5.5.1.Final) > Move deprecated tooling classes into an internal package > -------------------------------------------------------- > > Key: JBTM-2833 > URL: https://issues.jboss.org/browse/JBTM-2833 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tooling > Affects Versions: 5.5.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > commit 66a9291f56f (JBTM-2308]) "Mark classes deprecated since we need to rejig package names" marked many/most of the tooling instrumentation classes deprecated - these need to be moved to internal packages and the then marked as not deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 13:29:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 13:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2822) Add suppressed exceptions for failures during prepare In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2822. ------------------------------- > Add suppressed exceptions for failures during prepare > ----------------------------------------------------- > > Key: JBTM-2822 > URL: https://issues.jboss.org/browse/JBTM-2822 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.5.1.Final > > > JBTM-2636 added support for adding suppressed exceptions for issues reported during commit. It would be useful to do the same for prepare exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 13:29:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 13:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2831) Fix RTS inbound bridge participant deserialiser registration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2831: -------------------------------- Fix Version/s: 5.next (was: 5.5.1.Final) > Fix RTS inbound bridge participant deserialiser registration > ------------------------------------------------------------ > > Key: JBTM-2831 > URL: https://issues.jboss.org/browse/JBTM-2831 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Inbound bridge participant deserialiser is registered when InboundBridgeManager is created [1]. That deserialiser is immediately used to recreate participants and update REST-AT coordinator via its HTTP resource. > In WildFly deserialiser registration used to be triggered by creating InboundBridgeManager instance in InboundBridgeService#start method. > However, Undertow subsystem update was introduced which collected and held all HTTP requests until application server completed boot-up. This caused a lock because HTTP call to REST-AT coordinator was being held and InboundBridgeService was waiting for the response. As a result server never completed boot. > Tom has removed that initialisation as a workaround [2]. Everything still works, because inbound bridge recovery manager initialises InboundBridgeManager too. However, only in the second pass. This causes warnings messages during the first cycle of the recovery by REST-AT recovery module. > I'm suggesting to remove deserialiser registration from InboundBridgeManager constructor to keep it as simple as possible and move it to other place were it could be invoked safely and on time e.g. start of first pass of InboundBridgeRecoveryModule. > [1] https://github.com/jbosstm/narayana/blob/5.5.0.Final/rts/at/bridge/src/main/java/org/jboss/narayana/rest/bridge/inbound/InboundBridgeManager.java#L60 > [2] https://github.com/wildfly/wildfly/commit/6bc2e6a20b665201505f12c1c22fda9768a083ea -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 13:29:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 13:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2841) HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2841: -------------------------------- Fix Version/s: 5.next (was: 5.5.1.Final) > HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send() > ------------------------------------------------------------------------- > > Key: JBTM-2841 > URL: https://issues.jboss.org/browse/JBTM-2841 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > tpreturn() seems to non-block send without checking tranfer length. > It needs a wrapper of looping apr_socket_send() until all of the data write to the socket. > similar like [stomp_write_buffer|https://github.com/jbosstm/narayana/blob/c035f66960d189a5b96d1940c9d251a4e2d7b113/blacktie/hybrid/src/main/cpp/stomp.c] -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 13:29:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 13:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2825) JTA XAResourceRecord does not record the type of heuristic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2825. ------------------------------- > JTA XAResourceRecord does not record the type of heuristic > ---------------------------------------------------------- > > Key: JBTM-2825 > URL: https://issues.jboss.org/browse/JBTM-2825 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.5.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.5.1.Final > > > When a JTA XAResource receives a heuristic outcome during commit it does not record the type of heuristic. This information is required by the tooling in order to determine whether it is worthwhile reattempting the commit (for mixed and hazard heuristics it is worthwhile). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 13:29:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 13:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2840) Add new suppressed exception test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2840. ------------------------------- > Add new suppressed exception test > --------------------------------- > > Key: JBTM-2840 > URL: https://issues.jboss.org/browse/JBTM-2840 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.5.1.Final > > > Show that initCause messages in the XAException can be read and show how integration code could access them. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 15:58:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 15:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2834: -------------------------------- Fix Version/s: 5.5.1.Final > Delete a tx participant - XAResource#forget(xid) is not called for JTS > ---------------------------------------------------------------------- > > Key: JBTM-2834 > URL: https://issues.jboss.org/browse/JBTM-2834 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Michael Musgrove > Fix For: 5.5.1.Final > > > Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 15:58:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 15:58:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2834) Delete a tx participant - XAResource#forget(xid) is not called for JTS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2834. ------------------------------- Resolution: Done > Delete a tx participant - XAResource#forget(xid) is not called for JTS > ---------------------------------------------------------------------- > > Key: JBTM-2834 > URL: https://issues.jboss.org/browse/JBTM-2834 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Michael Musgrove > Fix For: 5.5.1.Final > > > Deleting specific participant (introduced by EAP7-594) is not working correctly in DR10. Method forget on a XAResource is not called. It seems to be regression compared to DR9. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 15:58:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 15:58:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2837. ------------------------------- Resolution: Done > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Fix For: 5.5.1.Final > > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 15:58:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 15:58:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2837) Server being stuck during shudown when transaction probe op is called In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2837: -------------------------------- Fix Version/s: 5.5.1.Final > Server being stuck during shudown when transaction probe op is called > --------------------------------------------------------------------- > > Key: JBTM-2837 > URL: https://issues.jboss.org/browse/JBTM-2837 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Fix For: 5.5.1.Final > > Attachments: server.log, stacktrace1.log > > > I do experience server to be stuck (in intermittent way) during shutdown. I need to use afterwards {{kill -9}} to stop it. > From my investigation it seems that it's caused by fact that {{jboss-cli}} operation {{:probe}} does cause {{XARecoveryModule.periodicWorkFirstPass}} being called > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L272 > That way {{scanState}} is left at value ScanStates.BETWEEN_PASSES [1] > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L195 > Now when shutdown of container is being run (you can check attached {{server.log}}) > the periodic recovery is stopped and the {{scanState}} is left as it is. At that point > call of {{XARecoveryModule#removeXAResourceRecoveryHelper}} causes thread waits for state {{IDLE}} ifinintely. https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L110 > You can consult thread dump from time when server gets stuck {{stacktrace1.log}}. > [1] > {code} > Thread [management-handler-thread - 5] (Suspended (breakpoint at line 149 in XARecoveryModule)) > owns: XARecoveryModule (id=219) > owns: AtomicAction (id=844) > owns: ObjStoreBrowser (id=845) > XARecoveryModule.periodicWorkFirstPass() line: 149 > XARecoveryModule.getNewXAResource(Xid) line: 272 > XARecoveryModule.getNewXAResource(XAResourceRecord) line: 310 > XAResourceRecord.getNewXAResource() line: 1303 > XAResourceRecord.restore_state(InputObjectState, int) line: 1054 > AtomicAction(BasicAction).restore_state(InputObjectState, int) line: 1180 > AtomicAction(BasicAction).activate(String) line: 488 > AtomicAction(BasicAction).activate() line: 451 > ActionBean$GenericAtomicActionWrapper.activate() line: 391 > ActionBean.createWrapper(UidWrapper, boolean) line: 107 > ActionBean.(UidWrapper) line: 93 > NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line: not available [native method] > NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 > DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 > Constructor.newInstance(Object...) line: 423 > UidWrapper.createMBean() line: 196 > ObjStoreBrowser.createBean(Uid, String) line: 481 > ObjStoreBrowser.probe() line: 435 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > Trampoline.invoke(Method, Object, Object[]) line: 71 > NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] > NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62 > DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43 > Method.invoke(Object, Object...) line: 498 > MethodUtil.invoke(Method, Object, Object[]) line: 275 > StandardMBeanIntrospector.invokeM2(Method, Object, Object[], Object) line: 112 > StandardMBeanIntrospector.invokeM2(Object, Object, Object[], Object) line: 46 > StandardMBeanIntrospector(MBeanIntrospector).invokeM(M, Object, Object[], Object) line: 237 > PerInterface.invoke(Object, String, Object[], String[], Object) line: 138 > StandardMBeanSupport(MBeanSupport).invoke(String, Object[], String[]) line: 252 > DefaultMBeanServerInterceptor.invoke(ObjectName, String, Object[], String[]) line: 819 > JmxMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 801 > PluggableMBeanServerImpl$TcclMBeanServer.invoke(ObjectName, String, Object[], String[]) line: 1512 > PluggableMBeanServerImpl.invoke(ObjectName, String, Object[], String[]) line: 731 > LogStoreProbeHandler.probeTransactions(MBeanServer, boolean) line: 157 > LogStoreProbeHandler.execute(OperationContext, ModelNode) line: 186 > OperationContextImpl(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 921 > OperationContextImpl(AbstractOperationContext).processStages() line: 664 > OperationContextImpl(AbstractOperationContext).executeOperation() line: 383 > OperationContextImpl.executeOperation() line: 1390 > ModelControllerImpl.internalExecute(ModelNode, OperationMessageHandler, ModelController$OperationTransactionControl, OperationAttachments, OperationStepHandler, boolean, boolean) line: 419 > ModelControllerImpl.lambda$execute$1(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > 277244299.run() line: not available > SecurityIdentity.runAs(PrivilegedAction) line: 193 > ModelControllerImpl.execute(Operation, OperationMessageHandler, ModelController$OperationTransactionControl) line: 240 > ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelNode, int, ManagementRequestContext, CompletedCallback) line: 217 > ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler$ExecuteRequestHandler, ModelNode, int, ManagementRequestContext, ModelControllerClientOperationHandler$CompletedCallback) line: 137 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 161 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run() line: 157 > SecurityIdentity.runAs(PrivilegedExceptionAction) line: 212 > AccessAuditContext.doAs(SecurityIdentity, InetAddress, PrivilegedExceptionAction) line: 185 > ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ManagementRequestContext) line: 157 > ManagementRequestContextImpl$1.doExecute() line: 70 > ManagementRequestContextImpl$1(ManagementRequestContextImpl$AsyncTaskRunner).run() line: 160 > ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1142 > ThreadPoolExecutor$Worker.run() line: 617 > JBossThread(Thread).run() line: 745 > JBossThread.run() line: 320 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 15:59:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 15:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2836) Add suppressed exceptions for failures during prepare for XA spec non-compliant cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2836. ------------------------------- > Add suppressed exceptions for failures during prepare for XA spec non-compliant cases > ------------------------------------------------------------------------------------- > > Key: JBTM-2836 > URL: https://issues.jboss.org/browse/JBTM-2836 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.5.1.Final > > > There was a request for include causing exceptions to list of suppressed ones when an error happens during 2PC prepare call. That was fixed by JBTM-2822. > The fix left aside a branch of code under {{doPrepare}} method which handles cases when {{XAResourceRecord#topLevelPrepare}} ends in situation which is not compliant with XA specification (https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAResourceRecord.java#L280) > Then there is taken code to > https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/BasicAction.java#L2742 > This enhancement follows the fix JBTM-2822 and saves deferred exception at that case as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 20 15:59:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 20 Jan 2017 15:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2836) Add suppressed exceptions for failures during prepare for XA spec non-compliant cases In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2836: -------------------------------- Fix Version/s: 5.5.1.Final > Add suppressed exceptions for failures during prepare for XA spec non-compliant cases > ------------------------------------------------------------------------------------- > > Key: JBTM-2836 > URL: https://issues.jboss.org/browse/JBTM-2836 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.5.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.5.1.Final > > > There was a request for include causing exceptions to list of suppressed ones when an error happens during 2PC prepare call. That was fixed by JBTM-2822. > The fix left aside a branch of code under {{doPrepare}} method which handles cases when {{XAResourceRecord#topLevelPrepare}} ends in situation which is not compliant with XA specification (https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAResourceRecord.java#L280) > Then there is taken code to > https://github.com/jbosstm/narayana/blob/5.5.0.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/BasicAction.java#L2742 > This enhancement follows the fix JBTM-2822 and saves deferred exception at that case as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 04:57:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 04:57:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2843) BlackTie builds failing (including release quickstarts) In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2843: ----------------------------------- Summary: BlackTie builds failing (including release quickstarts) Key: JBTM-2843 URL: https://issues.jboss.org/browse/JBTM-2843 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Tom Jenkinson Assignee: Amos Feng Priority: Blocker There are some builds failing consistently: Main build: http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/58/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux/console Hanging here: {quote} jboss.naming.context.java.JmsXA: javax.naming.NameNotFoundException: JmsXA -- service jboss.naming.context.java.JmsXA at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) at javax.naming.InitialContext.lookup(InitialContext.java:417) at javax.naming.InitialContext.lookup(InitialContext.java:417) at org.codehaus.stomp.jms.StompConnect.createXAConnectionFactory(StompConnect.java:195) at org.codehaus.stomp.jms.StompConnect.getXAConnectionFactory(StompConnect.java:84) at org.codehaus.stomp.jms.StompConnect.assignProtocolConverter(StompConnect.java:64) at org.codehaus.stomp.tcp.TcpTransportServer.run(TcpTransportServer.java:82) at java.lang.Thread.run(Thread.java:745) {quote} Release quickstarts: http://narayanaci1.eng.hst.ams2.redhat.com/job/release-narayana-quickstarts/13/console (similar error and shows {quote} [exec] "Services that were unable to start:" => ["jboss.concurrent.ee.context.service.default"], [exec] "Services that may be the cause:" => [ [exec] "jboss.iiop-openjdk.naming-service", [exec] "jboss.iiop-openjdk.orb-service" {quote} ) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:03:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:03:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1864) Implement volatile participant interface for REST-AT integration API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-1864: --------------------------------- > Implement volatile participant interface for REST-AT integration API > -------------------------------------------------------------------- > > Key: JBTM-1864 > URL: https://issues.jboss.org/browse/JBTM-1864 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:03:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:03:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1864) Implement volatile participant interface for REST-AT integration API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1864: -------------------------------- Fix Version/s: (was: 6.later) > Implement volatile participant interface for REST-AT integration API > -------------------------------------------------------------------- > > Key: JBTM-1864 > URL: https://issues.jboss.org/browse/JBTM-1864 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:03:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:03:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1864) Implement volatile participant interface for REST-AT integration API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1864. ------------------------------- Resolution: Duplicate Issue > Implement volatile participant interface for REST-AT integration API > -------------------------------------------------------------------- > > Key: JBTM-1864 > URL: https://issues.jboss.org/browse/JBTM-1864 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:04:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:04:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2259) Allow the ordering of some synchronizations to be configurable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2259: --------------------------------- > Allow the ordering of some synchronizations to be configurable > --------------------------------------------------------------- > > Key: JBTM-2259 > URL: https://issues.jboss.org/browse/JBTM-2259 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > IronJacamar delists resources in a beforeCompletion synchronization but under certain circumstances (see attached forum thread) it may run before all JPA persistence providers beforeCompletion synchronizations have been called (which breaks JPA). > The request is to add a configuration option to control the order in which certain synchronizations are called. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:04:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:04:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2259) Allow the ordering of some synchronizations to be configurable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2259: -------------------------------- Fix Version/s: (was: 6.later) > Allow the ordering of some synchronizations to be configurable > --------------------------------------------------------------- > > Key: JBTM-2259 > URL: https://issues.jboss.org/browse/JBTM-2259 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > IronJacamar delists resources in a beforeCompletion synchronization but under certain circumstances (see attached forum thread) it may run before all JPA persistence providers beforeCompletion synchronizations have been called (which breaks JPA). > The request is to add a configuration option to control the order in which certain synchronizations are called. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:04:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2259) Allow the ordering of some synchronizations to be configurable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2259. ------------------------------- Resolution: Rejected > Allow the ordering of some synchronizations to be configurable > --------------------------------------------------------------- > > Key: JBTM-2259 > URL: https://issues.jboss.org/browse/JBTM-2259 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > IronJacamar delists resources in a beforeCompletion synchronization but under certain circumstances (see attached forum thread) it may run before all JPA persistence providers beforeCompletion synchronizations have been called (which breaks JPA). > The request is to add a configuration option to control the order in which certain synchronizations are called. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:04:04 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:04:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1681) EJB support for Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-1681: --------------------------------- > EJB support for Compensations API > --------------------------------- > > Key: JBTM-1681 > URL: https://issues.jboss.org/browse/JBTM-1681 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > > We need to be able to use all the annotations on EJBs and also allow allow the handler implementations to be EJBs. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:04:04 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:04:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1681) EJB support for Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1681: -------------------------------- Fix Version/s: (was: 6.later) > EJB support for Compensations API > --------------------------------- > > Key: JBTM-1681 > URL: https://issues.jboss.org/browse/JBTM-1681 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > > We need to be able to use all the annotations on EJBs and also allow allow the handler implementations to be EJBs. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:04:04 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:04:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1681) EJB support for Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1681. ------------------------------- Resolution: Deferred > EJB support for Compensations API > --------------------------------- > > Key: JBTM-1681 > URL: https://issues.jboss.org/browse/JBTM-1681 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > > We need to be able to use all the annotations on EJBs and also allow allow the handler implementations to be EJBs. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:05:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2250: --------------------------------- > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Attachments: 2235.jstack, console.out, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:05:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2250: -------------------------------- Fix Version/s: (was: 6.later) > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Attachments: 2235.jstack, console.out, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:05:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:05:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2250) RecoveryManagerStartStopTest hang waiting for byteman rendezvous In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2250. ------------------------------- Resolution: Migrated to another ITS > RecoveryManagerStartStopTest hang waiting for byteman rendezvous > ---------------------------------------------------------------- > > Key: JBTM-2250 > URL: https://issues.jboss.org/browse/JBTM-2250 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Attachments: 2235.jstack, console.out, jstack.1125 > > > The test hung running CI job narayana-jdbcobjectstore (jstack output attached). Buiid config details are: > {quote} > Started by upstream project "narayana-jdbcobjectstore" build number 99 > originally caused by: > Started by user anonymous > Building remotely on brandon in workspace /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux > Checkout:linux / /home/hudson/workspace/narayana-jdbcobjectstore/DB_TYPE/db2/jdk/jdk7.latest/slave/linux - hudson.remoting.Channel at 64cff684:brandon > Using strategy: Default > Last Built Revision: Revision c37dd7bad1eb75837d79f0356baf35d9fae60a81 (origin/master) > Wiping out workspace first. > Cloning the remote Git repository > Cloning repository git://github.com/jbosstm/narayana.git > git --version > git version 1.7.1 > Fetching upstream changes from origin > Commencing build of Revision cda46e475c3ce62243cf7c63e68310923cb1930b (origin/master > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:06:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2243) Performance test harness hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2243: --------------------------------- > Performance test harness hang > ----------------------------- > > Key: JBTM-2243 > URL: https://issues.jboss.org/browse/JBTM-2243 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Attachments: 10046.jstack, archive.zip > > > CI job http://172.17.131.2/job/narayana-performance/TESTS=RTS,jdk=jdk7.latest,label=haverstraw/89/ hang - see attachments for details -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:06:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2243) Performance test harness hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2243: -------------------------------- Fix Version/s: (was: 6.later) > Performance test harness hang > ----------------------------- > > Key: JBTM-2243 > URL: https://issues.jboss.org/browse/JBTM-2243 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Attachments: 10046.jstack, archive.zip > > > CI job http://172.17.131.2/job/narayana-performance/TESTS=RTS,jdk=jdk7.latest,label=haverstraw/89/ hang - see attachments for details -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:06:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2243) Performance test harness hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2243. ------------------------------- Resolution: Won't Fix > Performance test harness hang > ----------------------------- > > Key: JBTM-2243 > URL: https://issues.jboss.org/browse/JBTM-2243 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Attachments: 10046.jstack, archive.zip > > > CI job http://172.17.131.2/job/narayana-performance/TESTS=RTS,jdk=jdk7.latest,label=haverstraw/89/ hang - see attachments for details -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:07:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:07:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-747) Implement REST-tx specifications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-747: -------------------------------- > Implement REST-tx specifications > -------------------------------- > > Key: JBTM-747 > URL: https://issues.jboss.org/browse/JBTM-747 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, TxBridge > Reporter: Mark Little > Assignee: Michael Musgrove > Attachments: REST-Atomic_v2_draft_8_comments_sept_4.pdf, rest-at-tm.xsd > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:07:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:07:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-747) Implement REST-tx specifications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-747: ------------------------------- Fix Version/s: (was: 6.later) > Implement REST-tx specifications > -------------------------------- > > Key: JBTM-747 > URL: https://issues.jboss.org/browse/JBTM-747 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, TxBridge > Reporter: Mark Little > Assignee: Michael Musgrove > Attachments: REST-Atomic_v2_draft_8_comments_sept_4.pdf, rest-at-tm.xsd > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:07:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:07:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-747) Implement REST-tx specifications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-747. ------------------------------ Resolution: Deferred > Implement REST-tx specifications > -------------------------------- > > Key: JBTM-747 > URL: https://issues.jboss.org/browse/JBTM-747 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, TxBridge > Reporter: Mark Little > Assignee: Michael Musgrove > Attachments: REST-Atomic_v2_draft_8_comments_sept_4.pdf, rest-at-tm.xsd > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:07:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:07:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1453) Reinstate/review the numbers to detect performance regressions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-1453: --------------------------------- > Reinstate/review the numbers to detect performance regressions > -------------------------------------------------------------- > > Key: JBTM-1453 > URL: https://issues.jboss.org/browse/JBTM-1453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.1.0 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:07:04 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:07:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1453) Reinstate/review the numbers to detect performance regressions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1453: -------------------------------- Fix Version/s: 5.1.0 (was: 6.later) > Reinstate/review the numbers to detect performance regressions > -------------------------------------------------------------- > > Key: JBTM-1453 > URL: https://issues.jboss.org/browse/JBTM-1453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.1.0 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:07:04 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:07:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1453) Reinstate/review the numbers to detect performance regressions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1453. ------------------------------- Resolution: Done > Reinstate/review the numbers to detect performance regressions > -------------------------------------------------------------- > > Key: JBTM-1453 > URL: https://issues.jboss.org/browse/JBTM-1453 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.1.0 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:08:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:08:01 -0500 (EST) 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 reopened JBTM-2103: --------------------------------- > 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 > > 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 (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:08:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:08:01 -0500 (EST) 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: (was: 6.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 > > 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 (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:08:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:08:01 -0500 (EST) 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 closed JBTM-2103. ------------------------------- Resolution: Won't Fix > 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 > > 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 (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:11:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:11:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2151: -------------------------------- Fix Version/s: 5.0.2 (was: 5.later) > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations, Demonstrator > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:11:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:11:02 -0500 (EST) 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 closed JBTM-2151. ------------------------------- > 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.0.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:12:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:12:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2265) BlackTie Jatmibroker TestTPConversation hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2265: -------------------------------- Fix Version/s: 5.2.0 (was: 5.later) > BlackTie Jatmibroker TestTPConversation hang > -------------------------------------------- > > Key: JBTM-2265 > URL: https://issues.jboss.org/browse/JBTM-2265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.2.0 > > Attachments: blacktie.zip, jstack.27403, jstack.27697 > > > CI job http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/193 is hanging with what looks like a stomp comms error -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:12:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:12:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2265) BlackTie Jatmibroker TestTPConversation hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2265. ------------------------------- > BlackTie Jatmibroker TestTPConversation hang > -------------------------------------------- > > Key: JBTM-2265 > URL: https://issues.jboss.org/browse/JBTM-2265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.2.0 > > Attachments: blacktie.zip, jstack.27403, jstack.27697 > > > CI job http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/193 is hanging with what looks like a stomp comms error -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:13:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2390. ------------------------------- > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.2 > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:13:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2390: -------------------------------- Fix Version/s: 5.2.2 (was: 5.later) > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.2 > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:13:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2436) Use ManagedThreadFactory, if available, to create PeriodicRecovery thread In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2436: --------------------------------- > Use ManagedThreadFactory, if available, to create PeriodicRecovery thread > ------------------------------------------------------------------------- > > Key: JBTM-2436 > URL: https://issues.jboss.org/browse/JBTM-2436 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:13:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2436) Use ManagedThreadFactory, if available, to create PeriodicRecovery thread In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2436: -------------------------------- Fix Version/s: (was: 5.later) > Use ManagedThreadFactory, if available, to create PeriodicRecovery thread > ------------------------------------------------------------------------- > > Key: JBTM-2436 > URL: https://issues.jboss.org/browse/JBTM-2436 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:14:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2436) Use ManagedThreadFactory, if available, to create PeriodicRecovery thread In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2436. ------------------------------- Resolution: Rejected > Use ManagedThreadFactory, if available, to create PeriodicRecovery thread > ------------------------------------------------------------------------- > > Key: JBTM-2436 > URL: https://issues.jboss.org/browse/JBTM-2436 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:16:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:16:00 -0500 (EST) 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 ] Tom Jenkinson updated JBTM-2488: -------------------------------- Fix Version/s: 5.2.0 (was: 5.later) > 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.2.0 > > > 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 (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:16:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:16:00 -0500 (EST) 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 ] Tom Jenkinson closed JBTM-2488. ------------------------------- > 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.2.0 > > > 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 (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:20:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:20:01 -0500 (EST) 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 ] Tom Jenkinson updated JBTM-2489: -------------------------------- Fix Version/s: 5.2.0 (was: 5.later) > 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.2.0 > > > 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 (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:20:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:20:01 -0500 (EST) 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 ] Tom Jenkinson closed JBTM-2489. ------------------------------- > 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.2.0 > > > 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 (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:21:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2398) Support VolatileStore.allObjUids In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2398: -------------------------------- Fix Version/s: 5.2.0 (was: 5.later) > Support VolatileStore.allObjUids > --------------------------------- > > Key: JBTM-2398 > URL: https://issues.jboss.org/browse/JBTM-2398 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Performance Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.2.0 > > > This method is used by REST-AT and would be a useful addition for baselining the performance of the coordinator for comparison with non transactional and empty transaction requests. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:21:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2398) Support VolatileStore.allObjUids In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2398. ------------------------------- > Support VolatileStore.allObjUids > --------------------------------- > > Key: JBTM-2398 > URL: https://issues.jboss.org/browse/JBTM-2398 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Performance Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.2.0 > > > This method is used by REST-AT and would be a useful addition for baselining the performance of the coordinator for comparison with non transactional and empty transaction requests. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:22:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:22:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2364) Include profiler output in benchmark runs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2364: -------------------------------- Fix Version/s: 5.2.2 (was: 5.later) > Include profiler output in benchmark runs > ----------------------------------------- > > Key: JBTM-2364 > URL: https://issues.jboss.org/browse/JBTM-2364 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Performance Testing > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.2.2 > > > Benchmarks runs should include profiling data to help diagnose performance issues and find opportunities for performance enhancements. > The natural choice is Java Flight Recorder (http://www.oracle.com/technetwork/java/javaseproducts/mission-control/java-mission-control-1998576.html) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:22:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:22:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2364) Include profiler output in benchmark runs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2364. ------------------------------- > Include profiler output in benchmark runs > ----------------------------------------- > > Key: JBTM-2364 > URL: https://issues.jboss.org/browse/JBTM-2364 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Performance Testing > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.2.2 > > > Benchmarks runs should include profiling data to help diagnose performance issues and find opportunities for performance enhancements. > The natural choice is Java Flight Recorder (http://www.oracle.com/technetwork/java/javaseproducts/mission-control/java-mission-control-1998576.html) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:22:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:22:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2465) PR job is missing perf regression output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2465: --------------------------------- > PR job is missing perf regression output > ---------------------------------------- > > Key: JBTM-2465 > URL: https://issues.jboss.org/browse/JBTM-2465 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > > The PERF axis of the CI job https://github.com/jbosstm/narayana/pull/889 did not produce any output because of the following error: > {code} > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.performance.Performance1-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/jmh/com.arjuna.ats.jta.xa.performance.JTAStoreTests-master.csv': No such file or directory > no benchmarks to compare > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:22:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:22:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2465) PR job is missing perf regression output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2465: -------------------------------- Fix Version/s: (was: 5.later) > PR job is missing perf regression output > ---------------------------------------- > > Key: JBTM-2465 > URL: https://issues.jboss.org/browse/JBTM-2465 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > > The PERF axis of the CI job https://github.com/jbosstm/narayana/pull/889 did not produce any output because of the following error: > {code} > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.performance.Performance1-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/jmh/com.arjuna.ats.jta.xa.performance.JTAStoreTests-master.csv': No such file or directory > no benchmarks to compare > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:22:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:22:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2465) PR job is missing perf regression output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2465. ------------------------------- Resolution: Out of Date > PR job is missing perf regression output > ---------------------------------------- > > Key: JBTM-2465 > URL: https://issues.jboss.org/browse/JBTM-2465 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > > The PERF axis of the CI job https://github.com/jbosstm/narayana/pull/889 did not produce any output because of the following error: > {code} > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.performance.Performance1-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaCore/arjuna/target/jmh/com.hp.mwtests.ts.arjuna.atomicaction.CheckedActionTest-master.csv': No such file or directory > Error: Unable to access jarfile /home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/benchmarks.jar > cp: cannot stat `/home/hudson/workspace/btny-pulls-narayana-jdk8/PROFILE/PERF/jdk/jdk8.latest/label/linux/tmp/performance/narayana/ArjunaJTA/jta/target/jmh/com.arjuna.ats.jta.xa.performance.JTAStoreTests-master.csv': No such file or directory > no benchmarks to compare > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:23:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:23:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2416: --------------------------------- > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:23:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:23:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2416: -------------------------------- Fix Version/s: (was: 5.later) > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:23:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:23:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2416. ------------------------------- Resolution: Out of Date > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:23:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:23:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2405) QA suite failure: CrashRecovery05_1_Test04 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2405: --------------------------------- > QA suite failure: CrashRecovery05_1_Test04 > ------------------------------------------ > > Key: JBTM-2405 > URL: https://issues.jboss.org/browse/JBTM-2405 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/830/PROFILE=QA_JTS_JACORB,jdk=jdk8.latest,label=linux/ -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:23:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:23:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2405) QA suite failure: CrashRecovery05_1_Test04 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2405: -------------------------------- Fix Version/s: (was: 5.later) > QA suite failure: CrashRecovery05_1_Test04 > ------------------------------------------ > > Key: JBTM-2405 > URL: https://issues.jboss.org/browse/JBTM-2405 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/830/PROFILE=QA_JTS_JACORB,jdk=jdk8.latest,label=linux/ -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:23:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:23:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2405) QA suite failure: CrashRecovery05_1_Test04 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2405. ------------------------------- Resolution: Duplicate Issue > QA suite failure: CrashRecovery05_1_Test04 > ------------------------------------------ > > Key: JBTM-2405 > URL: https://issues.jboss.org/browse/JBTM-2405 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/830/PROFILE=QA_JTS_JACORB,jdk=jdk8.latest,label=linux/ -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:24:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:24:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2360) QA suite failure: CrashRecovery05_2_Test045 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2360: --------------------------------- > QA suite failure: CrashRecovery05_2_Test045 > ------------------------------------------- > > Key: JBTM-2360 > URL: https://issues.jboss.org/browse/JBTM-2360 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/779/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux/ > I had a look and there are some messages that suggest that the connection was broken. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:24:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:24:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2360) QA suite failure: CrashRecovery05_2_Test045 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2360: -------------------------------- Fix Version/s: (was: 5.later) > QA suite failure: CrashRecovery05_2_Test045 > ------------------------------------------- > > Key: JBTM-2360 > URL: https://issues.jboss.org/browse/JBTM-2360 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/779/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux/ > I had a look and there are some messages that suggest that the connection was broken. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:24:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:24:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2360) QA suite failure: CrashRecovery05_2_Test045 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2360. ------------------------------- Resolution: Duplicate Issue > QA suite failure: CrashRecovery05_2_Test045 > ------------------------------------------- > > Key: JBTM-2360 > URL: https://issues.jboss.org/browse/JBTM-2360 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/779/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux/ > I had a look and there are some messages that suggest that the connection was broken. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:24:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:24:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2252) QA suite failure: CrashRecovery05_2_Test030 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2252: --------------------------------- > QA suite failure: CrashRecovery05_2_Test030 > -------------------------------------------- > > Key: JBTM-2252 > URL: https://issues.jboss.org/browse/JBTM-2252 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Attachments: CrashRecovery05_2_Test030.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/638/ -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:24:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:24:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2252) QA suite failure: CrashRecovery05_2_Test030 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2252: -------------------------------- Fix Version/s: (was: 5.later) > QA suite failure: CrashRecovery05_2_Test030 > -------------------------------------------- > > Key: JBTM-2252 > URL: https://issues.jboss.org/browse/JBTM-2252 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Attachments: CrashRecovery05_2_Test030.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/638/ -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:24:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:24:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2252) QA suite failure: CrashRecovery05_2_Test030 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2252. ------------------------------- Resolution: Out of Date > QA suite failure: CrashRecovery05_2_Test030 > -------------------------------------------- > > Key: JBTM-2252 > URL: https://issues.jboss.org/browse/JBTM-2252 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Attachments: CrashRecovery05_2_Test030.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/638/ -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:24:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:24:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2196) QA suite failure: CrashRecovery05_2_Test034 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2196: -------------------------------- Fix Version/s: (was: 5.later) > QA suite failure: CrashRecovery05_2_Test034 > ------------------------------------------- > > Key: JBTM-2196 > URL: https://issues.jboss.org/browse/JBTM-2196 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Attachments: CrashRecovery05_2_Test034.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/550/ -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:24:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:24:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2196) QA suite failure: CrashRecovery05_2_Test034 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2196. ------------------------------- > QA suite failure: CrashRecovery05_2_Test034 > ------------------------------------------- > > Key: JBTM-2196 > URL: https://issues.jboss.org/browse/JBTM-2196 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Attachments: CrashRecovery05_2_Test034.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/550/ -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:24:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:24:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2126) QA suite failure: CrashRecovery05_2_Test008 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2126: --------------------------------- > QA suite failure: CrashRecovery05_2_Test008 > ------------------------------------------- > > Key: JBTM-2126 > URL: https://issues.jboss.org/browse/JBTM-2126 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/466/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:25:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2126) QA suite failure: CrashRecovery05_2_Test008 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2126: -------------------------------- Fix Version/s: (was: 5.later) > QA suite failure: CrashRecovery05_2_Test008 > ------------------------------------------- > > Key: JBTM-2126 > URL: https://issues.jboss.org/browse/JBTM-2126 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/466/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:25:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2706) Verify that we can run on the IBM JVM with OpenJDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2706: --------------------------------- > Verify that we can run on the IBM JVM with OpenJDK > -------------------------------------------------- > > Key: JBTM-2706 > URL: https://issues.jboss.org/browse/JBTM-2706 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.3.4.Final > > > We need to set up a CI job that runs the JTS tests using the OpenJDK orb -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:25:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2126) QA suite failure: CrashRecovery05_2_Test008 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2126. ------------------------------- Resolution: Duplicate Issue > QA suite failure: CrashRecovery05_2_Test008 > ------------------------------------------- > > Key: JBTM-2126 > URL: https://issues.jboss.org/browse/JBTM-2126 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/466/PROFILE=QA_JTS_JACORB,jdk=jdk7.latest,label=linux -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:25:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2706) Verify that we can run on the IBM JVM with OpenJDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2706: -------------------------------- Fix Version/s: 5.3.4.Final (was: 5.later) > Verify that we can run on the IBM JVM with OpenJDK > -------------------------------------------------- > > Key: JBTM-2706 > URL: https://issues.jboss.org/browse/JBTM-2706 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.3.4.Final > > > We need to set up a CI job that runs the JTS tests using the OpenJDK orb -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:26:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2706) Verify that we can run on the IBM JVM with OpenJDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2706. ------------------------------- Resolution: Done > Verify that we can run on the IBM JVM with OpenJDK > -------------------------------------------------- > > Key: JBTM-2706 > URL: https://issues.jboss.org/browse/JBTM-2706 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.3.4.Final > > > We need to set up a CI job that runs the JTS tests using the OpenJDK orb -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:26:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2528) QA testsuite needs documenting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2528: -------------------------------- Fix Version/s: 5.2.14.Final (was: 5.later) > QA testsuite needs documenting > ------------------------------ > > Key: JBTM-2528 > URL: https://issues.jboss.org/browse/JBTM-2528 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.14.Final > > > We need a document detailing what the tests in the QA testsuite test. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:26:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:26:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2528) QA testsuite needs documenting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2528. ------------------------------- > QA testsuite needs documenting > ------------------------------ > > Key: JBTM-2528 > URL: https://issues.jboss.org/browse/JBTM-2528 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.14.Final > > > We need a document detailing what the tests in the QA testsuite test. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 23 06:27:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 23 Jan 2017 06:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2542) Migrate performance tests to the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2542: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Migrate performance tests to the performance repo > ------------------------------------------------- > > Key: JBTM-2542 > URL: https://issues.jboss.org/browse/JBTM-2542 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Attachments: config.xml, eap-cmp-config.xml > > > We still have lots of performance related unit tests that need migrating: > rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceDefaultUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhasePerformanceVolatileUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceVolatileUnitTest.java > ArjunaJTA/jta/tests/classes/com/arjuna/ats/jta/xa/performance/OnePhase2PCPerformanceDefaultUnitTest.java > ArjunaJTA/jta/tests/classes/com/hp/mwtests/ts/jta/commitmarkable/PerformanceTestCommitMarkableResource.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance1.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance2.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance4.java > ArjunaCore/arjuna/tests/classes/com/hp/mwtests/ts/arjuna/performance/Performance3.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance1.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance2.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/local/performance/Performance3.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/PerfHammer.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/remote/hammer/GridWorker.java > ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/local/synchronizations/Performance.java > ArjunaJTA/jta/tests/classes/io/narayana/perf/product/Product.java > ArjunaJTA/jta/tests/classes/io/narayana/perf/product/ProductWorker.java -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 25 05:01:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 25 Jan 2017 05:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2843) BlackTie builds failing (including release quickstarts) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1122 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > BlackTie builds failing (including release quickstarts) > ------------------------------------------------------- > > Key: JBTM-2843 > URL: https://issues.jboss.org/browse/JBTM-2843 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > > There are some builds failing consistently: > Main build: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/58/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux/console > Hanging here: > {quote} > jboss.naming.context.java.JmsXA: javax.naming.NameNotFoundException: JmsXA -- service jboss.naming.context.java.JmsXA > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.codehaus.stomp.jms.StompConnect.createXAConnectionFactory(StompConnect.java:195) > at org.codehaus.stomp.jms.StompConnect.getXAConnectionFactory(StompConnect.java:84) > at org.codehaus.stomp.jms.StompConnect.assignProtocolConverter(StompConnect.java:64) > at org.codehaus.stomp.tcp.TcpTransportServer.run(TcpTransportServer.java:82) > at java.lang.Thread.run(Thread.java:745) > {quote} > Release quickstarts: > http://narayanaci1.eng.hst.ams2.redhat.com/job/release-narayana-quickstarts/13/console > (similar error and shows > {quote} > [exec] "Services that were unable to start:" => ["jboss.concurrent.ee.context.service.default"], > [exec] "Services that may be the cause:" => [ > [exec] "jboss.iiop-openjdk.naming-service", > [exec] "jboss.iiop-openjdk.orb-service" > {quote} > ) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 25 05:02:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 25 Jan 2017 05:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2843) BlackTie builds failing (including release quickstarts) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13353240#comment-13353240 ] Tom Jenkinson commented on JBTM-2843: ------------------------------------- I think it is generating standalone-blacktie.xml that is incompatible with the current master WildFly version. I noticed the build-tools we use are out of date. > BlackTie builds failing (including release quickstarts) > ------------------------------------------------------- > > Key: JBTM-2843 > URL: https://issues.jboss.org/browse/JBTM-2843 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > > There are some builds failing consistently: > Main build: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/58/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux/console > Hanging here: > {quote} > jboss.naming.context.java.JmsXA: javax.naming.NameNotFoundException: JmsXA -- service jboss.naming.context.java.JmsXA > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.codehaus.stomp.jms.StompConnect.createXAConnectionFactory(StompConnect.java:195) > at org.codehaus.stomp.jms.StompConnect.getXAConnectionFactory(StompConnect.java:84) > at org.codehaus.stomp.jms.StompConnect.assignProtocolConverter(StompConnect.java:64) > at org.codehaus.stomp.tcp.TcpTransportServer.run(TcpTransportServer.java:82) > at java.lang.Thread.run(Thread.java:745) > {quote} > Release quickstarts: > http://narayanaci1.eng.hst.ams2.redhat.com/job/release-narayana-quickstarts/13/console > (similar error and shows > {quote} > [exec] "Services that were unable to start:" => ["jboss.concurrent.ee.context.service.default"], > [exec] "Services that may be the cause:" => [ > [exec] "jboss.iiop-openjdk.naming-service", > [exec] "jboss.iiop-openjdk.orb-service" > {quote} > ) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 25 05:50:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 25 Jan 2017 05:50:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2766) Implement pooling for transactional driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2766: -------------------------------- Issue Type: Enhancement (was: Task) > Implement pooling for transactional driver > ------------------------------------------ > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > Transactional driver does not provide connection pooling. We should either implement it ourselves or find a third party implementation. In case of the second option we should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jan 25 06:52:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 25 Jan 2017 06:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2843) BlackTie builds failing (including release quickstarts) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13353307#comment-13353307 ] Tom Jenkinson commented on JBTM-2843: ------------------------------------- Seems like a simple upgrade of the build-tools doesn't work. Effectively the config that worked for 4.2 doesn't seem to work on the current WFLY master server. Attempting to use 10.1.0 zip from the downloads site however that would mean that the BT runs would execute with the older version of Narayana. > BlackTie builds failing (including release quickstarts) > ------------------------------------------------------- > > Key: JBTM-2843 > URL: https://issues.jboss.org/browse/JBTM-2843 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > > There are some builds failing consistently: > Main build: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/58/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux/console > Hanging here: > {quote} > jboss.naming.context.java.JmsXA: javax.naming.NameNotFoundException: JmsXA -- service jboss.naming.context.java.JmsXA > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.codehaus.stomp.jms.StompConnect.createXAConnectionFactory(StompConnect.java:195) > at org.codehaus.stomp.jms.StompConnect.getXAConnectionFactory(StompConnect.java:84) > at org.codehaus.stomp.jms.StompConnect.assignProtocolConverter(StompConnect.java:64) > at org.codehaus.stomp.tcp.TcpTransportServer.run(TcpTransportServer.java:82) > at java.lang.Thread.run(Thread.java:745) > {quote} > Release quickstarts: > http://narayanaci1.eng.hst.ams2.redhat.com/job/release-narayana-quickstarts/13/console > (similar error and shows > {quote} > [exec] "Services that were unable to start:" => ["jboss.concurrent.ee.context.service.default"], > [exec] "Services that may be the cause:" => [ > [exec] "jboss.iiop-openjdk.naming-service", > [exec] "jboss.iiop-openjdk.orb-service" > {quote} > ) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 26 04:45:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 26 Jan 2017 04:45:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2682) RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2682. --------------------------------- Fix Version/s: (was: 5.later) Assignee: (was: Gytis Trikleris) Resolution: Out of Date > RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover > ----------------------------------------------------------------- > > Key: JBTM-2682 > URL: https://issues.jboss.org/browse/JBTM-2682 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Priority: Minor > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 191.234 sec <<< FAILURE! - in org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase > testCrashBeforeCommit(org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase) Time elapsed: 126.558 sec <<< FAILURE! > java.lang.AssertionError: Recovery failed > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase.testCrashBeforeCommit(RecoveryIntegrationTestCase.java:125) > {code} > {code} > javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} > May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -Dorg.jboss.byteman.verbose, -Dorg.jboss.byteman.transform.all, -javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 19:55:39,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final > 19:55:40,131 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 19:55:40,513 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting > 19:55:44,456 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 19:55:44,559 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 42) WFLYCLINF0001: Activating Infinispan subsystem. > 19:55:44,636 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 63) WFLYWS0002: Activating WebServices Extension > 19:55:44,659 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.6.Final > 19:55:44,670 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.6.Final > 19:55:44,592 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 49) WFLYJSF0007: Activated the following JSF Implementations: [main] > 19:55:44,619 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 61) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 19:55:45,323 INFO [org.jboss.as.security] (ServerService Thread Pool -- 60) WFLYSEC0002: Activating Security Subsystem > 19:55:45,345 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 1.3.21.Final starting > 19:55:45,381 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 43) WFLYIIOP0001: Activating IIOP Subsystem > 19:55:45,400 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 53) WFLYNAM0001: Activating Naming Subsystem > 19:55:45,622 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final > 19:55:45,580 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final > 19:55:46,430 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 41) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors > 19:55:46,561 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) > 19:55:46,803 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 37) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:55:46,967 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 19:55:47,167 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 19:55:47,181 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 > 19:55:47,136 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 19:55:48,041 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. > 19:55:48,132 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. > 19:55:48,116 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started > 19:55:49,637 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server. > 19:55:50,186 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting > 19:55:50,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 19:55:50,400 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,435 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,437 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,442 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,443 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,445 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,446 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,456 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,464 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,476 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,709 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,758 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource > 19:55:50,786 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.narayana.rest.integration.ParticipantResource.commit(org.jboss.narayana.rest.integration.ParticipantInformation) void for rule Kill JVM before commit > 19:55:50,803 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource > 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,863 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /rest-at-coordinator > 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,872 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,875 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,890 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: volatile-rest-at-participant > 19:55:51,378 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments > 19:55:51,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant > 19:55:52,131 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final > 19:55:52,379 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 19:55:53,079 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 19:55:53,163 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 19:55:53,226 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221013: Using NIO Journal > 19:55:53,437 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) > 19:55:53,576 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 19:55:53,600 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 19:55:53,636 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 19:55:53,639 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 19:55:55,441 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:55:55,442 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:55:57,287 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221007: Server is now live > 19:55:57,288 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] > 19:55:57,479 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA > 19:55:57,585 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:55:57,651 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:55:57,668 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 19:55:57,669 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.DLQ > 19:55:58,592 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started > 19:55:58,592 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra > 19:55:58,594 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 19:55:58,594 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 19:55:58,975 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 20406ms - Started 311 of 596 services (387 services are lazy, passive or on-demand) > 19:55:59,088 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content > 19:55:59,141 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:56:00,376 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 32) WFLYUT0021: Registered web context: /test > 19:56:01,492 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > May 17, 2016 7:56:02 PM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > 19:56:03,832 INFO [org.hibernate.validator.internal.util.Version] (default task-2) HV000001: Hibernate Validator 5.2.4.Final > 19:56:06,698 INFO [stdout] (default task-10) Rule.execute called for Kill JVM before commit_0 > 19:56:06,711 INFO [stdout] (default task-10) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 19:56:06,712 INFO [stdout] (default task-10) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 19:56:06,713 INFO [stdout] (default task-10) Default helper activated > 19:56:06,719 INFO [stdout] (default task-10) calling installed(Kill JVM before commit) for helper classorg.jboss.byteman.rule.helper.Helper > 19:56:06,719 INFO [stdout] (default task-10) Installed rule using default helper : Kill JVM before commit > 19:56:06,720 INFO [stdout] (default task-10) Kill JVM before commit execute > 19:56:06,724 INFO [stdout] (default task-10) rule.debug{Kill JVM before commit} : Killing JVM > May 17, 2016 7:56:07 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, javaVmArguments=-server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} > May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > 19:56:07,928 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final > 19:56:08,509 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 19:56:08,676 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting > 19:56:14,309 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 19:56:14,332 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final > 19:56:14,341 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final > 19:56:14,542 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 43) WFLYCLINF0001: Activating Infinispan subsystem. > 19:56:14,582 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension > 19:56:14,588 INFO [org.jboss.as.security] (ServerService Thread Pool -- 61) WFLYSEC0002: Activating Security Subsystem > 19:56:14,618 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem > 19:56:14,584 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 19:56:14,779 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 50) WFLYJSF0007: Activated the following JSF Implementations: [main] > 19:56:15,111 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.18.Final > 19:56:15,393 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) > 19:56:15,397 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 42) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors > 19:56:15,384 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final > 19:56:15,364 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 44) WFLYIIOP0001: Activating IIOP Subsystem > 19:56:15,482 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.21.Final starting > 19:56:15,647 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service > 19:56:16,045 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:56:16,348 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. > 19:56:16,403 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. > 19:56:16,514 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 19:56:16,585 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 19:56:16,675 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 > 19:56:17,193 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 19:56:18,843 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 19:56:18,844 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 19:56:19,134 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,177 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,178 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,180 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,181 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,182 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,187 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,188 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,205 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,207 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,264 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,519 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant > 19:56:19,524 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,541 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,547 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,596 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: volatile-rest-at-participant > 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,620 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,621 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:20,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /rest-at-coordinator > 19:56:20,390 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started > 19:56:20,449 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments > 19:56:20,462 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 19:56:20,780 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 19:56:21,802 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) > 19:56:22,023 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final > 19:56:22,222 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 19:56:22,251 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:56:23,039 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221013: Using NIO Journal > 19:56:23,341 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 19:56:23,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 19:56:23,364 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 19:56:23,366 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 19:56:23,742 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 2) WFLYUT0021: Registered web context: /test > 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221007: Server is now live > 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] > 19:56:24,368 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 2) AMQ221003: trying to deploy queue jms.queue.DLQ > 19:56:24,519 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA > 19:56:24,602 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 19:56:24,605 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:56:24,608 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:56:24,676 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started > 19:56:24,677 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra > 19:56:24,680 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 19:56:24,681 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:56:24,730 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 17840ms - Started 382 of 672 services (398 services are lazy, passive or on-demand) > 19:56:26,692 INFO [org.hibernate.validator.internal.util.Version] (default task-1) HV000001: Hibernate Validator 5.2.4.Final > 19:56:27,484 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:16 > 19:56:27,485 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:56:43,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:56:57,210 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:11,314 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:25,429 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:39,533 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:43,574 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /test > 19:57:43,608 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 52ms > 19:57:43,832 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content > 19:57:43,833 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") > May 17, 2016 7:57:43 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 19:57:43,850 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout. > 19:57:43,854 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown' > 19:57:43,877 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:57:43,877 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 19:57:43,877 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 19:57:43,897 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 78) AMQ151003: resource adaptor stopped > 19:57:44,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /rest-at-coordinator > 19:57:44,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: rest-at-participant > 19:57:44,705 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: volatile-rest-at-participant > 19:57:44,707 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping > 19:57:44,707 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 19:57:44,714 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 77) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:57:44,717 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 74) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory > 19:57:44,879 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] stopped > 19:57:44,880 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 19:57:44,881 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 19:57:44,882 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.21.Final stopping > 19:57:44,899 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.2.0.CR2 "Kenny" stopped in 43ms > May 17, 2016 7:57:44 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 26 05:00:02 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 26 Jan 2017 05:00:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2682) RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris reopened JBTM-2682: ----------------------------------- > RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover > ----------------------------------------------------------------- > > Key: JBTM-2682 > URL: https://issues.jboss.org/browse/JBTM-2682 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Priority: Minor > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 191.234 sec <<< FAILURE! - in org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase > testCrashBeforeCommit(org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase) Time elapsed: 126.558 sec <<< FAILURE! > java.lang.AssertionError: Recovery failed > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase.testCrashBeforeCommit(RecoveryIntegrationTestCase.java:125) > {code} > {code} > javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} > May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -Dorg.jboss.byteman.verbose, -Dorg.jboss.byteman.transform.all, -javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 19:55:39,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final > 19:55:40,131 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 19:55:40,513 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting > 19:55:44,456 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 19:55:44,559 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 42) WFLYCLINF0001: Activating Infinispan subsystem. > 19:55:44,636 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 63) WFLYWS0002: Activating WebServices Extension > 19:55:44,659 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.6.Final > 19:55:44,670 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.6.Final > 19:55:44,592 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 49) WFLYJSF0007: Activated the following JSF Implementations: [main] > 19:55:44,619 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 61) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 19:55:45,323 INFO [org.jboss.as.security] (ServerService Thread Pool -- 60) WFLYSEC0002: Activating Security Subsystem > 19:55:45,345 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 1.3.21.Final starting > 19:55:45,381 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 43) WFLYIIOP0001: Activating IIOP Subsystem > 19:55:45,400 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 53) WFLYNAM0001: Activating Naming Subsystem > 19:55:45,622 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final > 19:55:45,580 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final > 19:55:46,430 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 41) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors > 19:55:46,561 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) > 19:55:46,803 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 37) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:55:46,967 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 19:55:47,167 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 19:55:47,181 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 > 19:55:47,136 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 19:55:48,041 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. > 19:55:48,132 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. > 19:55:48,116 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started > 19:55:49,637 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server. > 19:55:50,186 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting > 19:55:50,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 19:55:50,400 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,435 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,437 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,442 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,443 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,445 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,446 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,456 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,464 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,476 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,709 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,758 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource > 19:55:50,786 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.narayana.rest.integration.ParticipantResource.commit(org.jboss.narayana.rest.integration.ParticipantInformation) void for rule Kill JVM before commit > 19:55:50,803 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource > 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,863 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /rest-at-coordinator > 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,872 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,875 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,890 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: volatile-rest-at-participant > 19:55:51,378 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments > 19:55:51,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant > 19:55:52,131 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final > 19:55:52,379 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 19:55:53,079 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 19:55:53,163 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 19:55:53,226 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221013: Using NIO Journal > 19:55:53,437 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) > 19:55:53,576 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 19:55:53,600 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 19:55:53,636 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 19:55:53,639 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 19:55:55,441 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:55:55,442 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:55:57,287 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221007: Server is now live > 19:55:57,288 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] > 19:55:57,479 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA > 19:55:57,585 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:55:57,651 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:55:57,668 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 19:55:57,669 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.DLQ > 19:55:58,592 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started > 19:55:58,592 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra > 19:55:58,594 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 19:55:58,594 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 19:55:58,975 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 20406ms - Started 311 of 596 services (387 services are lazy, passive or on-demand) > 19:55:59,088 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content > 19:55:59,141 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:56:00,376 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 32) WFLYUT0021: Registered web context: /test > 19:56:01,492 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > May 17, 2016 7:56:02 PM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > 19:56:03,832 INFO [org.hibernate.validator.internal.util.Version] (default task-2) HV000001: Hibernate Validator 5.2.4.Final > 19:56:06,698 INFO [stdout] (default task-10) Rule.execute called for Kill JVM before commit_0 > 19:56:06,711 INFO [stdout] (default task-10) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 19:56:06,712 INFO [stdout] (default task-10) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 19:56:06,713 INFO [stdout] (default task-10) Default helper activated > 19:56:06,719 INFO [stdout] (default task-10) calling installed(Kill JVM before commit) for helper classorg.jboss.byteman.rule.helper.Helper > 19:56:06,719 INFO [stdout] (default task-10) Installed rule using default helper : Kill JVM before commit > 19:56:06,720 INFO [stdout] (default task-10) Kill JVM before commit execute > 19:56:06,724 INFO [stdout] (default task-10) rule.debug{Kill JVM before commit} : Killing JVM > May 17, 2016 7:56:07 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, javaVmArguments=-server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} > May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > 19:56:07,928 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final > 19:56:08,509 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 19:56:08,676 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting > 19:56:14,309 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 19:56:14,332 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final > 19:56:14,341 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final > 19:56:14,542 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 43) WFLYCLINF0001: Activating Infinispan subsystem. > 19:56:14,582 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension > 19:56:14,588 INFO [org.jboss.as.security] (ServerService Thread Pool -- 61) WFLYSEC0002: Activating Security Subsystem > 19:56:14,618 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem > 19:56:14,584 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 19:56:14,779 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 50) WFLYJSF0007: Activated the following JSF Implementations: [main] > 19:56:15,111 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.18.Final > 19:56:15,393 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) > 19:56:15,397 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 42) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors > 19:56:15,384 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final > 19:56:15,364 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 44) WFLYIIOP0001: Activating IIOP Subsystem > 19:56:15,482 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.21.Final starting > 19:56:15,647 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service > 19:56:16,045 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:56:16,348 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. > 19:56:16,403 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. > 19:56:16,514 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 19:56:16,585 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 19:56:16,675 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 > 19:56:17,193 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 19:56:18,843 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 19:56:18,844 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 19:56:19,134 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,177 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,178 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,180 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,181 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,182 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,187 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,188 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,205 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,207 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,264 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,519 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant > 19:56:19,524 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,541 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,547 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,596 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: volatile-rest-at-participant > 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,620 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,621 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:20,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /rest-at-coordinator > 19:56:20,390 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started > 19:56:20,449 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments > 19:56:20,462 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 19:56:20,780 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 19:56:21,802 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) > 19:56:22,023 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final > 19:56:22,222 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 19:56:22,251 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:56:23,039 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221013: Using NIO Journal > 19:56:23,341 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 19:56:23,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 19:56:23,364 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 19:56:23,366 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 19:56:23,742 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 2) WFLYUT0021: Registered web context: /test > 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221007: Server is now live > 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] > 19:56:24,368 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 2) AMQ221003: trying to deploy queue jms.queue.DLQ > 19:56:24,519 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA > 19:56:24,602 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 19:56:24,605 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:56:24,608 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:56:24,676 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started > 19:56:24,677 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra > 19:56:24,680 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 19:56:24,681 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:56:24,730 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 17840ms - Started 382 of 672 services (398 services are lazy, passive or on-demand) > 19:56:26,692 INFO [org.hibernate.validator.internal.util.Version] (default task-1) HV000001: Hibernate Validator 5.2.4.Final > 19:56:27,484 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:16 > 19:56:27,485 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:56:43,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:56:57,210 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:11,314 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:25,429 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:39,533 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:43,574 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /test > 19:57:43,608 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 52ms > 19:57:43,832 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content > 19:57:43,833 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") > May 17, 2016 7:57:43 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 19:57:43,850 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout. > 19:57:43,854 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown' > 19:57:43,877 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:57:43,877 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 19:57:43,877 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 19:57:43,897 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 78) AMQ151003: resource adaptor stopped > 19:57:44,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /rest-at-coordinator > 19:57:44,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: rest-at-participant > 19:57:44,705 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: volatile-rest-at-participant > 19:57:44,707 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping > 19:57:44,707 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 19:57:44,714 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 77) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:57:44,717 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 74) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory > 19:57:44,879 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] stopped > 19:57:44,880 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 19:57:44,881 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 19:57:44,882 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.21.Final stopping > 19:57:44,899 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.2.0.CR2 "Kenny" stopped in 43ms > May 17, 2016 7:57:44 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 26 05:00:03 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 26 Jan 2017 05:00:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2682) RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2682. --------------------------------- Resolution: Cannot Reproduce > RecoveryIntegrationTestCase.testCrashBeforeCommit did not recover > ----------------------------------------------------------------- > > Key: JBTM-2682 > URL: https://issues.jboss.org/browse/JBTM-2682 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Priority: Minor > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 191.234 sec <<< FAILURE! - in org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase > testCrashBeforeCommit(org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase) Time elapsed: 126.558 sec <<< FAILURE! > java.lang.AssertionError: Recovery failed > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.narayana.rest.integration.test.integration.RecoveryIntegrationTestCase.testCrashBeforeCommit(RecoveryIntegrationTestCase.java:125) > {code} > {code} > javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} > May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > May 17, 2016 7:55:38 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -Dorg.jboss.byteman.verbose, -Dorg.jboss.byteman.transform.all, -javaagent:lib/byteman.jar=script:scripts/CrashBeforeCommit.btm,boot:lib/byteman.jar,listener:true, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 19:55:39,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final > 19:55:40,131 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 19:55:40,513 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting > 19:55:44,456 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 19:55:44,559 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 42) WFLYCLINF0001: Activating Infinispan subsystem. > 19:55:44,636 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 63) WFLYWS0002: Activating WebServices Extension > 19:55:44,659 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.6.Final > 19:55:44,670 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.6.Final > 19:55:44,592 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 49) WFLYJSF0007: Activated the following JSF Implementations: [main] > 19:55:44,619 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 61) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 19:55:45,323 INFO [org.jboss.as.security] (ServerService Thread Pool -- 60) WFLYSEC0002: Activating Security Subsystem > 19:55:45,345 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 1.3.21.Final starting > 19:55:45,381 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 43) WFLYIIOP0001: Activating IIOP Subsystem > 19:55:45,400 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 53) WFLYNAM0001: Activating Naming Subsystem > 19:55:45,622 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final > 19:55:45,580 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final > 19:55:46,430 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 41) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors > 19:55:46,561 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) > 19:55:46,803 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 37) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:55:46,967 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 19:55:47,167 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 19:55:47,181 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 > 19:55:47,136 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 19:55:48,041 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. > 19:55:48,132 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. > 19:55:48,116 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started > 19:55:49,637 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server. > 19:55:50,186 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting > 19:55:50,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 19:55:50,400 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,435 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,436 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,437 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,440 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,442 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,443 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,444 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,445 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,446 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,447 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,456 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,457 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,458 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,459 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,460 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,462 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,463 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,464 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,476 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:55:50,709 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,758 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource > 19:55:50,786 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.narayana.rest.integration.ParticipantResource.commit(org.jboss.narayana.rest.integration.ParticipantInformation) void for rule Kill JVM before commit > 19:55:50,803 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for Kill JVM before commit in class org.jboss.narayana.rest.integration.ParticipantResource > 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,805 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,806 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,807 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,808 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,809 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,810 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,811 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:55:50,863 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /rest-at-coordinator > 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,866 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,867 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,868 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,869 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,870 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,872 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,873 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,874 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,875 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:55:50,890 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: volatile-rest-at-participant > 19:55:51,378 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments > 19:55:51,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant > 19:55:52,131 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final > 19:55:52,379 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 19:55:53,079 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 19:55:53,163 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 19:55:53,226 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221013: Using NIO Journal > 19:55:53,437 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) > 19:55:53,576 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 19:55:53,600 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 19:55:53,636 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 19:55:53,639 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 19:55:55,441 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:55:55,442 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:55:55,445 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:55:57,287 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221007: Server is now live > 19:55:57,288 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] > 19:55:57,479 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA > 19:55:57,585 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:55:57,651 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 19) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:55:57,668 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 19:55:57,669 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.DLQ > 19:55:58,592 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started > 19:55:58,592 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra > 19:55:58,594 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 19:55:58,594 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 19:55:58,974 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 19:55:58,975 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 20406ms - Started 311 of 596 services (387 services are lazy, passive or on-demand) > 19:55:59,088 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content > 19:55:59,141 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 19:55:59,446 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:56:00,376 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 32) WFLYUT0021: Registered web context: /test > 19:56:01,492 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > May 17, 2016 7:56:02 PM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > 19:56:03,832 INFO [org.hibernate.validator.internal.util.Version] (default task-2) HV000001: Hibernate Validator 5.2.4.Final > 19:56:06,698 INFO [stdout] (default task-10) Rule.execute called for Kill JVM before commit_0 > 19:56:06,711 INFO [stdout] (default task-10) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 19:56:06,712 INFO [stdout] (default task-10) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 19:56:06,713 INFO [stdout] (default task-10) Default helper activated > 19:56:06,719 INFO [stdout] (default task-10) calling installed(Kill JVM before commit) for helper classorg.jboss.byteman.rule.helper.Helper > 19:56:06,719 INFO [stdout] (default task-10) Installed rule using default helper : Kill JVM before commit > 19:56:06,720 INFO [stdout] (default task-10) Kill JVM before commit execute > 19:56:06,724 INFO [stdout] (default task-10) rule.debug{Kill JVM before commit} : Killing JVM > May 17, 2016 7:56:07 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, javaVmArguments=-server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, startupTimeoutInSeconds=60, serverConfig=standalone-rts.xml} > May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > May 17, 2016 7:56:07 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dcom.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod=4, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-rts.xml] > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > 19:56:07,928 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final > 19:56:08,509 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 19:56:08,676 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.2.0.CR2 "Kenny" starting > 19:56:14,309 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 19:56:14,332 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final > 19:56:14,341 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final > 19:56:14,542 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 43) WFLYCLINF0001: Activating Infinispan subsystem. > 19:56:14,582 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension > 19:56:14,588 INFO [org.jboss.as.security] (ServerService Thread Pool -- 61) WFLYSEC0002: Activating Security Subsystem > 19:56:14,618 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem > 19:56:14,584 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 19:56:14,779 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 50) WFLYJSF0007: Activated the following JSF Implementations: [main] > 19:56:15,111 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.18.Final > 19:56:15,393 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final) > 19:56:15,397 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 42) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors > 19:56:15,384 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final > 19:56:15,364 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 44) WFLYIIOP0001: Activating IIOP Subsystem > 19:56:15,482 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.21.Final starting > 19:56:15,647 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service > 19:56:16,045 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 19:56:16,348 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing. > 19:56:16,403 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host. > 19:56:16,514 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 19:56:16,585 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 19:56:16,675 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 > 19:56:17,193 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 19:56:18,843 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 19:56:18,844 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 19:56:19,134 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,162 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,163 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,176 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,177 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,178 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,180 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,181 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,182 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,184 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,187 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,188 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,204 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,205 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,207 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,208 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,209 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,210 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,262 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,263 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,264 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication > 19:56:19,519 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: rest-at-participant > 19:56:19,524 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,525 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,526 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,527 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,528 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,540 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,541 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,547 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,548 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,549 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,550 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication > 19:56:19,596 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: volatile-rest-at-participant > 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,616 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.XmlJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.StringTextStar from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,618 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonCollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DocumentProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,619 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonJAXBContextFinder from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,620 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.JaxrsFormProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,621 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,622 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.JAXBElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.core.AcceptHeaderByFileSuffixFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,623 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlRootElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPFilter from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DefaultTextPlain from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,624 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JsonMapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonElementProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.SerializableProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FormUrlEncodedProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,625 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlSeeAlsoProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.json.JettisonXmlTypeProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.FileProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,626 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.InputStreamProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,627 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.MapProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.DataSourceProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.IIOImageProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:19,628 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-2) RESTEASY002205: Adding provider class org.jboss.resteasy.plugins.providers.jaxb.CollectionProvider from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication > 19:56:20,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /rest-at-coordinator > 19:56:20,390 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started > 19:56:20,449 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/deployments > 19:56:20,462 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 19:56:20,780 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 19:56:21,802 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.4.Final (Apache CXF 3.1.5) > 19:56:22,023 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final > 19:56:22,222 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 19:56:22,251 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 19:56:22,469 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 19:56:23,039 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221013: Using NIO Journal > 19:56:23,341 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 19:56:23,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 19:56:23,364 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 19:56:23,366 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 19:56:23,742 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 2) WFLYUT0021: Registered web context: /test > 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:56:24,236 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 19:56:24,239 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221007: Server is now live > 19:56:24,359 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [nodeID=49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] > 19:56:24,368 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 2) AMQ221003: trying to deploy queue jms.queue.DLQ > 19:56:24,519 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA > 19:56:24,602 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 19:56:24,605 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 19:56:24,608 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:56:24,676 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started > 19:56:24,677 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra > 19:56:24,680 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 19:56:24,681 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:56:24,730 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 19:56:25,091 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.2.0.CR2 "Kenny" started in 17840ms - Started 382 of 672 services (398 services are lazy, passive or on-demand) > 19:56:26,692 INFO [org.hibernate.validator.internal.util.Version] (default task-1) HV000001: Hibernate Validator 5.2.4.Final > 19:56:27,484 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:16 > 19:56:27,485 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:56:43,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:56:57,210 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:11,314 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:25,429 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:39,533 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8080/rest-at-participant/0:ffff0a27a81a:-7e7defde:573b6933:18 > 19:57:43,574 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /test > 19:57:43,608 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 52ms > 19:57:43,832 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.1.0.Final-SNAPSHOT/standalone/data/content/be/c7e201753abfa9619059b6feac0ee41834122e/content > 19:57:43,833 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") > May 17, 2016 7:57:43 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 19:57:43,850 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout. > 19:57:43,854 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown' > 19:57:43,877 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 19:57:43,877 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 19:57:43,877 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 19:57:43,897 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 78) AMQ151003: resource adaptor stopped > 19:57:44,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /rest-at-coordinator > 19:57:44,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: rest-at-participant > 19:57:44,705 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: volatile-rest-at-participant > 19:57:44,707 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping > 19:57:44,707 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 19:57:44,714 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 77) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 19:57:44,717 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 74) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory > 19:57:44,879 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-016 [49eb8a8a-1c60-11e6-808c-6f0ad4b2ec40] stopped > 19:57:44,880 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 19:57:44,881 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 19:57:44,882 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.21.Final stopping > 19:57:44,899 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.2.0.CR2 "Kenny" stopped in 43ms > May 17, 2016 7:57:44 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 26 09:55:01 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 26 Jan 2017 09:55:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2838) Please give back IPv6 profile for raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13353986#comment-13353986 ] Gytis Trikleris commented on JBTM-2838: --------------------------------------- [~dsimko], were you testing this quickstart before? IIRC I removed ipv6 profile because it couldn't have worked with hardcoded localhost urls. One example is here: https://github.com/jbosstm/quickstart/blob/master/XTS/raw-xts-api-demo/core/src/main/java/com/jboss/jbosstm/xts/demo/client/BasicClient.java#L313. But most of the wsdl files also have hardcoded localhost values. > Please give back IPv6 profile for raw-xts-api-demo quickstart > ------------------------------------------------------------- > > Key: JBTM-2838 > URL: https://issues.jboss.org/browse/JBTM-2838 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > This profile was removed by https://github.com/jbosstm/quickstart/commit/033d521bc78d80cedb36d1d085635edea6df303f#diff-150d8375c28d69d9eb53270d79389a41L275 > and our IPv6 tests are failing because of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 26 10:53:00 2017 From: issues at jboss.org (Daniel Simko (JIRA)) Date: Thu, 26 Jan 2017 10:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2838) Please give back IPv6 profile for raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13354028#comment-13354028 ] Daniel Simko commented on JBTM-2838: ------------------------------------ Hi [~gytis], yes, we were testing quickstarts before. The example which you provided is not hardcoded. If you loot at https://github.com/jbosstm/quickstart/blob/master/XTS/raw-xts-api-demo/core/src/main/java/com/jboss/jbosstm/xts/demo/client/BasicClient.java#L573 you can see that localhost url is only default value which is not used when system property is set. I didn't investigate the whole magic which we do during running ipv6 tests but I am quite sure that tests were passing before. > Please give back IPv6 profile for raw-xts-api-demo quickstart > ------------------------------------------------------------- > > Key: JBTM-2838 > URL: https://issues.jboss.org/browse/JBTM-2838 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > This profile was removed by https://github.com/jbosstm/quickstart/commit/033d521bc78d80cedb36d1d085635edea6df303f#diff-150d8375c28d69d9eb53270d79389a41L275 > and our IPv6 tests are failing because of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jan 26 11:11:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 26 Jan 2017 11:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2838) Please give back IPv6 profile for raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13354040#comment-13354040 ] Gytis Trikleris commented on JBTM-2838: --------------------------------------- I assume then that those values are coming from here: https://github.com/jbosstm/quickstart/blob/master/XTS/raw-xts-api-demo/war/src/main/webapp/WEB-INF/web.xml. Do you override web.xml in your tests somehow? I'd like to run the test before merging, to make sure it works. Because just by enabling ipv6 profile test fails, because it tries to connect to localhost. > Please give back IPv6 profile for raw-xts-api-demo quickstart > ------------------------------------------------------------- > > Key: JBTM-2838 > URL: https://issues.jboss.org/browse/JBTM-2838 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > This profile was removed by https://github.com/jbosstm/quickstart/commit/033d521bc78d80cedb36d1d085635edea6df303f#diff-150d8375c28d69d9eb53270d79389a41L275 > and our IPv6 tests are failing because of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 27 09:29:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 27 Jan 2017 09:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2843) BlackTie builds failing (including release quickstarts) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2843: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > BlackTie builds failing (including release quickstarts) > ------------------------------------------------------- > > Key: JBTM-2843 > URL: https://issues.jboss.org/browse/JBTM-2843 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > > There are some builds failing consistently: > Main build: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/58/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux/console > Hanging here: > {quote} > jboss.naming.context.java.JmsXA: javax.naming.NameNotFoundException: JmsXA -- service jboss.naming.context.java.JmsXA > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at org.codehaus.stomp.jms.StompConnect.createXAConnectionFactory(StompConnect.java:195) > at org.codehaus.stomp.jms.StompConnect.getXAConnectionFactory(StompConnect.java:84) > at org.codehaus.stomp.jms.StompConnect.assignProtocolConverter(StompConnect.java:64) > at org.codehaus.stomp.tcp.TcpTransportServer.run(TcpTransportServer.java:82) > at java.lang.Thread.run(Thread.java:745) > {quote} > Release quickstarts: > http://narayanaci1.eng.hst.ams2.redhat.com/job/release-narayana-quickstarts/13/console > (similar error and shows > {quote} > [exec] "Services that were unable to start:" => ["jboss.concurrent.ee.context.service.default"], > [exec] "Services that may be the cause:" => [ > [exec] "jboss.iiop-openjdk.naming-service", > [exec] "jboss.iiop-openjdk.orb-service" > {quote} > ) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 27 11:36:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Jan 2017 11:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2844) Compensations EAR archive test fails on JDK9 In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2844: ------------------------------------- Summary: Compensations EAR archive test fails on JDK9 Key: JBTM-2844 URL: https://issues.jboss.org/browse/JBTM-2844 Project: JBoss Transaction Manager Issue Type: Bug Components: Compensations Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next EarArchiveTestLocal test fails with the following error: {code} javax.xml.ws.WebServiceException: java.nio.file.FileSystemNotFoundException at org.jboss.narayana.compensations.integration.archive.EarArchiveTestLocal.(EarArchiveTestLocal.java:44) Caused by: java.nio.file.FileSystemNotFoundException at org.jboss.narayana.compensations.integration.archive.EarArchiveTestLocal.(EarArchiveTestLocal.java:44) {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 27 11:40:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Jan 2017 11:40:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2844) Compensations EAR archive test fails on JDK9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2844: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1123 > Compensations EAR archive test fails on JDK9 > -------------------------------------------- > > Key: JBTM-2844 > URL: https://issues.jboss.org/browse/JBTM-2844 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > EarArchiveTestLocal test fails with the following error: > {code} > javax.xml.ws.WebServiceException: java.nio.file.FileSystemNotFoundException > at org.jboss.narayana.compensations.integration.archive.EarArchiveTestLocal.(EarArchiveTestLocal.java:44) > Caused by: java.nio.file.FileSystemNotFoundException > at org.jboss.narayana.compensations.integration.archive.EarArchiveTestLocal.(EarArchiveTestLocal.java:44) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jan 27 14:01:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 27 Jan 2017 14:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2844) Compensations EAR archive test fails on JDK9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2844: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Compensations EAR archive test fails on JDK9 > -------------------------------------------- > > Key: JBTM-2844 > URL: https://issues.jboss.org/browse/JBTM-2844 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > EarArchiveTestLocal test fails with the following error: > {code} > javax.xml.ws.WebServiceException: java.nio.file.FileSystemNotFoundException > at org.jboss.narayana.compensations.integration.archive.EarArchiveTestLocal.(EarArchiveTestLocal.java:44) > Caused by: java.nio.file.FileSystemNotFoundException > at org.jboss.narayana.compensations.integration.archive.EarArchiveTestLocal.(EarArchiveTestLocal.java:44) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:38:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2736) Enhance error log message on long node name to contain max node name length In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2736: -------------------------------- Fix Version/s: 5.3.5.Final > Enhance error log message on long node name to contain max node name length > --------------------------------------------------------------------------- > > Key: JBTM-2736 > URL: https://issues.jboss.org/browse/JBTM-2736 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Affects Versions: 5.3.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.3.5.Final > > > When maximal node identifier size is exceeded an exception and log message is shown. This message does not contain information what was the maximum of the node identifier length for user could easily adjust his setting based on that info. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:38:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2736) Enhance error log message on long node name to contain max node name length In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2736. ------------------------------- > Enhance error log message on long node name to contain max node name length > --------------------------------------------------------------------------- > > Key: JBTM-2736 > URL: https://issues.jboss.org/browse/JBTM-2736 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Affects Versions: 5.3.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.3.5.Final > > > When maximal node identifier size is exceeded an exception and log message is shown. This message does not contain information what was the maximum of the node identifier length for user could easily adjust his setting based on that info. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:40:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:40:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1957) XTS crash recovery tests fail on IBM JDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-1957: --------------------------------- > XTS crash recovery tests fail on IBM JDK > ---------------------------------------- > > Key: JBTM-1957 > URL: https://issues.jboss.org/browse/JBTM-1957 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 4.17.10 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.0.0.CR2 > > > The XTS crash recovery tests fail on IBM JDK. This seem to be a problem of Arquillian settings. > What I do: > - switch to IBM JDK (JAVA_HOME + PATH) > - export JBOSS_HOME=/home/ochaloup/jboss/jboss-eap-* > - cd XTS/localjunit/crash-recovery-tests > - mvn test -Pxts.integration.tests.profile -Parq -Dtest=com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit > What I get - tests fail with error: > The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:40:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:40:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1957) XTS crash recovery tests fail on IBM JDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1957: -------------------------------- Fix Version/s: 5.0.0.CR2 > XTS crash recovery tests fail on IBM JDK > ---------------------------------------- > > Key: JBTM-1957 > URL: https://issues.jboss.org/browse/JBTM-1957 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 4.17.10 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.0.0.CR2 > > > The XTS crash recovery tests fail on IBM JDK. This seem to be a problem of Arquillian settings. > What I do: > - switch to IBM JDK (JAVA_HOME + PATH) > - export JBOSS_HOME=/home/ochaloup/jboss/jboss-eap-* > - cd XTS/localjunit/crash-recovery-tests > - mvn test -Pxts.integration.tests.profile -Parq -Dtest=com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit > What I get - tests fail with error: > The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:40:01 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 30 Jan 2017 05:40:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2845) REST-AT bridge recovery test hanging because of missing client api In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2845: ------------------------------------- Summary: REST-AT bridge recovery test hanging because of missing client api Key: JBTM-2845 URL: https://issues.jboss.org/browse/JBTM-2845 Project: JBoss Transaction Manager Issue Type: Bug Components: REST Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Blocker Fix For: 5.next REST-AT bridge recovery test is hanging in all environments. It seems that the cause is a change in WildFly modules. Following errors appears in a test log: {code} c (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:103) ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:114) ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.synchronizeParticipantUrlWithCoordinator(RecoveryManager.java:239) ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recreateParticipantInformation(RecoveryManager.java:202) ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recoverParticipants(RecoveryManager.java:153) ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.registerDeserializer(RecoveryManager.java:62) ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.ParticipantsManagerImpl.registerDeserializer(ParticipantsManagerImpl.java:105) ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.(InboundBridgeManager.java:60) ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.getInstance(InboundBridgeManager.java:50) ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.addBridgesToMapping(InboundBridgeRecoveryModule.java:164) ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.periodicWorkSecondPass(InboundBridgeRecoveryModule.java:109) ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" from local module loader @a87f8ec (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:200) ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName0(Native Method) ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName(Class.java:264) ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.newInstance(FactoryFinder.java:113) ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.find(FactoryFinder.java:206) ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:86) ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) ... 12 more {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:41:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1957) XTS crash recovery tests fail on IBM JDK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1957. ------------------------------- Resolution: Done > XTS crash recovery tests fail on IBM JDK > ---------------------------------------- > > Key: JBTM-1957 > URL: https://issues.jboss.org/browse/JBTM-1957 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 4.17.10 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.0.0.CR2 > > > The XTS crash recovery tests fail on IBM JDK. This seem to be a problem of Arquillian settings. > What I do: > - switch to IBM JDK (JAVA_HOME + PATH) > - export JBOSS_HOME=/home/ochaloup/jboss/jboss-eap-* > - cd XTS/localjunit/crash-recovery-tests > - mvn test -Pxts.integration.tests.profile -Parq -Dtest=com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit > What I get - tests fail with error: > The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:41:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 30 Jan 2017 05:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2845) REST-AT bridge recovery test hanging because of missing client api In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2845 started by Gytis Trikleris. --------------------------------------------- > REST-AT bridge recovery test hanging because of missing client api > ------------------------------------------------------------------ > > Key: JBTM-2845 > URL: https://issues.jboss.org/browse/JBTM-2845 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > REST-AT bridge recovery test is hanging in all environments. > It seems that the cause is a change in WildFly modules. Following errors appears in a test log: > {code} > c (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:103) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:114) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.synchronizeParticipantUrlWithCoordinator(RecoveryManager.java:239) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recreateParticipantInformation(RecoveryManager.java:202) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recoverParticipants(RecoveryManager.java:153) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.registerDeserializer(RecoveryManager.java:62) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.ParticipantsManagerImpl.registerDeserializer(ParticipantsManagerImpl.java:105) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.(InboundBridgeManager.java:60) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.getInstance(InboundBridgeManager.java:50) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.addBridgesToMapping(InboundBridgeRecoveryModule.java:164) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.periodicWorkSecondPass(InboundBridgeRecoveryModule.java:109) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" from local module loader @a87f8ec (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:200) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName0(Native Method) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName(Class.java:264) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.newInstance(FactoryFinder.java:113) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.find(FactoryFinder.java:206) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:86) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) ... 12 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:42:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:42:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2428) JTS client side transaction context seems not being propagated to EAP server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2428: --------------------------------- > JTS client side transaction context seems not being propagated to EAP server > ---------------------------------------------------------------------------- > > Key: JBTM-2428 > URL: https://issues.jboss.org/browse/JBTM-2428 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.1.1 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > It seems that transaction context is not propagated when JTS transaction is started on client. > This was working for EAP 6.4 where iiop corba implementation was used. The testing client is based on guide [1]. > The call from client to server via IIOP [4] works fine but when I'm trying to start transaction on client side and then expecting being propagated to server, server proclaims that there is no txn in the context. > This is how the orb is set up [2] > This is how the transaction is started [3] > This is how the remote call on ejb app server is done [4] > [1] https://developer.jboss.org/wiki/TransactionPropagationWithJBoss > [2] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/base/TestBaseOneServer.java;h=ed9b30aabe11fdb5f3290763beb167182a22a819;hb=HEAD#l530 > [3] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/base/TestBaseOneServer.java;h=ed9b30aabe11fdb5f3290763beb167182a22a819;hb=HEAD#l511 > [4] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/client/TxUtil.java;h=5dd55e22a52df6fd3845b1de5134f436f721a437;hb=HEAD#l69 > [5] [com.arjuna.ats.jts] (main) ARJUNA022251: The ORBManager is already associated with an ORB/OA. > FINE [javax.enterprise.resource.corba._DEFAULT_.rpc.protocol] (main) "IOP01600014: (BAD_INV_ORDER) Cannot access this attribute or method at this point": org.omg.CORBA.BAD_INV_ORDER: vmcid: OMG minor code: 14 completed: No > -- or -- > FINE [javax.enterprise.resource.corba._CORBA_.rpc.presentation] (main) "IOP00110227: (BAD_PARAM) ORBDynamicStubFactoryFactoryClass property had value com.sun.corba.se.impl.presentation.rmi.bcel.StubFactoryFactoryBCELImpl, which could not be loaded by the ORB ClassLoader": org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 227 completed: No -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:42:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:42:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2428) JTS client side transaction context seems not being propagated to EAP server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2428. ------------------------------- Resolution: Migrated to another ITS > JTS client side transaction context seems not being propagated to EAP server > ---------------------------------------------------------------------------- > > Key: JBTM-2428 > URL: https://issues.jboss.org/browse/JBTM-2428 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.1.1 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > It seems that transaction context is not propagated when JTS transaction is started on client. > This was working for EAP 6.4 where iiop corba implementation was used. The testing client is based on guide [1]. > The call from client to server via IIOP [4] works fine but when I'm trying to start transaction on client side and then expecting being propagated to server, server proclaims that there is no txn in the context. > This is how the orb is set up [2] > This is how the transaction is started [3] > This is how the remote call on ejb app server is done [4] > [1] https://developer.jboss.org/wiki/TransactionPropagationWithJBoss > [2] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/base/TestBaseOneServer.java;h=ed9b30aabe11fdb5f3290763beb167182a22a819;hb=HEAD#l530 > [3] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/base/TestBaseOneServer.java;h=ed9b30aabe11fdb5f3290763beb167182a22a819;hb=HEAD#l511 > [4] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/client/TxUtil.java;h=5dd55e22a52df6fd3845b1de5134f436f721a437;hb=HEAD#l69 > [5] [com.arjuna.ats.jts] (main) ARJUNA022251: The ORBManager is already associated with an ORB/OA. > FINE [javax.enterprise.resource.corba._DEFAULT_.rpc.protocol] (main) "IOP01600014: (BAD_INV_ORDER) Cannot access this attribute or method at this point": org.omg.CORBA.BAD_INV_ORDER: vmcid: OMG minor code: 14 completed: No > -- or -- > FINE [javax.enterprise.resource.corba._CORBA_.rpc.presentation] (main) "IOP00110227: (BAD_PARAM) ORBDynamicStubFactoryFactoryClass property had value com.sun.corba.se.impl.presentation.rmi.bcel.StubFactoryFactoryBCELImpl, which could not be loaded by the ORB ClassLoader": org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 227 completed: No -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:42:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:42:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2759) Static code analysis: potential lock collisions BaseTransactionManagerDelegate#findLock - interned string used as a lock In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2759. ------------------------------- > Static code analysis: potential lock collisions BaseTransactionManagerDelegate#findLock - interned string used as a lock > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2759 > URL: https://issues.jboss.org/browse/JBTM-2759 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.3.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.3.5.Final > > > _CID-17577_: Bad choice of lock object - Potential lock collisions > at class {{BaseTransactionManagerDelegate}}[9] at method {{findLock}}. > {quote} > string_literal: The string literal "__LOCKS_MAP" is an interned string. > ? interned_string_lock: Locking on an interned string can cause unexpected locking collisions with third party code. > ? Instead of using "__LOCKS_MAP" as a lock, create a final field of type Object which is only used as a lock. > {quote} > Explanation at description of JBTM-2758 > [9] https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/integration/src/main/java/com/arjuna/ats/jbossatx/BaseTransactionManagerDelegate.java#L350 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:42:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:42:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2758) Static code analysis: potential lock collisions FileProcessId#getpid - interned string used as a lock In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2758. ------------------------------- > Static code analysis: potential lock collisions FileProcessId#getpid - interned string used as a lock > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2758 > URL: https://issues.jboss.org/browse/JBTM-2758 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.3.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.3.5.Final > > > _CID-17581_: Bad choice of lock object - Potential lock collisions > at class `FileProcessId`[6] method `getpid` with error message > {quote} > Interned string as a lock may cause deadlocks or performance problems if a library also uses the interned string as a lock. > ?string_literal: The string literal "0x" is an interned string. > ?interned_string_lock: Locking on an interned string can cause unexpected locking collisions with third party code. > ?Instead of using "0x" as a lock, create a final field of type Object which is only used as a lock. > {quote} > See Java examples at Coverity page [7]. The explanation there is that > ? String literals are centrally interned and could also be locked on by a > library, causing you to potentially have deadlocks or lock collisions > with other code. > There are several places [8] on net when searching for `java synchronzation on strings`. > [6] https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/utils/FileProcessId.java#L63 > [7] https://ondemand.coverity.com/reference/7.6.1/en/coverity#N5069A > [8] http://www.javalobby.org/java/forums/t96352.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 05:42:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 05:42:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2701) Allow in-flowed XAR to be scanned for Xid more than once between scans of the recovery system In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2701. ------------------------------- > Allow in-flowed XAR to be scanned for Xid more than once between scans of the recovery system > --------------------------------------------------------------------------------------------- > > Key: JBTM-2701 > URL: https://issues.jboss.org/browse/JBTM-2701 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 4.17.33 > Environment: JBoss EA P6.4.8 > Reporter: Tom Ross > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.2.21.Final, 5.3.5.Final > > > The JCA getNewXAResource() call can only bring forward the scanning of XAResources once per recovery pass (i.e. once every two minutes per default). > The following signature can be observed in the log file: > {noformat} > 2016-06-28 12:18:33,068 TRACE [com.arjuna.ats.jta] (EJB default - 98) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:null, txid:< formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra >, heuristic: TwoPhaseOutcome.FINISH_OK, product: com/ecim/1.0, jndiName: java:/eis/custom-ra com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 64fa6d0e >, record id=0:ffff0af7f663:ba85fe7:57714e42:7058f3 > 2016-06-28 12:18:33,068 WARN [com.arjuna.ats.jta] (EJB default - 98) ARJUNA016038: No XAResource to recover < formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra > > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) BasicAction.doCommit for 0:ffff0af7f663:ba85fe7:57714e42:705303 received TwoPhaseOutcome.FINISH_ERROR from class com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) RecordList::insert(RecordList: empty) : appending /StateManager/AbstractRecord/XAResourceRecord for 0:ffff0af7f663:ba85fe7:57714e42:7058f3 > {noformat} > It would be useful to allow the getNewXAResource() call to re-scan XAR in case it is called in between recovery scans multiple times. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 06:05:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 06:05:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2845) REST-AT bridge recovery test hanging because of missing client api In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13354757#comment-13354757 ] Tom Jenkinson commented on JBTM-2845: ------------------------------------- Is it expected to be using jersey in the app server? > REST-AT bridge recovery test hanging because of missing client api > ------------------------------------------------------------------ > > Key: JBTM-2845 > URL: https://issues.jboss.org/browse/JBTM-2845 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > REST-AT bridge recovery test is hanging in all environments. > It seems that the cause is a change in WildFly modules. Following errors appears in a test log: > {code} > c (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:103) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:114) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.synchronizeParticipantUrlWithCoordinator(RecoveryManager.java:239) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recreateParticipantInformation(RecoveryManager.java:202) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recoverParticipants(RecoveryManager.java:153) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.registerDeserializer(RecoveryManager.java:62) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.ParticipantsManagerImpl.registerDeserializer(ParticipantsManagerImpl.java:105) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.(InboundBridgeManager.java:60) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.getInstance(InboundBridgeManager.java:50) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.addBridgesToMapping(InboundBridgeRecoveryModule.java:164) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.periodicWorkSecondPass(InboundBridgeRecoveryModule.java:109) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" from local module loader @a87f8ec (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:200) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName0(Native Method) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName(Class.java:264) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.newInstance(FactoryFinder.java:113) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.find(FactoryFinder.java:206) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:86) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) ... 12 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 06:26:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 30 Jan 2017 06:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2845) REST-AT bridge recovery test hanging because of missing client api In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13354764#comment-13354764 ] Gytis Trikleris commented on JBTM-2845: --------------------------------------- No, it's just a default fall back if there is no other implementation available. > REST-AT bridge recovery test hanging because of missing client api > ------------------------------------------------------------------ > > Key: JBTM-2845 > URL: https://issues.jboss.org/browse/JBTM-2845 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > REST-AT bridge recovery test is hanging in all environments. > It seems that the cause is a change in WildFly modules. Following errors appears in a test log: > {code} > c (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:103) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:114) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.synchronizeParticipantUrlWithCoordinator(RecoveryManager.java:239) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recreateParticipantInformation(RecoveryManager.java:202) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recoverParticipants(RecoveryManager.java:153) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.registerDeserializer(RecoveryManager.java:62) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.ParticipantsManagerImpl.registerDeserializer(ParticipantsManagerImpl.java:105) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.(InboundBridgeManager.java:60) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.getInstance(InboundBridgeManager.java:50) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.addBridgesToMapping(InboundBridgeRecoveryModule.java:164) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.periodicWorkSecondPass(InboundBridgeRecoveryModule.java:109) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" from local module loader @a87f8ec (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:200) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName0(Native Method) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName(Class.java:264) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.newInstance(FactoryFinder.java:113) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.find(FactoryFinder.java:206) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:86) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) ... 12 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 06:26:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 30 Jan 2017 06:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2845) REST-AT bridge recovery test hanging because of missing client api In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13354765#comment-13354765 ] Gytis Trikleris commented on JBTM-2845: --------------------------------------- This commit seems to be the cause https://github.com/wildfly/wildfly/commit/f22478a4bba109d7c4cf55aef935cf9a8f2f4857 > REST-AT bridge recovery test hanging because of missing client api > ------------------------------------------------------------------ > > Key: JBTM-2845 > URL: https://issues.jboss.org/browse/JBTM-2845 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > REST-AT bridge recovery test is hanging in all environments. > It seems that the cause is a change in WildFly modules. Following errors appears in a test log: > {code} > c (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:103) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:114) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.synchronizeParticipantUrlWithCoordinator(RecoveryManager.java:239) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recreateParticipantInformation(RecoveryManager.java:202) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recoverParticipants(RecoveryManager.java:153) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.registerDeserializer(RecoveryManager.java:62) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.ParticipantsManagerImpl.registerDeserializer(ParticipantsManagerImpl.java:105) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.(InboundBridgeManager.java:60) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.getInstance(InboundBridgeManager.java:50) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.addBridgesToMapping(InboundBridgeRecoveryModule.java:164) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.periodicWorkSecondPass(InboundBridgeRecoveryModule.java:109) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" from local module loader @a87f8ec (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:200) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName0(Native Method) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName(Class.java:264) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.newInstance(FactoryFinder.java:113) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.find(FactoryFinder.java:206) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:86) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) ... 12 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 06:57:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 30 Jan 2017 06:57:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2845) REST-AT bridge recovery test hanging because of missing client api In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13354785#comment-13354785 ] Tom Jenkinson commented on JBTM-2845: ------------------------------------- Downgrade of RestEASY may need us to revert https://issues.jboss.org/browse/JBTM-2714 ? > REST-AT bridge recovery test hanging because of missing client api > ------------------------------------------------------------------ > > Key: JBTM-2845 > URL: https://issues.jboss.org/browse/JBTM-2845 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > REST-AT bridge recovery test is hanging in all environments. > It seems that the cause is a change in WildFly modules. Following errors appears in a test log: > {code} > c (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:103) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:114) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.synchronizeParticipantUrlWithCoordinator(RecoveryManager.java:239) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recreateParticipantInformation(RecoveryManager.java:202) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recoverParticipants(RecoveryManager.java:153) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.registerDeserializer(RecoveryManager.java:62) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.ParticipantsManagerImpl.registerDeserializer(ParticipantsManagerImpl.java:105) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.(InboundBridgeManager.java:60) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.getInstance(InboundBridgeManager.java:50) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.addBridgesToMapping(InboundBridgeRecoveryModule.java:164) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.periodicWorkSecondPass(InboundBridgeRecoveryModule.java:109) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" from local module loader @a87f8ec (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:200) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName0(Native Method) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName(Class.java:264) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.newInstance(FactoryFinder.java:113) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.find(FactoryFinder.java:206) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:86) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) ... 12 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jan 30 08:34:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 30 Jan 2017 08:34:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2845) REST-AT bridge recovery test hanging because of missing client api In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #62 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > REST-AT bridge recovery test hanging because of missing client api > ------------------------------------------------------------------ > > Key: JBTM-2845 > URL: https://issues.jboss.org/browse/JBTM-2845 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > REST-AT bridge recovery test is hanging in all environments. > It seems that the cause is a change in WildFly modules. Following errors appears in a test log: > {code} > c (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:103) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:114) > ^[[0m^[[31m11:32:31,304 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.synchronizeParticipantUrlWithCoordinator(RecoveryManager.java:239) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recreateParticipantInformation(RecoveryManager.java:202) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.recoverParticipants(RecoveryManager.java:153) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.RecoveryManager.registerDeserializer(RecoveryManager.java:62) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.integration.ParticipantsManagerImpl.registerDeserializer(ParticipantsManagerImpl.java:105) > ^[[0m^[[31m11:32:31,305 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.(InboundBridgeManager.java:60) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeManager.getInstance(InboundBridgeManager.java:50) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.addBridgesToMapping(InboundBridgeRecoveryModule.java:164) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at org.jboss.narayana.rest.bridge.inbound.InboundBridgeRecoveryModule.periodicWorkSecondPass(InboundBridgeRecoveryModule.java:109) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > ^[[0m^[[31m11:32:31,306 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder from [Module "javax.ws.rs.api" from local module loader @a87f8ec (finder: local module finder @5443d039 (roots: /Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/Users/gytis/Workspace/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:200) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > ^[[0m^[[31m11:32:31,307 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName0(Native Method) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at java.lang.Class.forName(Class.java:264) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.newInstance(FactoryFinder.java:113) > ^[[0m^[[31m11:32:31,308 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.FactoryFinder.find(FactoryFinder.java:206) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:86) > ^[[0m^[[31m11:32:31,309 ERROR [stderr] (Periodic Recovery) ... 12 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 31 09:32:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 31 Jan 2017 09:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2838) Please give back IPv6 profile for raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13355628#comment-13355628 ] Tom Jenkinson commented on JBTM-2838: ------------------------------------- Sure, sounds OK to me. > Please give back IPv6 profile for raw-xts-api-demo quickstart > ------------------------------------------------------------- > > Key: JBTM-2838 > URL: https://issues.jboss.org/browse/JBTM-2838 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > This profile was removed by https://github.com/jbosstm/quickstart/commit/033d521bc78d80cedb36d1d085635edea6df303f#diff-150d8375c28d69d9eb53270d79389a41L275 > and our IPv6 tests are failing because of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 31 10:04:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 31 Jan 2017 10:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2838) Please give back IPv6 profile for raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #187 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Please give back IPv6 profile for raw-xts-api-demo quickstart > ------------------------------------------------------------- > > Key: JBTM-2838 > URL: https://issues.jboss.org/browse/JBTM-2838 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > This profile was removed by https://github.com/jbosstm/quickstart/commit/033d521bc78d80cedb36d1d085635edea6df303f#diff-150d8375c28d69d9eb53270d79389a41L275 > and our IPv6 tests are failing because of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 31 10:43:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 31 Jan 2017 10:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2838) Please give back IPv6 profile for raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2838: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Please give back IPv6 profile for raw-xts-api-demo quickstart > ------------------------------------------------------------- > > Key: JBTM-2838 > URL: https://issues.jboss.org/browse/JBTM-2838 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > This profile was removed by https://github.com/jbosstm/quickstart/commit/033d521bc78d80cedb36d1d085635edea6df303f#diff-150d8375c28d69d9eb53270d79389a41L275 > and our IPv6 tests are failing because of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jan 31 10:43:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 31 Jan 2017 10:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2838) Please give back IPv6 profile for raw-xts-api-demo quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2838: -------------------------------- Fix Version/s: 5.next > Please give back IPv6 profile for raw-xts-api-demo quickstart > ------------------------------------------------------------- > > Key: JBTM-2838 > URL: https://issues.jboss.org/browse/JBTM-2838 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: XTS > Affects Versions: 5.5.0.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > This profile was removed by https://github.com/jbosstm/quickstart/commit/033d521bc78d80cedb36d1d085635edea6df303f#diff-150d8375c28d69d9eb53270d79389a41L275 > and our IPv6 tests are failing because of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)