From issues at jboss.org Fri Jan 2 05:36:30 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 2 Jan 2015 05:36:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029688#comment-13029688 ] RH Bugzilla Integration commented on JBTM-2308: ----------------------------------------------- Kabir Khan changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from POST to MODIFIED > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.0.5 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Jan 3 11:00:34 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 3 Jan 2015 11:00:34 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2318) Too verbose startup? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029733#comment-13029733 ] Michael Musgrove commented on JBTM-2318: ---------------------------------------- Can we also add the following to the list of messages (relating to recovery) that should be demoted to debug level: {code} ARJUNA012324: Start RecoveryActivators ARJUNA012343: RecoveryManagerImple is ready. Socket listener is turned off. ARJUNA012296: ExpiredEntryMonitor running at {0} ARJUNA012332: Failed to establish connection to server ARJUNA012304: Removing old transaction status manager item {0} {code} > Too verbose startup? > -------------------- > > Key: JBTM-2318 > URL: https://issues.jboss.org/browse/JBTM-2318 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > > At startup of the most basic example we see ... > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService > INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem > INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start > INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > There's a separate conversation to be had about whether the INFO should be there (DEBUG maybe?) but ignoring those why do we print the other lines at all? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 01:02:29 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 5 Jan 2015 01:02:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2321) apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029742#comment-13029742 ] Amos Feng commented on JBTM-2321: --------------------------------- I have installed the dependencies manually and it should work on the sansa but it still needs to update the CI script. > apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build > ------------------------------------------------------------------------------------- > > Key: JBTM-2321 > URL: https://issues.jboss.org/browse/JBTM-2321 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-quickstarts/139 > {code} > [ERROR] Failed to execute goal on project blacktie-C: Could not resolve dependencies for project org.jboss.narayana.blacktie:blacktie-C:pom:5.0.5.Final-SNAPSHOT: Could not find artifact apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 in jbossThirdParty (https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/) -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 03:59:30 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 5 Jan 2015 03:59:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2321) apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng resolved JBTM-2321. ----------------------------- Resolution: Done I just update the job config to get the blacktie thirdparty dependencies of centos70x64 > apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build > ------------------------------------------------------------------------------------- > > Key: JBTM-2321 > URL: https://issues.jboss.org/browse/JBTM-2321 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-quickstarts/139 > {code} > [ERROR] Failed to execute goal on project blacktie-C: Could not resolve dependencies for project org.jboss.narayana.blacktie:blacktie-C:pom:5.0.5.Final-SNAPSHOT: Could not find artifact apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 in jbossThirdParty (https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/) -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 05:45:30 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 5 Jan 2015 05:45:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by coordinator in CloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris reopened JBTM-2194: ----------------------------------- Happened again on CI: http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/723/PROFILE=XTS,jdk=jdk7.latest,label=linux > Activity cancelled by coordinator in CloseTest > ---------------------------------------------- > > Key: JBTM-2194 > URL: https://issues.jboss.org/browse/JBTM-2194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > Repeating CI job: http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie-JBTM/job/JBTM-2194/ > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.CloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! > testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) > {code} > {code} > 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war > 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war > 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test > 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter > 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called > 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called > 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called > 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 > 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) Default helper activated > 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter > 18:45:39,135 INFO [stdout] (default task-16) create counter execute > 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 > 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 > 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl > 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 > 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called > 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute > 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting > 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 > 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called > 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking > 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken > 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake > 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity > 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl > 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 > 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute > 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter > 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called > 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called > 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated > 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test > 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms > 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 05:50:29 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 5 Jan 2015 05:50:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2316) Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2316: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool > ------------------------------------------------------------------------------------------------- > > Key: JBTM-2316 > URL: https://issues.jboss.org/browse/JBTM-2316 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > I can't see the transactional driver or JTAx stuff in the code-coverage report and I also don't think its worth aggregating in the performance test harness into the coverage numbers. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 06:16:29 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 5 Jan 2015 06:16:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by coordinator in CloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2194: ---------------------------------- Fix Version/s: 5.0.5 > Activity cancelled by coordinator in CloseTest > ---------------------------------------------- > > Key: JBTM-2194 > URL: https://issues.jboss.org/browse/JBTM-2194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.x.y > > > Repeating CI job: http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie-JBTM/job/JBTM-2194/ > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.CloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! > testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) > {code} > {code} > 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war > 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war > 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test > 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter > 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called > 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called > 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called > 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 > 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) Default helper activated > 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter > 18:45:39,135 INFO [stdout] (default task-16) create counter execute > 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 > 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 > 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl > 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 > 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called > 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute > 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting > 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 > 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called > 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking > 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken > 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake > 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity > 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl > 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 > 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute > 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter > 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called > 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called > 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated > 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test > 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms > 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 06:16:29 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 5 Jan 2015 06:16:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by coordinator in CloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2194: ---------------------------------- Fix Version/s: 5.x.y (was: 5.0.5) > Activity cancelled by coordinator in CloseTest > ---------------------------------------------- > > Key: JBTM-2194 > URL: https://issues.jboss.org/browse/JBTM-2194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.x.y > > > Repeating CI job: http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie-JBTM/job/JBTM-2194/ > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.CloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! > testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) > {code} > {code} > 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war > 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war > 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test > 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter > 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called > 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called > 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called > 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 > 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) Default helper activated > 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter > 18:45:39,135 INFO [stdout] (default task-16) create counter execute > 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 > 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 > 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl > 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 > 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called > 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute > 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting > 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 > 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called > 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking > 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken > 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake > 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity > 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl > 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 > 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute > 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter > 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called > 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called > 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated > 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test > 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms > 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 06:18:29 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 5 Jan 2015 06:18:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by coordinator in CloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2194: ---------------------------------- Description: {code} ------------------------------------------------------------------------------- Test set: com.arjuna.wstx.tests.arq.ba.CloseTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! com.arjuna.wst.TransactionRolledBackException: null at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) {code} {code} 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper 18:45:39,124 INFO [stdout] (default task-16) Default helper activated 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter 18:45:39,135 INFO [stdout] (default task-16) create counter execute 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war")  {code} was: Repeating CI job: http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie-JBTM/job/JBTM-2194/ {code} ------------------------------------------------------------------------------- Test set: com.arjuna.wstx.tests.arq.ba.CloseTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! com.arjuna.wst.TransactionRolledBackException: null at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) {code} {code} 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper 18:45:39,124 INFO [stdout] (default task-16) Default helper activated 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter 18:45:39,135 INFO [stdout] (default task-16) create counter execute 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war")  {code} > Activity cancelled by coordinator in CloseTest > ---------------------------------------------- > > Key: JBTM-2194 > URL: https://issues.jboss.org/browse/JBTM-2194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.x.y > > > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.CloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! > testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) > {code} > {code} > 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war > 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war > 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test > 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter > 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called > 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called > 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called > 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 > 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) Default helper activated > 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter > 18:45:39,135 INFO [stdout] (default task-16) create counter execute > 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 > 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 > 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl > 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 > 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called > 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute > 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting > 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 > 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called > 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking > 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken > 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake > 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity > 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl > 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 > 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute > 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter > 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called > 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called > 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated > 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test > 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms > 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 06:18:29 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 5 Jan 2015 06:18:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by coordinator in CloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2194: ---------------------------------- Comment: was deleted (was: http://172.17.131.2/view/Status/job/narayana/550/PROFILE=XTS,jdk=jdk7.latest,label=linux/) > Activity cancelled by coordinator in CloseTest > ---------------------------------------------- > > Key: JBTM-2194 > URL: https://issues.jboss.org/browse/JBTM-2194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.x.y > > > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.CloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! > testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) > {code} > {code} > 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war > 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war > 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test > 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter > 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called > 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called > 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called > 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 > 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) Default helper activated > 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter > 18:45:39,135 INFO [stdout] (default task-16) create counter execute > 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 > 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 > 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl > 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 > 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called > 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute > 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting > 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 > 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called > 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking > 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken > 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake > 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity > 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl > 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 > 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute > 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter > 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called > 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called > 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated > 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test > 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms > 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 11:35:29 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 5 Jan 2015 11:35:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2316) Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029962#comment-13029962 ] Michael Musgrove commented on JBTM-2316: ---------------------------------------- I have left the performance test harness since it is useful to know that it works (otherwise we cannot trust the performance figures). > Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool > ------------------------------------------------------------------------------------------------- > > Key: JBTM-2316 > URL: https://issues.jboss.org/browse/JBTM-2316 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > I can't see the transactional driver or JTAx stuff in the code-coverage report and I also don't think its worth aggregating in the performance test harness into the coverage numbers. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 16:28:29 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 5 Jan 2015 16:28:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2318) Too verbose startup? In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030038#comment-13030038 ] Mark Little commented on JBTM-2318: ----------------------------------- Yes, although there appear to be a couple of bugs in the 12296 and 12304 messaging anyway - the {0} should be replaced with the value of some instance variable and that doesn't appear to be happening. So even if they're demoted, they should still be fixed. > Too verbose startup? > -------------------- > > Key: JBTM-2318 > URL: https://issues.jboss.org/browse/JBTM-2318 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > > At startup of the most basic example we see ... > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService > INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem > INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185 > Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start > INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > There's a separate conversation to be had about whether the INFO should be there (DEBUG maybe?) but ignoring those why do we print the other lines at all? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 7 07:59:29 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 7 Jan 2015 07:59:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2280) alternative to JNDI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030506#comment-13030506 ] Michael Musgrove commented on JBTM-2280: ---------------------------------------- I have updated the ceylon code to use Toms changes that allow the user to provide the datasource (I will raise a ceylon PR after we do the next narayana release). This change means that the ceylon user no longer needs to register his datasources via JNDI. > alternative to JNDI > ------------------- > > Key: JBTM-2280 > URL: https://issues.jboss.org/browse/JBTM-2280 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gavin King > Assignee: Tom Jenkinson > > So far four (4) different people have tried and failed to get JBoss Transactions working in a Ceylon environment (i.e. JBoss Modules, essentially). The basic problem is that the TM has a totally spurious dependence on JNDI as the source of its transactional resources. Since JCA is neither defined nor available outside a Java EE environment, this forces anyone trying to use the TM outside of the application server to write their own nasty code depending on some really internal-looking APIs that basically sets up a JNDI-bound proxied datasource where both the TM and the application can find it. In principle this is sorta-straightforward (except for the internal-looking APIs). However, it means that most of the code in `ceylon.transaction` is actually about connection management and setting up JNDI-bound datasources. > Sadly it turns out that, in the context of JBoss Modules, even just getting a JNDI server on the right classloader has proved to be a task so difficult that four reasonably competent developers including myself and other folks who are much better programmers than me have failed at it. I'm sure it's remotely _possible_, and I'm sure that if I weren't using JBoss Modules it would be quite easy. But I'm also sure that it simply shouldn't be necessary. JNDI has nothing to do with transactions and is a distraction here. JNDI is this totally stringly-typed rubbish thing designed in the Clinton era as an abstraction of LDAP by folks who had never heard that Java has static types. Yeah, sure, it continues its zombie existence at the heart of the EE standards, even after we remembered that Java has static types in EE 6, but it just has no place in modern APIs. Other libraries like Hibernate, Spring, etc always offer alternative approaches with no dependence to JNDI. > IMO, what the TM _should_ do is offer an API that lets me hand it an instance of `XADataSource` (it doesn't care where that comes from) and hands my back an instance of `DataSource` that I can use to obtain transaction-bound connections. There is no reason, AFAICT, to involve JNDI in this at all. > XADataSource xads = youJustDontNeedToCare(); > DataSource ds = narayana.registerDataSource(xads); > Or something like that. Of course I'm sure I'm missing some subtleties here. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 7 08:32:29 2015 From: issues at jboss.org (Stephane Epardaud (JIRA)) Date: Wed, 7 Jan 2015 08:32:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2280) alternative to JNDI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030530#comment-13030530 ] Stephane Epardaud commented on JBTM-2280: ----------------------------------------- So this was closed and then fixed? > alternative to JNDI > ------------------- > > Key: JBTM-2280 > URL: https://issues.jboss.org/browse/JBTM-2280 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gavin King > Assignee: Tom Jenkinson > > So far four (4) different people have tried and failed to get JBoss Transactions working in a Ceylon environment (i.e. JBoss Modules, essentially). The basic problem is that the TM has a totally spurious dependence on JNDI as the source of its transactional resources. Since JCA is neither defined nor available outside a Java EE environment, this forces anyone trying to use the TM outside of the application server to write their own nasty code depending on some really internal-looking APIs that basically sets up a JNDI-bound proxied datasource where both the TM and the application can find it. In principle this is sorta-straightforward (except for the internal-looking APIs). However, it means that most of the code in `ceylon.transaction` is actually about connection management and setting up JNDI-bound datasources. > Sadly it turns out that, in the context of JBoss Modules, even just getting a JNDI server on the right classloader has proved to be a task so difficult that four reasonably competent developers including myself and other folks who are much better programmers than me have failed at it. I'm sure it's remotely _possible_, and I'm sure that if I weren't using JBoss Modules it would be quite easy. But I'm also sure that it simply shouldn't be necessary. JNDI has nothing to do with transactions and is a distraction here. JNDI is this totally stringly-typed rubbish thing designed in the Clinton era as an abstraction of LDAP by folks who had never heard that Java has static types. Yeah, sure, it continues its zombie existence at the heart of the EE standards, even after we remembered that Java has static types in EE 6, but it just has no place in modern APIs. Other libraries like Hibernate, Spring, etc always offer alternative approaches with no dependence to JNDI. > IMO, what the TM _should_ do is offer an API that lets me hand it an instance of `XADataSource` (it doesn't care where that comes from) and hands my back an instance of `DataSource` that I can use to obtain transaction-bound connections. There is no reason, AFAICT, to involve JNDI in this at all. > XADataSource xads = youJustDontNeedToCare(); > DataSource ds = narayana.registerDataSource(xads); > Or something like that. Of course I'm sure I'm missing some subtleties here. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 7 09:54:29 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 7 Jan 2015 09:54:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2325) Allow the user to provide a reference to an XADataSource for Transactional Driver In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2325: ----------------------------------- Summary: Allow the user to provide a reference to an XADataSource for Transactional Driver Key: JBTM-2325 URL: https://issues.jboss.org/browse/JBTM-2325 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Transaction Core Affects Versions: 5.0.4 Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.5 Certain environments have class loader constraints that do not let the direct recoverable connection load the users configured XADataSource. It is therefore necessary to provide an implementation that can be passed by reference. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 7 10:00:31 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 7 Jan 2015 10:00:31 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2280) alternative to JNDI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030567#comment-13030567 ] Tom Jenkinson commented on JBTM-2280: ------------------------------------- Hi Stephane, I added a feature over here JBTM-2325 it will be in the next version of Narayana - hope it works for you. I created a forum entry over here if you would like to discuss it further: https://developer.jboss.org/message/909177#909177 Thanks, Tom > alternative to JNDI > ------------------- > > Key: JBTM-2280 > URL: https://issues.jboss.org/browse/JBTM-2280 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gavin King > Assignee: Tom Jenkinson > > So far four (4) different people have tried and failed to get JBoss Transactions working in a Ceylon environment (i.e. JBoss Modules, essentially). The basic problem is that the TM has a totally spurious dependence on JNDI as the source of its transactional resources. Since JCA is neither defined nor available outside a Java EE environment, this forces anyone trying to use the TM outside of the application server to write their own nasty code depending on some really internal-looking APIs that basically sets up a JNDI-bound proxied datasource where both the TM and the application can find it. In principle this is sorta-straightforward (except for the internal-looking APIs). However, it means that most of the code in `ceylon.transaction` is actually about connection management and setting up JNDI-bound datasources. > Sadly it turns out that, in the context of JBoss Modules, even just getting a JNDI server on the right classloader has proved to be a task so difficult that four reasonably competent developers including myself and other folks who are much better programmers than me have failed at it. I'm sure it's remotely _possible_, and I'm sure that if I weren't using JBoss Modules it would be quite easy. But I'm also sure that it simply shouldn't be necessary. JNDI has nothing to do with transactions and is a distraction here. JNDI is this totally stringly-typed rubbish thing designed in the Clinton era as an abstraction of LDAP by folks who had never heard that Java has static types. Yeah, sure, it continues its zombie existence at the heart of the EE standards, even after we remembered that Java has static types in EE 6, but it just has no place in modern APIs. Other libraries like Hibernate, Spring, etc always offer alternative approaches with no dependence to JNDI. > IMO, what the TM _should_ do is offer an API that lets me hand it an instance of `XADataSource` (it doesn't care where that comes from) and hands my back an instance of `DataSource` that I can use to obtain transaction-bound connections. There is no reason, AFAICT, to involve JNDI in this at all. > XADataSource xads = youJustDontNeedToCare(); > DataSource ds = narayana.registerDataSource(xads); > Or something like that. Of course I'm sure I'm missing some subtleties here. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 7 10:04:29 2015 From: issues at jboss.org (Stephane Epardaud (JIRA)) Date: Wed, 7 Jan 2015 10:04:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2280) alternative to JNDI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030570#comment-13030570 ] Stephane Epardaud commented on JBTM-2280: ----------------------------------------- Well this sounds great, I hope we can validate that it fixes our specific problem. > alternative to JNDI > ------------------- > > Key: JBTM-2280 > URL: https://issues.jboss.org/browse/JBTM-2280 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gavin King > Assignee: Tom Jenkinson > > So far four (4) different people have tried and failed to get JBoss Transactions working in a Ceylon environment (i.e. JBoss Modules, essentially). The basic problem is that the TM has a totally spurious dependence on JNDI as the source of its transactional resources. Since JCA is neither defined nor available outside a Java EE environment, this forces anyone trying to use the TM outside of the application server to write their own nasty code depending on some really internal-looking APIs that basically sets up a JNDI-bound proxied datasource where both the TM and the application can find it. In principle this is sorta-straightforward (except for the internal-looking APIs). However, it means that most of the code in `ceylon.transaction` is actually about connection management and setting up JNDI-bound datasources. > Sadly it turns out that, in the context of JBoss Modules, even just getting a JNDI server on the right classloader has proved to be a task so difficult that four reasonably competent developers including myself and other folks who are much better programmers than me have failed at it. I'm sure it's remotely _possible_, and I'm sure that if I weren't using JBoss Modules it would be quite easy. But I'm also sure that it simply shouldn't be necessary. JNDI has nothing to do with transactions and is a distraction here. JNDI is this totally stringly-typed rubbish thing designed in the Clinton era as an abstraction of LDAP by folks who had never heard that Java has static types. Yeah, sure, it continues its zombie existence at the heart of the EE standards, even after we remembered that Java has static types in EE 6, but it just has no place in modern APIs. Other libraries like Hibernate, Spring, etc always offer alternative approaches with no dependence to JNDI. > IMO, what the TM _should_ do is offer an API that lets me hand it an instance of `XADataSource` (it doesn't care where that comes from) and hands my back an instance of `DataSource` that I can use to obtain transaction-bound connections. There is no reason, AFAICT, to involve JNDI in this at all. > XADataSource xads = youJustDontNeedToCare(); > DataSource ds = narayana.registerDataSource(xads); > Or something like that. Of course I'm sure I'm missing some subtleties here. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 8 12:17:29 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 8 Jan 2015 12:17:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2326: ----------------------------------- Summary: Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager Key: JBTM-2326 URL: https://issues.jboss.org/browse/JBTM-2326 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTA, Tooling Reporter: Tom Jenkinson Assignee: Tom Jenkinson Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 8 21:24:29 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 8 Jan 2015 21:24:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2327) wildfly-blacktie does not contain jars in the release In-Reply-To: References: Message-ID: Amos Feng created JBTM-2327: ------------------------------- Summary: wildfly-blacktie does not contain jars in the release Key: JBTM-2327 URL: https://issues.jboss.org/browse/JBTM-2327 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Affects Versions: 5.0.4 Reporter: Amos Feng Assignee: Amos Feng Priority: Blocker Fix For: 5.0.5 it does not copy the artifact into the module folder as it looks like missing the "copy-module-artifacts="true" in the server-provisioning.xml -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 8 22:13:29 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 8 Jan 2015 22:13:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2327) wildfly-blacktie does not contain jars in the release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2327: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/798 > wildfly-blacktie does not contain jars in the release > ----------------------------------------------------- > > Key: JBTM-2327 > URL: https://issues.jboss.org/browse/JBTM-2327 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.4 > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.5 > > > it does not copy the artifact into the module folder as it looks like missing the "copy-module-artifacts="true" in the server-provisioning.xml -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 9 02:27:29 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 9 Jan 2015 02:27:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2327) wildfly-blacktie does not contain jars in the release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2327: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > wildfly-blacktie does not contain jars in the release > ----------------------------------------------------- > > Key: JBTM-2327 > URL: https://issues.jboss.org/browse/JBTM-2327 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.4 > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.5 > > > it does not copy the artifact into the module folder as it looks like missing the "copy-module-artifacts="true" in the server-provisioning.xml -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 9 02:28:29 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 9 Jan 2015 02:28:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2322) Add linux64el7 to the Narayana CI matrix for BlackTie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2322: ---------------------------- Summary: Add linux64el7 to the Narayana CI matrix for BlackTie (was: Add el7 to the Narayana CI matrix for BlackTie) > Add linux64el7 to the Narayana CI matrix for BlackTie > ----------------------------------------------------- > > Key: JBTM-2322 > URL: https://issues.jboss.org/browse/JBTM-2322 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.5 > > > Currently we do not build blacktie on the EL7 node (sansa). We should do this and add it to the narayana matrix job: http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/ -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 9 02:30:30 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Fri, 9 Jan 2015 02:30:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2322) Add linux64el7 to the Narayana CI matrix for BlackTie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng resolved JBTM-2322. ----------------------------- Resolution: Done It also needs to add in the btny-narayana-pulls and update the CI script to get the blacktie third party libraries with centos70x64 > Add linux64el7 to the Narayana CI matrix for BlackTie > ----------------------------------------------------- > > Key: JBTM-2322 > URL: https://issues.jboss.org/browse/JBTM-2322 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.5 > > > Currently we do not build blacktie on the EL7 node (sansa). We should do this and add it to the narayana matrix job: http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/ -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 9 04:35:29 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 Jan 2015 04:35:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031200#comment-13031200 ] Tom Jenkinson commented on JBTM-2326: ------------------------------------- The XAR should be indexed by JNDI name. > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 9 09:56:30 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 9 Jan 2015 09:56:30 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031337#comment-13031337 ] Tom Jenkinson commented on JBTM-2326: ------------------------------------- When enableStatistics is enabled it would be useful to see a count of transactions are are completed by the recovery manager to enable users to see issues in their application. The counts of interest are "completed", "indount", "heuristics" > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 9 09:58:29 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 9 Jan 2015 09:58:29 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated JBTM-2326: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1178798 > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 9 15:46:36 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 9 Jan 2015 15:46:36 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031489#comment-13031489 ] RH Bugzilla Integration commented on JBTM-2308: ----------------------------------------------- Paul Gier changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from MODIFIED to ON_QA > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.0.5 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 03:05:49 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 12 Jan 2015 03:05:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031643#comment-13031643 ] Amos Feng commented on JBTM-2090: --------------------------------- It happens again. http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/728/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el7/ > BlackTie process terminating with default action of signal 13 (SIGPIPE) > ----------------------------------------------------------------------- > > Key: JBTM-2090 > URL: https://issues.jboss.org/browse/JBTM-2090 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Labels: linux64el6 > Fix For: 5.x.y > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log > {code} > ==11776== Process terminating with default action of signal 13 (SIGPIPE) > ==11776== at 0x72734ED: ??? (in /lib64/libpthread-2.12.so) > ==11776== by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9) > ==11776== by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305) > ==11776== by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347) > ==11776== by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536) > ==11776== by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==11776== by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183) > ==11776== by 0x6D24122: tpdiscon (XATMIc.cxx:1220) > ==11776== by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66) > ==11776== by 0x49B74A: CppUnit::TestCaller::tearDown() (TestCaller.h:182) > ==11776== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==11776== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==11776== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==11776== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==11776== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==11776== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==11776== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==11776== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==11776== by 0x4F6F83: main (TestRunner.cxx:27) > --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap() > --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap() > --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap() > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 03:06:49 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 12 Jan 2015 03:06:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2090: ---------------------------- Fix Version/s: 5.0.5 (was: 5.x.y) > BlackTie process terminating with default action of signal 13 (SIGPIPE) > ----------------------------------------------------------------------- > > Key: JBTM-2090 > URL: https://issues.jboss.org/browse/JBTM-2090 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Labels: linux64el6, linux64el7 > Fix For: 5.0.5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log > {code} > ==11776== Process terminating with default action of signal 13 (SIGPIPE) > ==11776== at 0x72734ED: ??? (in /lib64/libpthread-2.12.so) > ==11776== by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9) > ==11776== by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305) > ==11776== by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347) > ==11776== by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536) > ==11776== by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==11776== by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183) > ==11776== by 0x6D24122: tpdiscon (XATMIc.cxx:1220) > ==11776== by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66) > ==11776== by 0x49B74A: CppUnit::TestCaller::tearDown() (TestCaller.h:182) > ==11776== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==11776== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==11776== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==11776== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==11776== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==11776== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==11776== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==11776== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==11776== by 0x4F6F83: main (TestRunner.cxx:27) > --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap() > --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap() > --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap() > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 03:06:49 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 12 Jan 2015 03:06:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2090: ---------------------------- Priority: Major (was: Minor) > BlackTie process terminating with default action of signal 13 (SIGPIPE) > ----------------------------------------------------------------------- > > Key: JBTM-2090 > URL: https://issues.jboss.org/browse/JBTM-2090 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Labels: linux64el6, linux64el7 > Fix For: 5.0.5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log > {code} > ==11776== Process terminating with default action of signal 13 (SIGPIPE) > ==11776== at 0x72734ED: ??? (in /lib64/libpthread-2.12.so) > ==11776== by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9) > ==11776== by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305) > ==11776== by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347) > ==11776== by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536) > ==11776== by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==11776== by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183) > ==11776== by 0x6D24122: tpdiscon (XATMIc.cxx:1220) > ==11776== by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66) > ==11776== by 0x49B74A: CppUnit::TestCaller::tearDown() (TestCaller.h:182) > ==11776== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==11776== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==11776== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==11776== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==11776== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==11776== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==11776== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==11776== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==11776== by 0x4F6F83: main (TestRunner.cxx:27) > --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap() > --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap() > --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap() > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 03:06:49 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 12 Jan 2015 03:06:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2090: ---------------------------- Labels: linux64el6 linux64el7 (was: linux64el6) > BlackTie process terminating with default action of signal 13 (SIGPIPE) > ----------------------------------------------------------------------- > > Key: JBTM-2090 > URL: https://issues.jboss.org/browse/JBTM-2090 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Labels: linux64el6, linux64el7 > Fix For: 5.0.5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log > {code} > ==11776== Process terminating with default action of signal 13 (SIGPIPE) > ==11776== at 0x72734ED: ??? (in /lib64/libpthread-2.12.so) > ==11776== by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9) > ==11776== by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305) > ==11776== by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347) > ==11776== by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536) > ==11776== by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==11776== by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183) > ==11776== by 0x6D24122: tpdiscon (XATMIc.cxx:1220) > ==11776== by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66) > ==11776== by 0x49B74A: CppUnit::TestCaller::tearDown() (TestCaller.h:182) > ==11776== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==11776== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==11776== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==11776== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==11776== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==11776== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==11776== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==11776== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==11776== by 0x4F6F83: main (TestRunner.cxx:27) > --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap() > --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap() > --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap() > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 07:42:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 07:42:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2328) Deprecate the HeuristicInformation interface In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2328: ----------------------------------- Summary: Deprecate the HeuristicInformation interface Key: JBTM-2328 URL: https://issues.jboss.org/browse/JBTM-2328 Project: JBoss Transaction Manager Issue Type: Task Components: Transaction Core Reporter: Tom Jenkinson Assignee: Michael Musgrove There exists and HeuristicInformation interface (https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/HeuristicInformation.java) which was intended to allow an AbstractRecord implementor to provide additional details about the heuristic state of the record as well as provide access to tooling to clear the state of the heuristic within the (potentially remove) resource manager. This has been decoupled from the tooling for many iterations (the ability to resolve the heuristic appears as though it was never wired up) and though Mike is updating the tooling to access the additional context of the heuristic state we do not propose to continue with this as the recommendation of resolving heuristics. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 07:43:48 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 07:43:48 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2329: ----------------------------------- Summary: Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction Key: JBTM-2329 URL: https://issues.jboss.org/browse/JBTM-2329 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. After discussion on the forum, it seems likely the API would be something like: Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) {code} public interface HeuristicManagement { public void resolve() throws CouldNotResolveException; } {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 07:45:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 07:45:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2330) Document the procedure to discover and resolve heuristically completed branches in Narayana In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2330: ----------------------------------- Summary: Document the procedure to discover and resolve heuristically completed branches in Narayana Key: JBTM-2330 URL: https://issues.jboss.org/browse/JBTM-2330 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Documentation Reporter: Tom Jenkinson Assignee: Michael Musgrove Our documentation is not complete in this area. We need to describe how users can detect heuristically completed branches in the system. It would be useful to consider this in standalone and embedded wildfly modes. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 07:46:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 07:46:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2329: -------------------------------- Forum Reference: https://developer.jboss.org/message/912282 > Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2329 > URL: https://issues.jboss.org/browse/JBTM-2329 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. > After discussion on the forum, it seems likely the API would be something like: > Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. > Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) > {code} > public interface HeuristicManagement > { > public void resolve() throws CouldNotResolveException; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 07:46:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 07:46:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2330) Document the procedure to discover and resolve heuristically completed branches in Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2330: -------------------------------- Forum Reference: https://developer.jboss.org/message/912282 > Document the procedure to discover and resolve heuristically completed branches in Narayana > ------------------------------------------------------------------------------------------- > > Key: JBTM-2330 > URL: https://issues.jboss.org/browse/JBTM-2330 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Our documentation is not complete in this area. We need to describe how users can detect heuristically completed branches in the system. It would be useful to consider this in standalone and embedded wildfly modes. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 07:46:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 07:46:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2328) Deprecate the HeuristicInformation interface In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2328: -------------------------------- Forum Reference: https://developer.jboss.org/message/912282 > Deprecate the HeuristicInformation interface > -------------------------------------------- > > Key: JBTM-2328 > URL: https://issues.jboss.org/browse/JBTM-2328 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > There exists and HeuristicInformation interface (https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/HeuristicInformation.java) which was intended to allow an AbstractRecord implementor to provide additional details about the heuristic state of the record as well as provide access to tooling to clear the state of the heuristic within the (potentially remove) resource manager. > This has been decoupled from the tooling for many iterations (the ability to resolve the heuristic appears as though it was never wired up) and though Mike is updating the tooling to access the additional context of the heuristic state we do not propose to continue with this as the recommendation of resolving heuristics. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 07:46:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 07:46:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2330) Document the procedure to discover and resolve heuristically completed branches in Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2330: -------------------------------- Fix Version/s: 5.0.5 > Document the procedure to discover and resolve heuristically completed branches in Narayana > ------------------------------------------------------------------------------------------- > > Key: JBTM-2330 > URL: https://issues.jboss.org/browse/JBTM-2330 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Our documentation is not complete in this area. We need to describe how users can detect heuristically completed branches in the system. It would be useful to consider this in standalone and embedded wildfly modes. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 07:51:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 07:51:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2316) Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2316: -------------------------------- Summary: Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage (was: Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage and remove performance tool) > Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage > --------------------------------------------------------------------- > > Key: JBTM-2316 > URL: https://issues.jboss.org/browse/JBTM-2316 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > I can't see the transactional driver or JTAx stuff in the code-coverage report and I also don't think its worth aggregating in the performance test harness into the coverage numbers. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 08:05:50 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 08:05:50 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2325) Allow the user to provide a reference to an XADataSource for Transactional Driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2325. --------------------------------- Resolution: Done > Allow the user to provide a reference to an XADataSource for Transactional Driver > --------------------------------------------------------------------------------- > > Key: JBTM-2325 > URL: https://issues.jboss.org/browse/JBTM-2325 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.5 > > > Certain environments have class loader constraints that do not let the direct recoverable connection load the users configured XADataSource. It is therefore necessary to provide an implementation that can be passed by reference. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 08:08:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 08:08:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2090: -------------------------------- Fix Version/s: 5.x.y (was: 5.0.5) > BlackTie process terminating with default action of signal 13 (SIGPIPE) > ----------------------------------------------------------------------- > > Key: JBTM-2090 > URL: https://issues.jboss.org/browse/JBTM-2090 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Labels: linux64el6, linux64el7 > Fix For: 5.x.y > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log > {code} > ==11776== Process terminating with default action of signal 13 (SIGPIPE) > ==11776== at 0x72734ED: ??? (in /lib64/libpthread-2.12.so) > ==11776== by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9) > ==11776== by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305) > ==11776== by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347) > ==11776== by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536) > ==11776== by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==11776== by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183) > ==11776== by 0x6D24122: tpdiscon (XATMIc.cxx:1220) > ==11776== by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66) > ==11776== by 0x49B74A: CppUnit::TestCaller::tearDown() (TestCaller.h:182) > ==11776== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==11776== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==11776== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==11776== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==11776== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==11776== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==11776== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==11776== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==11776== by 0x4F6F83: main (TestRunner.cxx:27) > --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap() > --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap() > --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap() > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 08:08:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Jan 2015 08:08:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2330) Document the procedure to discover and resolve heuristically completed branches in Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2330: -------------------------------- Fix Version/s: 5.x.y (was: 5.0.5) > Document the procedure to discover and resolve heuristically completed branches in Narayana > ------------------------------------------------------------------------------------------- > > Key: JBTM-2330 > URL: https://issues.jboss.org/browse/JBTM-2330 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.x.y > > > Our documentation is not complete in this area. We need to describe how users can detect heuristically completed branches in the system. It would be useful to consider this in standalone and embedded wildfly modes. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 09:23:49 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 12 Jan 2015 09:23:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2331) TransactionalDriver may leave a JDBC Connection associated after transaction termination In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2331: -------------------------------------- Summary: TransactionalDriver may leave a JDBC Connection associated after transaction termination Key: JBTM-2331 URL: https://issues.jboss.org/browse/JBTM-2331 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.0.4 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.5 1) Start a transaction; 2) Obtain a connection via the TransactionalDriver 3) End transaction 4) start another transaction 5) Call connection.isClosed() this will produce the following exception because the transactional driver thinks the connection is still associated: {code} java.lang.RuntimeException: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:228) at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:368) at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:305) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:113) at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:40) at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:33) at com.redhat.ceylon.launcher.Launcher.main(Launcher.java:26) Caused by: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1078) at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) at ceylon.dbc.ConnectionStatus.connection(ConnectionStatus.ceylon:22) at ceylon.dbc.Sql.prepareStatement$priv$(Sql.ceylon:89) at ceylon.dbc.Sql.access$100(Sql.ceylon:701) at ceylon.dbc.Sql$Update.execute$canonical$(Sql.ceylon:346) at ceylon.dbc.Sql$Update.execute(Sql.ceylon:343) at example.ceylon.transaction.tm.runTx_.runTx(transaction.ceylon:199) at example.ceylon.transaction.tm.run_.run(transaction.ceylon:225) at example.ceylon.transaction.tm.run_.main(transaction.ceylon) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at ceylon.modules.api.runtime.SecurityActions.invokeRunInternal(SecurityActions.java:58) at ceylon.modules.api.runtime.SecurityActions.invokeRun(SecurityActions.java:48) at ceylon.modules.api.runtime.AbstractRuntime.invokeRun(AbstractRuntime.java:101) at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:167) at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:151) at ceylon.modules.Main.execute(Main.java:69) at ceylon.modules.Main.main(Main.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.modules.Module.run(Module.java:312) at org.jboss.modules.Main.main(Main.java:460) at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:208) ... 10 more {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 09:33:49 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 12 Jan 2015 09:33:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2331) TransactionalDriver may leave a JDBC Connection associated after transaction termination In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2331: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/799 > TransactionalDriver may leave a JDBC Connection associated after transaction termination > ---------------------------------------------------------------------------------------- > > Key: JBTM-2331 > URL: https://issues.jboss.org/browse/JBTM-2331 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > 1) Start a transaction; > 2) Obtain a connection via the TransactionalDriver > 3) End transaction > 4) start another transaction > 5) Call connection.isClosed() > this will produce the following exception because the transactional driver thinks the connection is still associated: > {code} > java.lang.RuntimeException: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:228) > at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:368) > at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:305) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:113) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:40) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:33) > at com.redhat.ceylon.launcher.Launcher.main(Launcher.java:26) > Caused by: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1078) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at ceylon.dbc.ConnectionStatus.connection(ConnectionStatus.ceylon:22) > at ceylon.dbc.Sql.prepareStatement$priv$(Sql.ceylon:89) > at ceylon.dbc.Sql.access$100(Sql.ceylon:701) > at ceylon.dbc.Sql$Update.execute$canonical$(Sql.ceylon:346) > at ceylon.dbc.Sql$Update.execute(Sql.ceylon:343) > at example.ceylon.transaction.tm.runTx_.runTx(transaction.ceylon:199) > at example.ceylon.transaction.tm.run_.run(transaction.ceylon:225) > at example.ceylon.transaction.tm.run_.main(transaction.ceylon) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at ceylon.modules.api.runtime.SecurityActions.invokeRunInternal(SecurityActions.java:58) > at ceylon.modules.api.runtime.SecurityActions.invokeRun(SecurityActions.java:48) > at ceylon.modules.api.runtime.AbstractRuntime.invokeRun(AbstractRuntime.java:101) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:167) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:151) > at ceylon.modules.Main.execute(Main.java:69) > at ceylon.modules.Main.main(Main.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:208) > ... 10 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 11:02:49 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 12 Jan 2015 11:02:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031851#comment-13031851 ] RH Bugzilla Integration commented on JBTM-2308: ----------------------------------------------- Hayk Hovsepyan changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from ON_QA to VERIFIED > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.0.5 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 12:36:48 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 12 Jan 2015 12:36:48 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2331) TransactionalDriver may leave a JDBC Connection associated after transaction termination In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2331: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TransactionalDriver may leave a JDBC Connection associated after transaction termination > ---------------------------------------------------------------------------------------- > > Key: JBTM-2331 > URL: https://issues.jboss.org/browse/JBTM-2331 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > 1) Start a transaction; > 2) Obtain a connection via the TransactionalDriver > 3) End transaction > 4) start another transaction > 5) Call connection.isClosed() > this will produce the following exception because the transactional driver thinks the connection is still associated: > {code} > java.lang.RuntimeException: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:228) > at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:368) > at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:305) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:113) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:40) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:33) > at com.redhat.ceylon.launcher.Launcher.main(Launcher.java:26) > Caused by: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1078) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at ceylon.dbc.ConnectionStatus.connection(ConnectionStatus.ceylon:22) > at ceylon.dbc.Sql.prepareStatement$priv$(Sql.ceylon:89) > at ceylon.dbc.Sql.access$100(Sql.ceylon:701) > at ceylon.dbc.Sql$Update.execute$canonical$(Sql.ceylon:346) > at ceylon.dbc.Sql$Update.execute(Sql.ceylon:343) > at example.ceylon.transaction.tm.runTx_.runTx(transaction.ceylon:199) > at example.ceylon.transaction.tm.run_.run(transaction.ceylon:225) > at example.ceylon.transaction.tm.run_.main(transaction.ceylon) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at ceylon.modules.api.runtime.SecurityActions.invokeRunInternal(SecurityActions.java:58) > at ceylon.modules.api.runtime.SecurityActions.invokeRun(SecurityActions.java:48) > at ceylon.modules.api.runtime.AbstractRuntime.invokeRun(AbstractRuntime.java:101) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:167) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:151) > at ceylon.modules.Main.execute(Main.java:69) > at ceylon.modules.Main.main(Main.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:208) > ... 10 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 13 03:33:49 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 13 Jan 2015 03:33:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032032#comment-13032032 ] Amos Feng commented on JBTM-2090: --------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/730/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el7/ > BlackTie process terminating with default action of signal 13 (SIGPIPE) > ----------------------------------------------------------------------- > > Key: JBTM-2090 > URL: https://issues.jboss.org/browse/JBTM-2090 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Labels: linux64el6, linux64el7 > Fix For: 5.x.y > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log > {code} > ==11776== Process terminating with default action of signal 13 (SIGPIPE) > ==11776== at 0x72734ED: ??? (in /lib64/libpthread-2.12.so) > ==11776== by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9) > ==11776== by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305) > ==11776== by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347) > ==11776== by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536) > ==11776== by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==11776== by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183) > ==11776== by 0x6D24122: tpdiscon (XATMIc.cxx:1220) > ==11776== by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66) > ==11776== by 0x49B74A: CppUnit::TestCaller::tearDown() (TestCaller.h:182) > ==11776== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==11776== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==11776== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==11776== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==11776== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==11776== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==11776== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==11776== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==11776== by 0x4F6F83: main (TestRunner.cxx:27) > --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap() > --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap() > --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap() > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 13 04:56:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 13 Jan 2015 04:56:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032050#comment-13032050 ] Tom Jenkinson commented on JBTM-2295: ------------------------------------- When we create a quickstart etc for this I think it would be nice to create a blog article too somewhat similar to http://rpestano.wordpress.com/2015/01/10/a-simple-java-ee-docker-example/ > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 13 05:07:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 13 Jan 2015 05:07:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2297) Store docker image for service(s) in JBoss repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032058#comment-13032058 ] Tom Jenkinson commented on JBTM-2297: ------------------------------------- There are instructions here on whom to contact to get this uploaded: http://www.jboss.org/docker/ > Store docker image for service(s) in JBoss repo > ----------------------------------------------- > > Key: JBTM-2297 > URL: https://issues.jboss.org/browse/JBTM-2297 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > We have a repo for JBoss project docker images. Store our final version (not POC version I created) there. Also see if this also suggests a way of distributing and storing the docker file to create it/them. I'm assuming we don't need to store this information within the Narayana repo, but perhaps we do and in which case we'll probably need a docker directory. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 13 05:08:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 13 Jan 2015 05:08:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032059#comment-13032059 ] Tom Jenkinson commented on JBTM-2295: ------------------------------------- [~gytis], I think the docker scripts you have here look like a good start to me > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 13 05:10:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 13 Jan 2015 05:10:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2296: -------------------------------- Fix Version/s: 5.0.5 > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 14 08:42:49 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Wed, 14 Jan 2015 08:42:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032452#comment-13032452 ] Mark Little commented on JBTM-2296: ----------------------------------- Worth mentioning for completeness that if we stick with pure CORBA approaches then we could use a CORBA Naming Service and tie things together that way. But there are pros and cons. > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 14 09:06:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 14 Jan 2015 09:06:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032467#comment-13032467 ] Tom Jenkinson commented on JBTM-2296: ------------------------------------- I was actually chatting to Gytis about this this morning on IRC. Allowing clients to resolve the transaction manager via an ORBInitialHost:ORBInitialPort combo seems easier than asking clients to retrieve the IOR from a shared location. He is looking at sharing on the forum a prototype docker setup that: 1. Spins up the JacORB naming service on a known port first 2. Config Narayana to connect to the name service to register the IOR Then a remote client just need the IP address of the docker VM plus this known port in order to connect to the transaction manager, rather than access to the CosServices.cfg. The other option we considered is to use a configurable name for the CosServices.cfg based on the node name so that we can have a variable number of them: https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/orbportability/classes/com/arjuna/orbportability/common/OrbPortabilityEnvironmentBean.java#L114 That would require sharing those files in a manner similar to our current POC. > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 14 10:44:49 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 14 Jan 2015 10:44:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2323) Resume dualstack testing on the NCL CI cluster In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2323. ------------------------------------ Resolution: Done I have configured the job on the NCL cluser: http://172.17.130.4:8080/job/narayana-dualstack/ > Resume dualstack testing on the NCL CI cluster > ---------------------------------------------- > > Key: JBTM-2323 > URL: https://issues.jboss.org/browse/JBTM-2323 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > The new CI nodes are not configured for IPv6. As this is a bit specialised it would make sense to keep this job back on the Newcastle cluster. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 11:38:49 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Thu, 15 Jan 2015 11:38:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032842#comment-13032842 ] Mark Little commented on JBTM-2296: ----------------------------------- Another thought: CORBA already specifies how key services should be resolved using resolve_initial_references. Some ORBs may use a Name Server for this, others may statically add it via config data. Check the ORB Portability layer for these options. If we are going to stay within CORBA land then it should be done via resolve_initial_references, which may be the same as CosServices.cfg for JacORB but it could be something different for the JDK ORB. > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 11:39:49 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Thu, 15 Jan 2015 11:39:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2332) resolve_initial_references on JDK ORB In-Reply-To: References: Message-ID: Mark Little created JBTM-2332: --------------------------------- Summary: resolve_initial_references on JDK ORB Key: JBTM-2332 URL: https://issues.jboss.org/browse/JBTM-2332 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTS Affects Versions: 5.0.4 Reporter: Mark Little Assignee: Michael Musgrove Check how the JDK ORB uses resolve_initial_references and that it is tied into the ORB Portability layer. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 16 02:20:49 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 16 Jan 2015 02:20:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033020#comment-13033020 ] RH Bugzilla Integration commented on JBTM-2326: ----------------------------------------------- Harald Pehl changed the Status of [bug 1178798|https://bugzilla.redhat.com/show_bug.cgi?id=1178798] from ASSIGNED to POST > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 16 06:26:52 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 16 Jan 2015 06:26:52 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033077#comment-13033077 ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- Vaclav Tunka changed the Status of [bug 1170567|https://bugzilla.redhat.com/show_bug.cgi?id=1170567] from MODIFIED to ON_QA > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.25, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 05:54:49 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 19 Jan 2015 05:54:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2333) BlacTie subsystem build fails, because of missing org.jacorb module In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2333: ------------------------------------- Summary: BlacTie subsystem build fails, because of missing org.jacorb module Key: JBTM-2333 URL: https://issues.jboss.org/browse/JBTM-2333 Project: JBoss Transaction Manager Issue Type: Bug Components: Application Server Integration, BlackTie Reporter: Gytis Trikleris Assignee: Amos Feng Priority: Minor Fix For: 5.0.5 http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ {code} [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] [ERROR] -> [Help 1] {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 05:55:48 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 19 Jan 2015 05:55:48 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2333) BlacTie subsystem build fails, because of missing org.jacorb module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033433#comment-13033433 ] Gytis Trikleris commented on JBTM-2333: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-windows2008-catelyn/819 > BlacTie subsystem build fails, because of missing org.jacorb module > ------------------------------------------------------------------- > > Key: JBTM-2333 > URL: https://issues.jboss.org/browse/JBTM-2333 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration, BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack > [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 07:39:49 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 19 Jan 2015 07:39:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033503#comment-13033503 ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- Hayk Hovsepyan changed the Status of [bug 1170567|https://bugzilla.redhat.com/show_bug.cgi?id=1170567] from ON_QA to VERIFIED > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.25, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 08:06:50 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Jan 2015 08:06:50 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2333) Blacktie subsystem build fails, because of missing org.jacorb module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2333: -------------------------------- Summary: Blacktie subsystem build fails, because of missing org.jacorb module (was: BlacTie subsystem build fails, because of missing org.jacorb module) > Blacktie subsystem build fails, because of missing org.jacorb module > -------------------------------------------------------------------- > > Key: JBTM-2333 > URL: https://issues.jboss.org/browse/JBTM-2333 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration, BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack > [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 08:09:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Jan 2015 08:09:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2090: -------------------------------- Fix Version/s: 5.0.5 (was: 5.x.y) > BlackTie process terminating with default action of signal 13 (SIGPIPE) > ----------------------------------------------------------------------- > > Key: JBTM-2090 > URL: https://issues.jboss.org/browse/JBTM-2090 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Labels: linux64el6, linux64el7 > Fix For: 5.0.5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log > {code} > ==11776== Process terminating with default action of signal 13 (SIGPIPE) > ==11776== at 0x72734ED: ??? (in /lib64/libpthread-2.12.so) > ==11776== by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9) > ==11776== by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305) > ==11776== by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347) > ==11776== by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536) > ==11776== by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==11776== by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183) > ==11776== by 0x6D24122: tpdiscon (XATMIc.cxx:1220) > ==11776== by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66) > ==11776== by 0x49B74A: CppUnit::TestCaller::tearDown() (TestCaller.h:182) > ==11776== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==11776== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==11776== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==11776== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==11776== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==11776== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==11776== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==11776== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==11776== by 0x4F6F83: main (TestRunner.cxx:27) > --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap() > --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap() > --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap() > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 08:21:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Jan 2015 08:21:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2333) Blacktie subsystem build fails, because of missing org.jacorb module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2333: -------------------------------- Priority: Blocker (was: Minor) > Blacktie subsystem build fails, because of missing org.jacorb module > -------------------------------------------------------------------- > > Key: JBTM-2333 > URL: https://issues.jboss.org/browse/JBTM-2333 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration, BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack > [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 23:32:49 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 19 Jan 2015 23:32:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2333) Blacktie subsystem build fails, because of missing org.jacorb module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2333: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/800 > Blacktie subsystem build fails, because of missing org.jacorb module > -------------------------------------------------------------------- > > Key: JBTM-2333 > URL: https://issues.jboss.org/browse/JBTM-2333 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration, BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack > [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 21 01:50:49 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Wed, 21 Jan 2015 01:50:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2334) Improve ease of use within Tomcat In-Reply-To: References: Message-ID: Mark Little created JBTM-2334: --------------------------------- Summary: Improve ease of use within Tomcat Key: JBTM-2334 URL: https://issues.jboss.org/browse/JBTM-2334 Project: JBoss Transaction Manager Issue Type: Feature Request Components: JTA Affects Versions: 5.0.4 Reporter: Mark Little Assignee: Tom Jenkinson It's still too difficult for people to do. http://drieselliott.tumblr.com/post/99496743610/integrating-narayana-transaction-manager-with -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 21 02:45:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 21 Jan 2015 02:45:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2334) Improve ease of use within Tomcat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033990#comment-13033990 ] Tom Jenkinson commented on JBTM-2334: ------------------------------------- Just to comment that there is a quickstart for getting tomcat, ironjacamar and Narayana running. Its only applicable if you would like JCA managed resources though: https://github.com/jbosstm/quickstart/blob/master/jca-and-tomcat/ > Improve ease of use within Tomcat > --------------------------------- > > Key: JBTM-2334 > URL: https://issues.jboss.org/browse/JBTM-2334 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > > It's still too difficult for people to do. > http://drieselliott.tumblr.com/post/99496743610/integrating-narayana-transaction-manager-with -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 21 04:29:49 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Wed, 21 Jan 2015 04:29:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2334) Improve ease of use within Tomcat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034022#comment-13034022 ] Mark Little commented on JBTM-2334: ----------------------------------- Does that address the same use case though? If not then we should re-examine what we're doing. > Improve ease of use within Tomcat > --------------------------------- > > Key: JBTM-2334 > URL: https://issues.jboss.org/browse/JBTM-2334 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Tom Jenkinson > > It's still too difficult for people to do. > http://drieselliott.tumblr.com/post/99496743610/integrating-narayana-transaction-manager-with -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 21 10:05:48 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 21 Jan 2015 10:05:48 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2333) Blacktie subsystem build fails, because of missing org.jacorb module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2333: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Blacktie subsystem build fails, because of missing org.jacorb module > -------------------------------------------------------------------- > > Key: JBTM-2333 > URL: https://issues.jboss.org/browse/JBTM-2333 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration, BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack > [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 21 10:10:48 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 21 Jan 2015 10:10:48 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2335) Removing CORBA in JATMI In-Reply-To: References: Message-ID: Amos Feng created JBTM-2335: ------------------------------- Summary: Removing CORBA in JATMI Key: JBTM-2335 URL: https://issues.jboss.org/browse/JBTM-2335 Project: JBoss Transaction Manager Issue Type: Feature Request Components: BlackTie Reporter: Amos Feng Assignee: Amos Feng Priority: Minor Fix For: 5.x.y Currently we are still using the OrbManagement, it needs to be removed as we have not supported the OTS Transaction in Blacktie transport. It also need to port the JATMI code to use RTS. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 23 17:23:49 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Fri, 23 Jan 2015 17:23:49 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034738#comment-13034738 ] RH Bugzilla Integration commented on JBTM-2326: ----------------------------------------------- Kabir Khan changed the Status of [bug 1178798|https://bugzilla.redhat.com/show_bug.cgi?id=1178798] from POST to MODIFIED > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java#L1017 so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 26 09:52:48 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 26 Jan 2015 09:52:48 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-860: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/802 > use XAResourceWrapper metadata for assume complete > -------------------------------------------------- > > Key: JBTM-860 > URL: https://issues.jboss.org/browse/JBTM-860 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Resource Manager > Affects Versions: 4.15.0 > Reporter: Jonathan Halliday > Assignee: Gytis Trikleris > Fix For: 5.x.y > > > In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM. It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control. With the availability of RM id information from XAResourceWrapper this becomes feasible. -- This message was sent by Atlassian JIRA (v6.3.11#6341)