From issues at jboss.org Mon Mar 5 01:50:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 5 Mar 2018 01:50:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2998) Blacktie TestTPGetRply failed with unknown session In-Reply-To: References: Message-ID: Amos Feng created JBTM-2998: ------------------------------- Summary: Blacktie TestTPGetRply failed with unknown session Key: JBTM-2998 URL: https://issues.jboss.org/browse/JBTM-2998 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Amos Feng Assignee: Amos Feng Priority: Minor Fix For: 5.later {noformat} 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerClient :200 ) - get session: 3 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerClient :209 ) - did not get session: 3 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :411 ) - _get_tperrno 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :415 ) - found _get_tperrno2 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :418 ) - returning _get_tperrno2 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :924 ) - tpgetrply return: -1 tperrno: 2 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :411 ) - _get_tperrno 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :415 ) - found _get_tperrno2 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :418 ) - returning _get_tperrno2 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerLogc :72 ) - CHKCOND ASSERT FAILED C:\hudson\workspace\narayana-catelyn\blacktie\xatmi\src\test\cpp\TestTPGetRply.cxx:272 {noformat} It looks like that the sessionIds have the prev id in the other tests which has not been removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Mar 7 11:57:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 7 Mar 2018 11:57:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2999) Update git url for the jboss-as part of the build In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2999: -------------------------------------- Summary: Update git url for the jboss-as part of the build Key: JBTM-2999 URL: https://issues.jboss.org/browse/JBTM-2999 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Affects Versions: 5.8.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The AS part of the narayana build on mac-os fails with: {quote} Building AS First time checkout of AS7 Cloning into jboss-as... error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing https://github.com/jbosstm/jboss-as.git/info/refs fatal: HTTP request failed {quote} using the git url does work though: git://github.com/jbosstm/jboss-as.git -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Mar 7 12:00:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 7 Mar 2018 12:00:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2999) Update git url for the jboss-as part of the build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1291 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Update git url for the jboss-as part of the build > ------------------------------------------------- > > Key: JBTM-2999 > URL: https://issues.jboss.org/browse/JBTM-2999 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.8.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The AS part of the narayana build on mac-os fails with: > {quote} > Building AS > First time checkout of AS7 > Cloning into jboss-as... > error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing https://github.com/jbosstm/jboss-as.git/info/refs > fatal: HTTP request failed > {quote} > using the git url does work though: > git://github.com/jbosstm/jboss-as.git -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Mar 8 06:18:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 8 Mar 2018 06:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2999) Update git url for the jboss-as part of the build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2999: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update git url for the jboss-as part of the build > ------------------------------------------------- > > Key: JBTM-2999 > URL: https://issues.jboss.org/browse/JBTM-2999 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.8.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The AS part of the narayana build on mac-os fails with: > {quote} > Building AS > First time checkout of AS7 > Cloning into jboss-as... > error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing https://github.com/jbosstm/jboss-as.git/info/refs > fatal: HTTP request failed > {quote} > using the git url does work though: > git://github.com/jbosstm/jboss-as.git -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Mar 9 10:14:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 9 Mar 2018 10:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2995: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 13 14:21:00 2018 From: issues at jboss.org (Daniel Shaver (JIRA)) Date: Tue, 13 Mar 2018 14:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3000) Support for Oracle Wallet JDBC connections In-Reply-To: References: Message-ID: Daniel Shaver created JBTM-3000: ----------------------------------- Summary: Support for Oracle Wallet JDBC connections Key: JBTM-3000 URL: https://issues.jboss.org/browse/JBTM-3000 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Daniel Shaver Priority: Optional In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet. This means that Narayana does not support Oracle Wallet JDBC connections. This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. {code:java} user = info.getProperty(TransactionalDriver.userName, ""); passwd = info.getProperty(TransactionalDriver.password, ""); {code} and in com.arjuna.ats.internal.jdbc.ConnectionManager {code:java} String user = info.getProperty(TransactionalDriver.userName, ""); String passwd = info.getProperty(TransactionalDriver.password, ""); {code} I believe it should be okay to just remove default value so that the client's input is always taken as-is. I was able to successfully build test this change out locally, using OJDBC 12.2.0.1 and Oracle UCP 12.2.0.1 running in a spring boot/tomcat container. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 13 14:28:00 2018 From: issues at jboss.org (Anonymous (JIRA)) Date: Tue, 13 Mar 2018 14:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3000) Support for Oracle Wallet JDBC connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when dshaver1 created pull request #1294 in GitHub --------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Support for Oracle Wallet JDBC connections > ------------------------------------------ > > Key: JBTM-3000 > URL: https://issues.jboss.org/browse/JBTM-3000 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Daniel Shaver > Priority: Optional > > In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet. > This means that Narayana does not support Oracle Wallet JDBC connections. > This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. > {code:java} > user = info.getProperty(TransactionalDriver.userName, ""); > passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > and in com.arjuna.ats.internal.jdbc.ConnectionManager > {code:java} > String user = info.getProperty(TransactionalDriver.userName, ""); > String passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > I believe it should be okay to just remove default value so that the client's input is always taken as-is. > I was able to successfully build test this change out locally, using OJDBC 12.2.0.1 and Oracle UCP 12.2.0.1 running in a spring boot/tomcat container. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 13 15:08:00 2018 From: issues at jboss.org (Daniel Shaver (JIRA)) Date: Tue, 13 Mar 2018 15:08:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3000) Support for Oracle Wallet JDBC connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Shaver updated JBTM-3000: -------------------------------- Description: In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet. This means that Narayana does not support Oracle Wallet JDBC connections. This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. {code:java} user = info.getProperty(TransactionalDriver.userName, ""); passwd = info.getProperty(TransactionalDriver.password, ""); {code} and in com.arjuna.ats.internal.jdbc.ConnectionManager {code:java} String user = info.getProperty(TransactionalDriver.userName, ""); String passwd = info.getProperty(TransactionalDriver.password, ""); {code} I believe it should be okay to just remove default value so that the client's input is always taken as-is? was: In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet. This means that Narayana does not support Oracle Wallet JDBC connections. This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. {code:java} user = info.getProperty(TransactionalDriver.userName, ""); passwd = info.getProperty(TransactionalDriver.password, ""); {code} and in com.arjuna.ats.internal.jdbc.ConnectionManager {code:java} String user = info.getProperty(TransactionalDriver.userName, ""); String passwd = info.getProperty(TransactionalDriver.password, ""); {code} I believe it should be okay to just remove default value so that the client's input is always taken as-is. I was able to successfully build test this change out locally, using OJDBC 12.2.0.1 and Oracle UCP 12.2.0.1 running in a spring boot/tomcat container. > Support for Oracle Wallet JDBC connections > ------------------------------------------ > > Key: JBTM-3000 > URL: https://issues.jboss.org/browse/JBTM-3000 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Daniel Shaver > Priority: Optional > > In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet. > This means that Narayana does not support Oracle Wallet JDBC connections. > This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. > {code:java} > user = info.getProperty(TransactionalDriver.userName, ""); > passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > and in com.arjuna.ats.internal.jdbc.ConnectionManager > {code:java} > String user = info.getProperty(TransactionalDriver.userName, ""); > String passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > I believe it should be okay to just remove default value so that the client's input is always taken as-is? -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 13 15:23:00 2018 From: issues at jboss.org (Daniel Shaver (JIRA)) Date: Tue, 13 Mar 2018 15:23:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3000) Support for Oracle Wallet JDBC connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545399#comment-13545399 ] Daniel Shaver commented on JBTM-3000: ------------------------------------- Nevermind, it looks like the null username and password issue was resolved in 5.8.0 (I was using 5.5.3 originally) inside BaseTransactionalDriverXAConnection: {code:java} if ((_user == null || _user.isEmpty()) && (_passwd == null || _passwd.isEmpty())) { if (jdbcLogger.logger.isTraceEnabled()) { jdbcLogger.logger.trace("BaseTransactionalDriverXAConnection - getting connection with no user"); } _theConnection = _theDataSource.getXAConnection(); } else { if (jdbcLogger.logger.isTraceEnabled()) { jdbcLogger.logger.trace("BaseTransactionalDriverXAConnection - getting connection for user " + _user); } _theConnection = _theDataSource.getXAConnection(_user, _passwd); } {code} But I'm still seeing issues. Requires further digging. > Support for Oracle Wallet JDBC connections > ------------------------------------------ > > Key: JBTM-3000 > URL: https://issues.jboss.org/browse/JBTM-3000 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Daniel Shaver > Priority: Optional > > In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet. > This means that Narayana does not support Oracle Wallet JDBC connections. > This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. > {code:java} > user = info.getProperty(TransactionalDriver.userName, ""); > passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > and in com.arjuna.ats.internal.jdbc.ConnectionManager > {code:java} > String user = info.getProperty(TransactionalDriver.userName, ""); > String passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > I believe it should be okay to just remove default value so that the client's input is always taken as-is? -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Mar 14 19:26:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 14 Mar 2018 19:26:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3000) Support for Oracle Wallet JDBC connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3000. ------------------------------- Resolution: Done I think it would be better to create a thread in our forum over here: https://developer.jboss.org/en/jbosstm/content?filterID=contentstatus%5bpublished%5d~objecttype~objecttype%5bthread%5d > Support for Oracle Wallet JDBC connections > ------------------------------------------ > > Key: JBTM-3000 > URL: https://issues.jboss.org/browse/JBTM-3000 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Daniel Shaver > Priority: Optional > > In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet. > This means that Narayana does not support Oracle Wallet JDBC connections. > This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. > {code:java} > user = info.getProperty(TransactionalDriver.userName, ""); > passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > and in com.arjuna.ats.internal.jdbc.ConnectionManager > {code:java} > String user = info.getProperty(TransactionalDriver.userName, ""); > String passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > I believe it should be okay to just remove default value so that the client's input is always taken as-is? -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 20 09:55:03 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 20 Mar 2018 09:55:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3001) MBean representing a transaction should consider state when is to be removed In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-3001: ------------------------------------- Summary: MBean representing a transaction should consider state when is to be removed Key: JBTM-3001 URL: https://issues.jboss.org/browse/JBTM-3001 Project: JBoss Transaction Manager Issue Type: Bug Components: Tooling Affects Versions: 5.8.0.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka When transaction mbean is to be removed by tooling - there is a transaction available in the object store and recovery does not catch it for deletion (the reason could be various - either the transaction is set with heuristic outcome, or transaction was subordinate and recovery waits for the outer player to finish transaction but there is nobody coming, or there is record in txn log store but the RA already forgot about transaction and we want to clean the transaction manager log store) - then currently the transaction manager just tries to call [XAResource.forget|https://docs.oracle.com/javaee/7/api/javax/transaction/xa/XAResource.html#forget-javax.transaction.xa.Xid-]. But the forget call is available (correct by the XA specification) only when the participant finished with in the heuristic state. But deleting transaction by the tooling (even that should be only the tool of the last resort as normally recovery manager handles this automatically) should cause the transaction and all participants are correctly finished (forget or rolled-back) even the transaction is in prepared state (not in heuristic one). When {{forget}} is called on prepared transaction branch then (e.g. for Artemis ActiveMQ) the {{XAException.XAER_NOTA}} is thrown[1]. * The mbean should consider the state of the participant and choose if to rollback ({{prepared}} state) or if to forget ({{heuristic}} state). * The mbean should consider to check {{XAException}} error code as when {{XAResource.forget}} returns {{XAER_NOTA}} (pubs.opengroup.org/onlinepubs/009680699/toc.pdf, {{The specified XID is not known by the resource manager as a heuristically completed XID.}}) then the branch is in incorrect state - probably it's prepared thus rollback could be run. {code} 2018-03-20 11:06:06,614 TRACE [com.arjuna.ats.jta] (management-handler-thread - 1) XAResourceRecord.forget for XAResourceRecord < resource:org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper at 25091a7a, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805b6:-19805d73:5ab0d062:1c, node_name=1, branch_uid=0:ffff0a2805b6:-19805d73:5ab0d062:23, subordinatenodename=null, eis_name=forgot eis name for: 1 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: ActiveMQ Artemis/2.0, jndiName: java:/JmsXA NodeId:c07b7f00-2c1e-11e8-9014-54e1ad661a0b com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 69af92f1 > 2018-03-20 11:06:06,636 WARN [com.arjuna.ats.jta] (management-handler-thread - 1) ARJUNA016006: XAResourceRecord forget failed: - forget threw exception: javax.transaction.xa.XAException at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaForget(ActiveMQSessionContext.java:490) at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.forget(ClientSessionImpl.java:1196) at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.forget(ActiveMQXAResourceWrapper.java:123) at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.forget(ActiveMQXAResourceWrapperImpl.java:86) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forget(XAResourceRecord.java:806) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forgetHeuristic(XAResourceRecord.java:792) at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.removeFromList(LogRecordWrapper.java:238) at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean$GenericAtomicActionWrapper.remove(ActionBean.java:463) at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:327) at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.remove(LogRecordWrapper.java:218) at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:149) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475) at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) at org.jboss.as.txn.subsystem.LogStoreTransactionDeleteHandler.execute(LogStoreTransactionDeleteHandler.java:59) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 20 09:59:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 20 Mar 2018 09:59:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3001) MBean representing a transaction should consider state when is to be removed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548526#comment-13548526 ] Ondra Chaloupka commented on JBTM-3001: --------------------------------------- For example in scenario where jboss eap receives ejb call and subordinate is created and then never finished we can end in state there is prepare transaction in narayana object store and prepared transaction at jms broker side. If jboss eap cli is used and {{delete}} operation is called the result is: - transaction *is not* removed from the Artemis journal - transaction *is* removed from narayana/eap object store I assume that the reason why it's removed (from narayana object store) is the settings[1][2] ignoring the error on the forget call. The delete WFLY cli operation is called from[3]. [1] https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/osb/mbean/LogRecordWrapper.java#L239 [2] https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/common/ObjectStoreEnvironmentBean.java#L89 [3] [4] https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/subsystem/LogStoreTransactionDeleteHandler.java#L59 > MBean representing a transaction should consider state when is to be removed > ---------------------------------------------------------------------------- > > Key: JBTM-3001 > URL: https://issues.jboss.org/browse/JBTM-3001 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > When transaction mbean is to be removed by tooling - there is a transaction available in the object store and recovery does not catch it for deletion (the reason could be various - either the transaction is set with heuristic outcome, or transaction was subordinate and recovery waits for the outer player to finish transaction but there is nobody coming, or there is record in txn log store but the RA already forgot about transaction and we want to clean the transaction manager log store) - then currently the transaction manager just tries to call [XAResource.forget|https://docs.oracle.com/javaee/7/api/javax/transaction/xa/XAResource.html#forget-javax.transaction.xa.Xid-]. But the forget call is available (correct by the XA specification) only when the participant finished with in the heuristic state. > But deleting transaction by the tooling (even that should be only the tool of the last resort as normally recovery manager handles this automatically) should cause the transaction and all participants are correctly finished (forget or rolled-back) even the transaction is in prepared state (not in heuristic one). > When {{forget}} is called on prepared transaction branch then (e.g. for Artemis ActiveMQ) the {{XAException.XAER_NOTA}} is thrown[1]. > * The mbean should consider the state of the participant and choose if to rollback ({{prepared}} state) or if to forget ({{heuristic}} state). > * The mbean should consider to check {{XAException}} error code as when {{XAResource.forget}} returns {{XAER_NOTA}} (pubs.opengroup.org/onlinepubs/009680699/toc.pdf, {{The specified XID is not known by the resource manager as a heuristically completed XID.}}) then the branch is in incorrect state - probably it's prepared thus rollback could be run. > {code} > 2018-03-20 11:06:06,614 TRACE [com.arjuna.ats.jta] (management-handler-thread - 1) XAResourceRecord.forget for XAResourceRecord < resource:org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper at 25091a7a, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805b6:-19805d73:5ab0d062:1c, node_name=1, branch_uid=0:ffff0a2805b6:-19805d73:5ab0d062:23, subordinatenodename=null, eis_name=forgot eis name for: 1 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: ActiveMQ Artemis/2.0, jndiName: java:/JmsXA NodeId:c07b7f00-2c1e-11e8-9014-54e1ad661a0b com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 69af92f1 > > 2018-03-20 11:06:06,636 WARN [com.arjuna.ats.jta] (management-handler-thread - 1) ARJUNA016006: XAResourceRecord forget failed: - forget threw exception: javax.transaction.xa.XAException > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaForget(ActiveMQSessionContext.java:490) > at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.forget(ClientSessionImpl.java:1196) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.forget(ActiveMQXAResourceWrapper.java:123) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.forget(ActiveMQXAResourceWrapperImpl.java:86) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forget(XAResourceRecord.java:806) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forgetHeuristic(XAResourceRecord.java:792) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.removeFromList(LogRecordWrapper.java:238) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean$GenericAtomicActionWrapper.remove(ActionBean.java:463) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:327) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.remove(LogRecordWrapper.java:218) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475) > at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) > at org.jboss.as.txn.subsystem.LogStoreTransactionDeleteHandler.execute(LogStoreTransactionDeleteHandler.java:59) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 20 10:02:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 20 Mar 2018 10:02:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3001) MBean representing a transaction should consider state when is to be removed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3001: ---------------------------------- Attachment: standalone-full.xml data-tooling.zip data-subordinate.zip > MBean representing a transaction should consider state when is to be removed > ---------------------------------------------------------------------------- > > Key: JBTM-3001 > URL: https://issues.jboss.org/browse/JBTM-3001 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Attachments: data-subordinate.zip, data-tooling.zip, standalone-full.xml > > > When transaction mbean is to be removed by tooling - there is a transaction available in the object store and recovery does not catch it for deletion (the reason could be various - either the transaction is set with heuristic outcome, or transaction was subordinate and recovery waits for the outer player to finish transaction but there is nobody coming, or there is record in txn log store but the RA already forgot about transaction and we want to clean the transaction manager log store) - then currently the transaction manager just tries to call [XAResource.forget|https://docs.oracle.com/javaee/7/api/javax/transaction/xa/XAResource.html#forget-javax.transaction.xa.Xid-]. But the forget call is available (correct by the XA specification) only when the participant finished with in the heuristic state. > But deleting transaction by the tooling (even that should be only the tool of the last resort as normally recovery manager handles this automatically) should cause the transaction and all participants are correctly finished (forget or rolled-back) even the transaction is in prepared state (not in heuristic one). > When {{forget}} is called on prepared transaction branch then (e.g. for Artemis ActiveMQ) the {{XAException.XAER_NOTA}} is thrown[1]. > * The mbean should consider the state of the participant and choose if to rollback ({{prepared}} state) or if to forget ({{heuristic}} state). > * The mbean should consider to check {{XAException}} error code as when {{XAResource.forget}} returns {{XAER_NOTA}} (pubs.opengroup.org/onlinepubs/009680699/toc.pdf, {{The specified XID is not known by the resource manager as a heuristically completed XID.}}) then the branch is in incorrect state - probably it's prepared thus rollback could be run. > {code} > 2018-03-20 11:06:06,614 TRACE [com.arjuna.ats.jta] (management-handler-thread - 1) XAResourceRecord.forget for XAResourceRecord < resource:org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper at 25091a7a, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805b6:-19805d73:5ab0d062:1c, node_name=1, branch_uid=0:ffff0a2805b6:-19805d73:5ab0d062:23, subordinatenodename=null, eis_name=forgot eis name for: 1 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: ActiveMQ Artemis/2.0, jndiName: java:/JmsXA NodeId:c07b7f00-2c1e-11e8-9014-54e1ad661a0b com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 69af92f1 > > 2018-03-20 11:06:06,636 WARN [com.arjuna.ats.jta] (management-handler-thread - 1) ARJUNA016006: XAResourceRecord forget failed: - forget threw exception: javax.transaction.xa.XAException > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaForget(ActiveMQSessionContext.java:490) > at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.forget(ClientSessionImpl.java:1196) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.forget(ActiveMQXAResourceWrapper.java:123) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.forget(ActiveMQXAResourceWrapperImpl.java:86) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forget(XAResourceRecord.java:806) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forgetHeuristic(XAResourceRecord.java:792) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.removeFromList(LogRecordWrapper.java:238) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean$GenericAtomicActionWrapper.remove(ActionBean.java:463) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:327) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.remove(LogRecordWrapper.java:218) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475) > at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) > at org.jboss.as.txn.subsystem.LogStoreTransactionDeleteHandler.execute(LogStoreTransactionDeleteHandler.java:59) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 20 11:11:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 20 Mar 2018 11:11:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3001) MBean representing a transaction should consider state when is to be removed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1295 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > MBean representing a transaction should consider state when is to be removed > ---------------------------------------------------------------------------- > > Key: JBTM-3001 > URL: https://issues.jboss.org/browse/JBTM-3001 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Attachments: data-subordinate.zip, data-tooling.zip, standalone-full.xml > > > When transaction mbean is to be removed by tooling - there is a transaction available in the object store and recovery does not catch it for deletion (the reason could be various - either the transaction is set with heuristic outcome, or transaction was subordinate and recovery waits for the outer player to finish transaction but there is nobody coming, or there is record in txn log store but the RA already forgot about transaction and we want to clean the transaction manager log store) - then currently the transaction manager just tries to call [XAResource.forget|https://docs.oracle.com/javaee/7/api/javax/transaction/xa/XAResource.html#forget-javax.transaction.xa.Xid-]. But the forget call is available (correct by the XA specification) only when the participant finished with in the heuristic state. > But deleting transaction by the tooling (even that should be only the tool of the last resort as normally recovery manager handles this automatically) should cause the transaction and all participants are correctly finished (forget or rolled-back) even the transaction is in prepared state (not in heuristic one). > When {{forget}} is called on prepared transaction branch then (e.g. for Artemis ActiveMQ) the {{XAException.XAER_NOTA}} is thrown[1]. > * The mbean should consider the state of the participant and choose if to rollback ({{prepared}} state) or if to forget ({{heuristic}} state). > * The mbean should consider to check {{XAException}} error code as when {{XAResource.forget}} returns {{XAER_NOTA}} (pubs.opengroup.org/onlinepubs/009680699/toc.pdf, {{The specified XID is not known by the resource manager as a heuristically completed XID.}}) then the branch is in incorrect state - probably it's prepared thus rollback could be run. > {code} > 2018-03-20 11:06:06,614 TRACE [com.arjuna.ats.jta] (management-handler-thread - 1) XAResourceRecord.forget for XAResourceRecord < resource:org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper at 25091a7a, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805b6:-19805d73:5ab0d062:1c, node_name=1, branch_uid=0:ffff0a2805b6:-19805d73:5ab0d062:23, subordinatenodename=null, eis_name=forgot eis name for: 1 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: ActiveMQ Artemis/2.0, jndiName: java:/JmsXA NodeId:c07b7f00-2c1e-11e8-9014-54e1ad661a0b com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 69af92f1 > > 2018-03-20 11:06:06,636 WARN [com.arjuna.ats.jta] (management-handler-thread - 1) ARJUNA016006: XAResourceRecord forget failed: - forget threw exception: javax.transaction.xa.XAException > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaForget(ActiveMQSessionContext.java:490) > at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.forget(ClientSessionImpl.java:1196) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.forget(ActiveMQXAResourceWrapper.java:123) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.forget(ActiveMQXAResourceWrapperImpl.java:86) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forget(XAResourceRecord.java:806) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forgetHeuristic(XAResourceRecord.java:792) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.removeFromList(LogRecordWrapper.java:238) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean$GenericAtomicActionWrapper.remove(ActionBean.java:463) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:327) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.remove(LogRecordWrapper.java:218) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475) > at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) > at org.jboss.as.txn.subsystem.LogStoreTransactionDeleteHandler.execute(LogStoreTransactionDeleteHandler.java:59) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 20 15:35:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 20 Mar 2018 15:35:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3002) XTS integration tests fails on: SoapFault11: Callback wasn't triggered In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-3002: ------------------------------------- Summary: XTS integration tests fails on: SoapFault11: Callback wasn't triggered Key: JBTM-3002 URL: https://issues.jboss.org/browse/JBTM-3002 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Affects Versions: 5.8.0.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Critical There is failing XTS tests with {{com.arjuna.webservices11.SoapFault11: Receiver[Callback wasn't triggered]}}. This could be cause by some changes in WFLY server or it's some coincidence of wrong integration on the Narayana side. {code} INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl INFO [stdout] (default task-2) KEV: processing SOAP action http://fabrikam123.com/CompletionCommit ERROR [stderr] (default task-2) Proxy Listener Service: org.apache.http.client.ClientProtocolException ERROR [stderr] (default task-2) org.apache.http.client.ClientProtocolException ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.doRequest(HttpClientURLConnection.java:189) ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.connect(HttpClientURLConnection.java:205) ERROR [stderr] (default task-2) at com.jboss.transaction.txinterop.proxy.ProxyListenerService.doPost(ProxyListenerService.java:184) ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) ERROR [stderr] (default task-2) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) ERROR [stderr] (default task-2) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) ERROR [stderr] (default task-2) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) ERROR [stderr] (default task-2) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:748) ERROR [stderr] (default task-2) Caused by: org.apache.http.ProtocolException: Content-Length header already present ERROR [stderr] (default task-2) at org.apache.http.protocol.RequestContent.process(RequestContent.java:96) ERROR [stderr] (default task-2) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:132) ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:182) ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ERROR [stderr] (default task-2) ... 48 more INFO [stdout] (default task-1) KEV: removed conversation c1 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantReadOnly.ParticipantCompletionReadOnlyRules INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.ParticipantProcessorImpl INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.CoordinatorProcessorImpl INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: '/interop11' from server 'default-server' {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 20 16:39:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 20 Mar 2018 16:39:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3002) XTS integration tests fails on: SoapFault11: Callback wasn't triggered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548782#comment-13548782 ] Ondra Chaloupka commented on JBTM-3002: --------------------------------------- it seems the failures start to be seen when version of WFLY core happens (https://issues.jboss.org/browse/WFLY-10013). Now investigation will continue to check if it's currently issue of integration at Narayana side or there is some omission at WFLY. > XTS integration tests fails on: SoapFault11: Callback wasn't triggered > ---------------------------------------------------------------------- > > Key: JBTM-3002 > URL: https://issues.jboss.org/browse/JBTM-3002 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > There is failing XTS tests with {{com.arjuna.webservices11.SoapFault11: Receiver[Callback wasn't triggered]}}. > This could be cause by some changes in WFLY server or it's some coincidence of wrong integration on the Narayana side. > {code} > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [stdout] (default task-2) KEV: processing SOAP action http://fabrikam123.com/CompletionCommit > ERROR [stderr] (default task-2) Proxy Listener Service: org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.doRequest(HttpClientURLConnection.java:189) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.connect(HttpClientURLConnection.java:205) > ERROR [stderr] (default task-2) at com.jboss.transaction.txinterop.proxy.ProxyListenerService.doPost(ProxyListenerService.java:184) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > ERROR [stderr] (default task-2) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:748) > ERROR [stderr] (default task-2) Caused by: org.apache.http.ProtocolException: Content-Length header already present > ERROR [stderr] (default task-2) at org.apache.http.protocol.RequestContent.process(RequestContent.java:96) > ERROR [stderr] (default task-2) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:132) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:182) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > ERROR [stderr] (default task-2) ... 48 more > INFO [stdout] (default task-1) KEV: removed conversation c1 > INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantReadOnly.ParticipantCompletionReadOnlyRules > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.ParticipantProcessorImpl > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.CoordinatorProcessorImpl > INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: '/interop11' from server 'default-server' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 20 16:40:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 20 Mar 2018 16:40:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3002) XTS integration tests fails on: SoapFault11: Callback wasn't triggered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548782#comment-13548782 ] Ondra Chaloupka edited comment on JBTM-3002 at 3/20/18 4:39 PM: ---------------------------------------------------------------- it seems the failures start to be seen when version of WFLY core happens (https://issues.jboss.org/browse/WFLY-10013, WFLY commit {{fb308b9422}}). Now investigation will continue to check if it's currently issue of integration at Narayana side or there is some omission at WFLY. was (Author: ochaloup): it seems the failures start to be seen when version of WFLY core happens (https://issues.jboss.org/browse/WFLY-10013). Now investigation will continue to check if it's currently issue of integration at Narayana side or there is some omission at WFLY. > XTS integration tests fails on: SoapFault11: Callback wasn't triggered > ---------------------------------------------------------------------- > > Key: JBTM-3002 > URL: https://issues.jboss.org/browse/JBTM-3002 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > There is failing XTS tests with {{com.arjuna.webservices11.SoapFault11: Receiver[Callback wasn't triggered]}}. > This could be cause by some changes in WFLY server or it's some coincidence of wrong integration on the Narayana side. > {code} > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [stdout] (default task-2) KEV: processing SOAP action http://fabrikam123.com/CompletionCommit > ERROR [stderr] (default task-2) Proxy Listener Service: org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.doRequest(HttpClientURLConnection.java:189) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.connect(HttpClientURLConnection.java:205) > ERROR [stderr] (default task-2) at com.jboss.transaction.txinterop.proxy.ProxyListenerService.doPost(ProxyListenerService.java:184) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > ERROR [stderr] (default task-2) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:748) > ERROR [stderr] (default task-2) Caused by: org.apache.http.ProtocolException: Content-Length header already present > ERROR [stderr] (default task-2) at org.apache.http.protocol.RequestContent.process(RequestContent.java:96) > ERROR [stderr] (default task-2) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:132) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:182) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > ERROR [stderr] (default task-2) ... 48 more > INFO [stdout] (default task-1) KEV: removed conversation c1 > INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantReadOnly.ParticipantCompletionReadOnlyRules > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.ParticipantProcessorImpl > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.CoordinatorProcessorImpl > INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: '/interop11' from server 'default-server' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Mar 21 13:41:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 21 Mar 2018 13:41:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3001) MBean representing a transaction should consider state when is to be removed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549327#comment-13549327 ] Ondra Chaloupka commented on JBTM-3001: --------------------------------------- Per discussion with [~mmusgrov] the records in {{prepared}} state should not be permitted to be removed by the tooling. The prepared records in the object store is expected to be managed by recovery manager - either they will be committed or rolled-back as orphans. The {{delete}} operation (remove of the mbean) is expected to handle only(*!*) heuristically finished transactions. > MBean representing a transaction should consider state when is to be removed > ---------------------------------------------------------------------------- > > Key: JBTM-3001 > URL: https://issues.jboss.org/browse/JBTM-3001 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Attachments: data-subordinate.zip, data-tooling.zip, standalone-full.xml > > > When transaction mbean is to be removed by tooling - there is a transaction available in the object store and recovery does not catch it for deletion (the reason could be various - either the transaction is set with heuristic outcome, or transaction was subordinate and recovery waits for the outer player to finish transaction but there is nobody coming, or there is record in txn log store but the RA already forgot about transaction and we want to clean the transaction manager log store) - then currently the transaction manager just tries to call [XAResource.forget|https://docs.oracle.com/javaee/7/api/javax/transaction/xa/XAResource.html#forget-javax.transaction.xa.Xid-]. But the forget call is available (correct by the XA specification) only when the participant finished with in the heuristic state. > But deleting transaction by the tooling (even that should be only the tool of the last resort as normally recovery manager handles this automatically) should cause the transaction and all participants are correctly finished (forget or rolled-back) even the transaction is in prepared state (not in heuristic one). > When {{forget}} is called on prepared transaction branch then (e.g. for Artemis ActiveMQ) the {{XAException.XAER_NOTA}} is thrown[1]. > * The mbean should consider the state of the participant and choose if to rollback ({{prepared}} state) or if to forget ({{heuristic}} state). > * The mbean should consider to check {{XAException}} error code as when {{XAResource.forget}} returns {{XAER_NOTA}} (pubs.opengroup.org/onlinepubs/009680699/toc.pdf, {{The specified XID is not known by the resource manager as a heuristically completed XID.}}) then the branch is in incorrect state - probably it's prepared thus rollback could be run. > {code} > 2018-03-20 11:06:06,614 TRACE [com.arjuna.ats.jta] (management-handler-thread - 1) XAResourceRecord.forget for XAResourceRecord < resource:org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper at 25091a7a, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805b6:-19805d73:5ab0d062:1c, node_name=1, branch_uid=0:ffff0a2805b6:-19805d73:5ab0d062:23, subordinatenodename=null, eis_name=forgot eis name for: 1 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: ActiveMQ Artemis/2.0, jndiName: java:/JmsXA NodeId:c07b7f00-2c1e-11e8-9014-54e1ad661a0b com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 69af92f1 > > 2018-03-20 11:06:06,636 WARN [com.arjuna.ats.jta] (management-handler-thread - 1) ARJUNA016006: XAResourceRecord forget failed: - forget threw exception: javax.transaction.xa.XAException > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaForget(ActiveMQSessionContext.java:490) > at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.forget(ClientSessionImpl.java:1196) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.forget(ActiveMQXAResourceWrapper.java:123) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.forget(ActiveMQXAResourceWrapperImpl.java:86) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forget(XAResourceRecord.java:806) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forgetHeuristic(XAResourceRecord.java:792) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.removeFromList(LogRecordWrapper.java:238) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean$GenericAtomicActionWrapper.remove(ActionBean.java:463) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:327) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.remove(LogRecordWrapper.java:218) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475) > at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) > at org.jboss.as.txn.subsystem.LogStoreTransactionDeleteHandler.execute(LogStoreTransactionDeleteHandler.java:59) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Mar 26 08:36:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 26 Mar 2018 08:36:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3003) standalone-xts.xml is not found in WS-AT performance tests In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-3003: ----------------------------------- Summary: standalone-xts.xml is not found in WS-AT performance tests Key: JBTM-3003 URL: https://issues.jboss.org/browse/JBTM-3003 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing, XTS Reporter: Tom Jenkinson Assignee: Michael Musgrove [INFO] ------------------------------------------------------------------------ [INFO] Building ws-at 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ws-at --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ws-at --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/hudson/workspace/narayana-performance/comparison/ws-at/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ ws-at --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 8 source files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ ws-at --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ ws-at --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 1 source file to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/test-classes [INFO] [INFO] --- maven-antrun-plugin:1.7:run (default) @ ws-at --- [INFO] Executing tasks main: [copy] Copying 12826 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server1 [copy] Copied 4874 empty directories to 143 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server1 [copy] Copying 25652 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server2 [copy] Copied 9748 empty directories to 286 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server2 [copy] Copying 51304 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server3 [copy] Copied 19496 empty directories to 572 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server3 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] comparison-parent .................................. SUCCESS [ 0.189 s] [INFO] common ............................................. SUCCESS [ 1.305 s] [INFO] ws-at .............................................. FAILURE [ 30.599 s] [INFO] rest-at ............................................ SKIPPED [INFO] jts ................................................ SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 32.244 s [INFO] Finished at: 2018-03-25T00:07:53+00:00 [INFO] Final Memory: 62M/680M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project ws-at: An Ant BuildException has occured: Warning: Could not find file /home/hudson/workspace/narayana-performance/docs/examples/configs/standalone-xts.xml to copy. [ERROR] around Ant part ...... @ 13:232 in /home/hudson/workspace/narayana-performance/comparison/ws-at/target/antrun/build-main.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 04:37:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Mar 2018 04:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3003) standalone-xts.xml is not found in WS-AT performance tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka reassigned JBTM-3003: ------------------------------------- Assignee: Ondra Chaloupka (was: Michael Musgrove) > standalone-xts.xml is not found in WS-AT performance tests > ---------------------------------------------------------- > > Key: JBTM-3003 > URL: https://issues.jboss.org/browse/JBTM-3003 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, XTS > Reporter: Tom Jenkinson > Assignee: Ondra Chaloupka > > [INFO] ------------------------------------------------------------------------ > [INFO] Building ws-at 1.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ws-at --- > [INFO] > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ws-at --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/hudson/workspace/narayana-performance/comparison/ws-at/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ ws-at --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 8 source files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/classes > [INFO] > [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ ws-at --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 2 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ ws-at --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 1 source file to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/test-classes > [INFO] > [INFO] --- maven-antrun-plugin:1.7:run (default) @ ws-at --- > [INFO] Executing tasks > main: > [copy] Copying 12826 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server1 > [copy] Copied 4874 empty directories to 143 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server1 > [copy] Copying 25652 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server2 > [copy] Copied 9748 empty directories to 286 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server2 > [copy] Copying 51304 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server3 > [copy] Copied 19496 empty directories to 572 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server3 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] comparison-parent .................................. SUCCESS [ 0.189 s] > [INFO] common ............................................. SUCCESS [ 1.305 s] > [INFO] ws-at .............................................. FAILURE [ 30.599 s] > [INFO] rest-at ............................................ SKIPPED > [INFO] jts ................................................ SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 32.244 s > [INFO] Finished at: 2018-03-25T00:07:53+00:00 > [INFO] Final Memory: 62M/680M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project ws-at: An Ant BuildException has occured: Warning: Could not find file /home/hudson/workspace/narayana-performance/docs/examples/configs/standalone-xts.xml to copy. > [ERROR] around Ant part ...... @ 13:232 in /home/hudson/workspace/narayana-performance/comparison/ws-at/target/antrun/build-main.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 06:00:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 27 Mar 2018 06:00:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3001) MBean representing a transaction should consider state when is to be removed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551941#comment-13551941 ] Michael Musgrove commented on JBTM-3001: ---------------------------------------- [~ochaloup] I never said that "records in prepared state should not be permitted to be removed by the tooling". What I did say was {quote} Well if the admin knows it is safe to remove a prepared transaction then the tooling should allow him to do that (but ideally prepared transactions should be left to the recovery manager and the delete operation is provided as a last resort). {quote} > MBean representing a transaction should consider state when is to be removed > ---------------------------------------------------------------------------- > > Key: JBTM-3001 > URL: https://issues.jboss.org/browse/JBTM-3001 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Attachments: data-subordinate.zip, data-tooling.zip, standalone-full.xml > > > When transaction mbean is to be removed by tooling - there is a transaction available in the object store and recovery does not catch it for deletion (the reason could be various - either the transaction is set with heuristic outcome, or transaction was subordinate and recovery waits for the outer player to finish transaction but there is nobody coming, or there is record in txn log store but the RA already forgot about transaction and we want to clean the transaction manager log store) - then currently the transaction manager just tries to call [XAResource.forget|https://docs.oracle.com/javaee/7/api/javax/transaction/xa/XAResource.html#forget-javax.transaction.xa.Xid-]. But the forget call is available (correct by the XA specification) only when the participant finished with in the heuristic state. > But deleting transaction by the tooling (even that should be only the tool of the last resort as normally recovery manager handles this automatically) should cause the transaction and all participants are correctly finished (forget or rolled-back) even the transaction is in prepared state (not in heuristic one). > When {{forget}} is called on prepared transaction branch then (e.g. for Artemis ActiveMQ) the {{XAException.XAER_NOTA}} is thrown[1]. > * The mbean should consider the state of the participant and choose if to rollback ({{prepared}} state) or if to forget ({{heuristic}} state). > * The mbean should consider to check {{XAException}} error code as when {{XAResource.forget}} returns {{XAER_NOTA}} (pubs.opengroup.org/onlinepubs/009680699/toc.pdf, {{The specified XID is not known by the resource manager as a heuristically completed XID.}}) then the branch is in incorrect state - probably it's prepared thus rollback could be run. > {code} > 2018-03-20 11:06:06,614 TRACE [com.arjuna.ats.jta] (management-handler-thread - 1) XAResourceRecord.forget for XAResourceRecord < resource:org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper at 25091a7a, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805b6:-19805d73:5ab0d062:1c, node_name=1, branch_uid=0:ffff0a2805b6:-19805d73:5ab0d062:23, subordinatenodename=null, eis_name=forgot eis name for: 1 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: ActiveMQ Artemis/2.0, jndiName: java:/JmsXA NodeId:c07b7f00-2c1e-11e8-9014-54e1ad661a0b com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 69af92f1 > > 2018-03-20 11:06:06,636 WARN [com.arjuna.ats.jta] (management-handler-thread - 1) ARJUNA016006: XAResourceRecord forget failed: - forget threw exception: javax.transaction.xa.XAException > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaForget(ActiveMQSessionContext.java:490) > at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.forget(ClientSessionImpl.java:1196) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.forget(ActiveMQXAResourceWrapper.java:123) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.forget(ActiveMQXAResourceWrapperImpl.java:86) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forget(XAResourceRecord.java:806) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forgetHeuristic(XAResourceRecord.java:792) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.removeFromList(LogRecordWrapper.java:238) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean$GenericAtomicActionWrapper.remove(ActionBean.java:463) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:327) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.remove(LogRecordWrapper.java:218) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475) > at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) > at org.jboss.as.txn.subsystem.LogStoreTransactionDeleteHandler.execute(LogStoreTransactionDeleteHandler.java:59) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 08:17:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Mar 2018 08:17:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3001) MBean representing a transaction should consider state when is to be removed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552053#comment-13552053 ] Ondra Chaloupka commented on JBTM-3001: --------------------------------------- [~mmusgrov] I see, thank you for clarification Mike. That was my wrong understanding which I've already adjusted just I haven't updated the issue here. I got the point (at least I hope :) > MBean representing a transaction should consider state when is to be removed > ---------------------------------------------------------------------------- > > Key: JBTM-3001 > URL: https://issues.jboss.org/browse/JBTM-3001 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Attachments: data-subordinate.zip, data-tooling.zip, standalone-full.xml > > > When transaction mbean is to be removed by tooling - there is a transaction available in the object store and recovery does not catch it for deletion (the reason could be various - either the transaction is set with heuristic outcome, or transaction was subordinate and recovery waits for the outer player to finish transaction but there is nobody coming, or there is record in txn log store but the RA already forgot about transaction and we want to clean the transaction manager log store) - then currently the transaction manager just tries to call [XAResource.forget|https://docs.oracle.com/javaee/7/api/javax/transaction/xa/XAResource.html#forget-javax.transaction.xa.Xid-]. But the forget call is available (correct by the XA specification) only when the participant finished with in the heuristic state. > But deleting transaction by the tooling (even that should be only the tool of the last resort as normally recovery manager handles this automatically) should cause the transaction and all participants are correctly finished (forget or rolled-back) even the transaction is in prepared state (not in heuristic one). > When {{forget}} is called on prepared transaction branch then (e.g. for Artemis ActiveMQ) the {{XAException.XAER_NOTA}} is thrown[1]. > * The mbean should consider the state of the participant and choose if to rollback ({{prepared}} state) or if to forget ({{heuristic}} state). > * The mbean should consider to check {{XAException}} error code as when {{XAResource.forget}} returns {{XAER_NOTA}} (pubs.opengroup.org/onlinepubs/009680699/toc.pdf, {{The specified XID is not known by the resource manager as a heuristically completed XID.}}) then the branch is in incorrect state - probably it's prepared thus rollback could be run. > {code} > 2018-03-20 11:06:06,614 TRACE [com.arjuna.ats.jta] (management-handler-thread - 1) XAResourceRecord.forget for XAResourceRecord < resource:org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper at 25091a7a, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805b6:-19805d73:5ab0d062:1c, node_name=1, branch_uid=0:ffff0a2805b6:-19805d73:5ab0d062:23, subordinatenodename=null, eis_name=forgot eis name for: 1 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: ActiveMQ Artemis/2.0, jndiName: java:/JmsXA NodeId:c07b7f00-2c1e-11e8-9014-54e1ad661a0b com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 69af92f1 > > 2018-03-20 11:06:06,636 WARN [com.arjuna.ats.jta] (management-handler-thread - 1) ARJUNA016006: XAResourceRecord forget failed: - forget threw exception: javax.transaction.xa.XAException > at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaForget(ActiveMQSessionContext.java:490) > at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.forget(ClientSessionImpl.java:1196) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.forget(ActiveMQXAResourceWrapper.java:123) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.forget(ActiveMQXAResourceWrapperImpl.java:86) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forget(XAResourceRecord.java:806) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forgetHeuristic(XAResourceRecord.java:792) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.removeFromList(LogRecordWrapper.java:238) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean$GenericAtomicActionWrapper.remove(ActionBean.java:463) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:327) > at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.remove(LogRecordWrapper.java:218) > at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:149) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475) > at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724) > at org.jboss.as.txn.subsystem.LogStoreTransactionDeleteHandler.execute(LogStoreTransactionDeleteHandler.java:59) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 08:40:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Mar 2018 08:40:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3003) standalone-xts.xml is not found in WS-AT performance tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #44 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > standalone-xts.xml is not found in WS-AT performance tests > ---------------------------------------------------------- > > Key: JBTM-3003 > URL: https://issues.jboss.org/browse/JBTM-3003 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, XTS > Reporter: Tom Jenkinson > Assignee: Ondra Chaloupka > > [INFO] ------------------------------------------------------------------------ > [INFO] Building ws-at 1.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ws-at --- > [INFO] > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ws-at --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/hudson/workspace/narayana-performance/comparison/ws-at/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ ws-at --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 8 source files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/classes > [INFO] > [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ ws-at --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 2 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ ws-at --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 1 source file to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/test-classes > [INFO] > [INFO] --- maven-antrun-plugin:1.7:run (default) @ ws-at --- > [INFO] Executing tasks > main: > [copy] Copying 12826 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server1 > [copy] Copied 4874 empty directories to 143 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server1 > [copy] Copying 25652 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server2 > [copy] Copied 9748 empty directories to 286 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server2 > [copy] Copying 51304 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server3 > [copy] Copied 19496 empty directories to 572 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server3 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] comparison-parent .................................. SUCCESS [ 0.189 s] > [INFO] common ............................................. SUCCESS [ 1.305 s] > [INFO] ws-at .............................................. FAILURE [ 30.599 s] > [INFO] rest-at ............................................ SKIPPED > [INFO] jts ................................................ SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 32.244 s > [INFO] Finished at: 2018-03-25T00:07:53+00:00 > [INFO] Final Memory: 62M/680M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project ws-at: An Ant BuildException has occured: Warning: Could not find file /home/hudson/workspace/narayana-performance/docs/examples/configs/standalone-xts.xml to copy. > [ERROR] around Ant part ...... @ 13:232 in /home/hudson/workspace/narayana-performance/comparison/ws-at/target/antrun/build-main.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 09:03:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Mar 2018 09:03:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3002) XTS integration tests fails on: SoapFault11: Callback wasn't triggered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3002: ---------------------------------- Steps to Reproduce: * build WFLY * {{export JBOSS_HOME=$WFLY_HOME}} * {{cp $JBOSS_HOME/docs/examples/configs/standalone-xts.xml $JBOSS_HOME/standalone/configuration/ && sed -i 's/\\( XTS integration tests fails on: SoapFault11: Callback wasn't triggered > ---------------------------------------------------------------------- > > Key: JBTM-3002 > URL: https://issues.jboss.org/browse/JBTM-3002 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > There is failing XTS tests with {{com.arjuna.webservices11.SoapFault11: Receiver[Callback wasn't triggered]}}. > This could be cause by some changes in WFLY server or it's some coincidence of wrong integration on the Narayana side. > {code} > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [stdout] (default task-2) KEV: processing SOAP action http://fabrikam123.com/CompletionCommit > ERROR [stderr] (default task-2) Proxy Listener Service: org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.doRequest(HttpClientURLConnection.java:189) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.connect(HttpClientURLConnection.java:205) > ERROR [stderr] (default task-2) at com.jboss.transaction.txinterop.proxy.ProxyListenerService.doPost(ProxyListenerService.java:184) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > ERROR [stderr] (default task-2) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:748) > ERROR [stderr] (default task-2) Caused by: org.apache.http.ProtocolException: Content-Length header already present > ERROR [stderr] (default task-2) at org.apache.http.protocol.RequestContent.process(RequestContent.java:96) > ERROR [stderr] (default task-2) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:132) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:182) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > ERROR [stderr] (default task-2) ... 48 more > INFO [stdout] (default task-1) KEV: removed conversation c1 > INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantReadOnly.ParticipantCompletionReadOnlyRules > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.ParticipantProcessorImpl > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.CoordinatorProcessorImpl > INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: '/interop11' from server 'default-server' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 09:03:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Mar 2018 09:03:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3002) XTS integration tests fails on: SoapFault11: Callback wasn't triggered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3002: ---------------------------------- Steps to Reproduce: * build WFLY * {{export JBOSS_HOME=$WFLY_HOME}} * {{cp $JBOSS_HOME/docs/examples/configs/standalone-xts.xml $JBOSS_HOME/standalone/configuration/ && sed -i 's/( XTS integration tests fails on: SoapFault11: Callback wasn't triggered > ---------------------------------------------------------------------- > > Key: JBTM-3002 > URL: https://issues.jboss.org/browse/JBTM-3002 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > There is failing XTS tests with {{com.arjuna.webservices11.SoapFault11: Receiver[Callback wasn't triggered]}}. > This could be cause by some changes in WFLY server or it's some coincidence of wrong integration on the Narayana side. > {code} > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [stdout] (default task-2) KEV: processing SOAP action http://fabrikam123.com/CompletionCommit > ERROR [stderr] (default task-2) Proxy Listener Service: org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.doRequest(HttpClientURLConnection.java:189) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.connect(HttpClientURLConnection.java:205) > ERROR [stderr] (default task-2) at com.jboss.transaction.txinterop.proxy.ProxyListenerService.doPost(ProxyListenerService.java:184) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > ERROR [stderr] (default task-2) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:748) > ERROR [stderr] (default task-2) Caused by: org.apache.http.ProtocolException: Content-Length header already present > ERROR [stderr] (default task-2) at org.apache.http.protocol.RequestContent.process(RequestContent.java:96) > ERROR [stderr] (default task-2) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:132) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:182) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > ERROR [stderr] (default task-2) ... 48 more > INFO [stdout] (default task-1) KEV: removed conversation c1 > INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantReadOnly.ParticipantCompletionReadOnlyRules > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.ParticipantProcessorImpl > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.CoordinatorProcessorImpl > INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: '/interop11' from server 'default-server' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 09:05:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Mar 2018 09:05:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3002) XTS integration tests fails on: SoapFault11: Callback wasn't triggered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3002: ---------------------------------- Steps to Reproduce: # build WFLY # clone narayana {{git clone https://github.com/jbosstm/narayana}} * {{cd narayana/XTS/localjunit/WSTX11-interop}} * {{mvn clean install -Parq -Dtest=ATTest#testAT1_1}} {code:bash} export JBOSS_HOME=$WFLY_HOME export NARAYANA_HOME="$PWD/narayana" cp $JBOSS_HOME/docs/examples/configs/standalone-xts.xml $JBOSS_HOME/standalone/configuration/ &&\ sed -i 's/\( XTS integration tests fails on: SoapFault11: Callback wasn't triggered > ---------------------------------------------------------------------- > > Key: JBTM-3002 > URL: https://issues.jboss.org/browse/JBTM-3002 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > There is failing XTS tests with {{com.arjuna.webservices11.SoapFault11: Receiver[Callback wasn't triggered]}}. > This could be cause by some changes in WFLY server or it's some coincidence of wrong integration on the Narayana side. > {code} > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [stdout] (default task-2) KEV: processing SOAP action http://fabrikam123.com/CompletionCommit > ERROR [stderr] (default task-2) Proxy Listener Service: org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.doRequest(HttpClientURLConnection.java:189) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.connect(HttpClientURLConnection.java:205) > ERROR [stderr] (default task-2) at com.jboss.transaction.txinterop.proxy.ProxyListenerService.doPost(ProxyListenerService.java:184) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > ERROR [stderr] (default task-2) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:748) > ERROR [stderr] (default task-2) Caused by: org.apache.http.ProtocolException: Content-Length header already present > ERROR [stderr] (default task-2) at org.apache.http.protocol.RequestContent.process(RequestContent.java:96) > ERROR [stderr] (default task-2) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:132) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:182) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > ERROR [stderr] (default task-2) ... 48 more > INFO [stdout] (default task-1) KEV: removed conversation c1 > INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantReadOnly.ParticipantCompletionReadOnlyRules > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.ParticipantProcessorImpl > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.CoordinatorProcessorImpl > INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: '/interop11' from server 'default-server' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 09:05:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Mar 2018 09:05:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3002) XTS integration tests fails on: SoapFault11: Callback wasn't triggered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3002: ---------------------------------- Steps to Reproduce: # build WFLY # clone narayana {{git clone https://github.com/jbosstm/narayana}} {code:bash} export JBOSS_HOME=$WFLY_HOME export NARAYANA_HOME="$PWD/narayana" cp $JBOSS_HOME/docs/examples/configs/standalone-xts.xml $JBOSS_HOME/standalone/configuration/ &&\ sed -i 's/\( XTS integration tests fails on: SoapFault11: Callback wasn't triggered > ---------------------------------------------------------------------- > > Key: JBTM-3002 > URL: https://issues.jboss.org/browse/JBTM-3002 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > There is failing XTS tests with {{com.arjuna.webservices11.SoapFault11: Receiver[Callback wasn't triggered]}}. > This could be cause by some changes in WFLY server or it's some coincidence of wrong integration on the Narayana side. > {code} > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [stdout] (default task-2) KEV: processing SOAP action http://fabrikam123.com/CompletionCommit > ERROR [stderr] (default task-2) Proxy Listener Service: org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.doRequest(HttpClientURLConnection.java:189) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.connect(HttpClientURLConnection.java:205) > ERROR [stderr] (default task-2) at com.jboss.transaction.txinterop.proxy.ProxyListenerService.doPost(ProxyListenerService.java:184) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > ERROR [stderr] (default task-2) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:748) > ERROR [stderr] (default task-2) Caused by: org.apache.http.ProtocolException: Content-Length header already present > ERROR [stderr] (default task-2) at org.apache.http.protocol.RequestContent.process(RequestContent.java:96) > ERROR [stderr] (default task-2) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:132) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:182) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > ERROR [stderr] (default task-2) ... 48 more > INFO [stdout] (default task-1) KEV: removed conversation c1 > INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantReadOnly.ParticipantCompletionReadOnlyRules > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.ParticipantProcessorImpl > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.CoordinatorProcessorImpl > INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: '/interop11' from server 'default-server' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 09:14:02 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 27 Mar 2018 09:14:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2685: -------------------------------- Description: **(some commits that reference this issue are actually for https://issues.jboss.org/browse/JBTM-2955)** Get the latest build from https://jdk9.java.net/download/ and check for any issues. was:Get the latest build from https://jdk9.java.net/download/ and check for any issues. > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > > **(some commits that reference this issue are actually for https://issues.jboss.org/browse/JBTM-2955)** > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 10:35:05 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Mar 2018 10:35:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3002) XTS integration tests fails on: SoapFault11: Callback wasn't triggered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3002: ---------------------------------- Steps to Reproduce: # build WFLY # clone narayana {{git clone https://github.com/jbosstm/narayana}} {code:bash} export JBOSS_HOME=$WFLY_HOME export NARAYANA_HOME="$PWD/narayana" cp $JBOSS_HOME/docs/examples/configs/standalone-xts.xml $JBOSS_HOME/standalone/configuration/ &&\ sed -i 's/\( XTS integration tests fails on: SoapFault11: Callback wasn't triggered > ---------------------------------------------------------------------- > > Key: JBTM-3002 > URL: https://issues.jboss.org/browse/JBTM-3002 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > There is failing XTS tests with {{com.arjuna.webservices11.SoapFault11: Receiver[Callback wasn't triggered]}}. > This could be cause by some changes in WFLY server or it's some coincidence of wrong integration on the Narayana side. > {code} > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [stdout] (default task-2) KEV: processing SOAP action http://fabrikam123.com/CompletionCommit > ERROR [stderr] (default task-2) Proxy Listener Service: org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.doRequest(HttpClientURLConnection.java:189) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.connect(HttpClientURLConnection.java:205) > ERROR [stderr] (default task-2) at com.jboss.transaction.txinterop.proxy.ProxyListenerService.doPost(ProxyListenerService.java:184) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > ERROR [stderr] (default task-2) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:748) > ERROR [stderr] (default task-2) Caused by: org.apache.http.ProtocolException: Content-Length header already present > ERROR [stderr] (default task-2) at org.apache.http.protocol.RequestContent.process(RequestContent.java:96) > ERROR [stderr] (default task-2) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:132) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:182) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > ERROR [stderr] (default task-2) ... 48 more > INFO [stdout] (default task-1) KEV: removed conversation c1 > INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantReadOnly.ParticipantCompletionReadOnlyRules > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.ParticipantProcessorImpl > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.CoordinatorProcessorImpl > INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: '/interop11' from server 'default-server' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Mar 27 16:20:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Mar 2018 16:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3003) standalone-xts.xml is not found in WS-AT performance tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552416#comment-13552416 ] Ondra Chaloupka commented on JBTM-3003: --------------------------------------- the trouble is about downloading WFLY from the correct location and fixing arquillian dependencies to get all working > standalone-xts.xml is not found in WS-AT performance tests > ---------------------------------------------------------- > > Key: JBTM-3003 > URL: https://issues.jboss.org/browse/JBTM-3003 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, XTS > Reporter: Tom Jenkinson > Assignee: Ondra Chaloupka > > [INFO] ------------------------------------------------------------------------ > [INFO] Building ws-at 1.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ ws-at --- > [INFO] > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ws-at --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/hudson/workspace/narayana-performance/comparison/ws-at/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ ws-at --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 8 source files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/classes > [INFO] > [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ ws-at --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 2 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ ws-at --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 1 source file to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/test-classes > [INFO] > [INFO] --- maven-antrun-plugin:1.7:run (default) @ ws-at --- > [INFO] Executing tasks > main: > [copy] Copying 12826 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server1 > [copy] Copied 4874 empty directories to 143 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server1 > [copy] Copying 25652 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server2 > [copy] Copied 9748 empty directories to 286 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server2 > [copy] Copying 51304 files to /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server3 > [copy] Copied 19496 empty directories to 572 empty directories under /home/hudson/workspace/narayana-performance/comparison/ws-at/target/server3 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] comparison-parent .................................. SUCCESS [ 0.189 s] > [INFO] common ............................................. SUCCESS [ 1.305 s] > [INFO] ws-at .............................................. FAILURE [ 30.599 s] > [INFO] rest-at ............................................ SKIPPED > [INFO] jts ................................................ SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 32.244 s > [INFO] Finished at: 2018-03-25T00:07:53+00:00 > [INFO] Final Memory: 62M/680M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project ws-at: An Ant BuildException has occured: Warning: Could not find file /home/hudson/workspace/narayana-performance/docs/examples/configs/standalone-xts.xml to copy. > [ERROR] around Ant part ...... @ 13:232 in /home/hudson/workspace/narayana-performance/comparison/ws-at/target/antrun/build-main.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Mar 28 05:21:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 28 Mar 2018 05:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3002) XTS integration tests fails on: SoapFault11: Callback wasn't triggered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552611#comment-13552611 ] Ondra Chaloupka commented on JBTM-3002: --------------------------------------- My investigation continued to the point that: * header {{Content-Length}} is added to the out-coming message (see error {{Content-Length header already present}} in the stacktrace) and the {{apache.http library}} does not permit it. The header is added at https://github.com/jbosstm/narayana/blob/master/XTS/localjunit/WSTFSC07-interop/src/main/java/com/jboss/transaction/wstf/proxy/ProxyListenerService.java#L182 * the change in the work is that there is change in underlaying class of the {{URLConnection}} that we call {{HttpURLConnection.setRequestProperty}} on. The change is from using {code} sun.net.www.protocol.http.HttpURLConnection HttpURLConnection.isRestrictedHeader(String, String) line: 470 HttpURLConnection.isExternalMessageHeaderAllowed(String, String) line: 493 HttpURLConnection.setRequestProperty(String, String) line: 3075 {code} to {code} HttpClientURLConnection(URLConnection).setRequestProperty(String, String) line: 1078 java.net.HttpClientURLConnection {code} In the prior implementation there was called method {{HttpURLConnection.isRestrictedHeader}} which does not allow the {{Content-Length}} to be added to the out-comming call (but what I understand in some case (?) it was permitted). More investigation what is purpose of the change and how to avoid error is needed to be done. > XTS integration tests fails on: SoapFault11: Callback wasn't triggered > ---------------------------------------------------------------------- > > Key: JBTM-3002 > URL: https://issues.jboss.org/browse/JBTM-3002 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.8.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > There is failing XTS tests with {{com.arjuna.webservices11.SoapFault11: Receiver[Callback wasn't triggered]}}. > This could be cause by some changes in WFLY server or it's some coincidence of wrong integration on the Narayana side. > {code} > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://fabrikam123.com}ParticipantService from WSDL: vfs:/content/interop11.war/WEB-INF/classes/com/jboss/transaction/txinterop/webservices/atinterop/generated/wsdl/interopat-participant-binding.wsdl > INFO [stdout] (default task-2) KEV: processing SOAP action http://fabrikam123.com/CompletionCommit > ERROR [stderr] (default task-2) Proxy Listener Service: org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) org.apache.http.client.ClientProtocolException > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.doRequest(HttpClientURLConnection.java:189) > ERROR [stderr] (default task-2) at org.wildfly.url.http.HttpClientURLConnection.connect(HttpClientURLConnection.java:205) > ERROR [stderr] (default task-2) at com.jboss.transaction.txinterop.proxy.ProxyListenerService.doPost(ProxyListenerService.java:184) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > ERROR [stderr] (default task-2) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) > ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > ERROR [stderr] (default task-2) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1523) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) > ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > ERROR [stderr] (default task-2) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > ERROR [stderr] (default task-2) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:748) > ERROR [stderr] (default task-2) Caused by: org.apache.http.ProtocolException: Content-Length header already present > ERROR [stderr] (default task-2) at org.apache.http.protocol.RequestContent.process(RequestContent.java:96) > ERROR [stderr] (default task-2) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:132) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:182) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) > ERROR [stderr] (default task-2) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) > ERROR [stderr] (default task-2) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > ERROR [stderr] (default task-2) ... 48 more > INFO [stdout] (default task-1) KEV: removed conversation c1 > INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantReadOnly.ParticipantCompletionReadOnlyRules > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.ParticipantProcessorImpl > INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.CoordinatorProcessorImpl > INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: '/interop11' from server 'default-server' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Mar 28 08:56:00 2018 From: issues at jboss.org (Michal Karm Babacek (JIRA)) Date: Wed, 28 Mar 2018 08:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3004) "Connection is already associated with a different transaction" with Tomcat JDBC pool, XA In-Reply-To: References: Message-ID: Michal Karm Babacek created JBTM-3004: ----------------------------------------- Summary: "Connection is already associated with a different transaction" with Tomcat JDBC pool, XA Key: JBTM-3004 URL: https://issues.jboss.org/browse/JBTM-3004 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.next Environment: Tomcat 9.0.4, Tomcat JDBC Pool, PostgreSQL 10, Oracle JDK 8, Centos 7 x86_64 Reporter: Michal Karm Babacek Assignee: Amos Feng Priority: Critical Attachments: test.war h2. Goal To have a transaction manager taking care of XA capable data source with pooled connection to the database. h2. Means There are two pools in the Tomcat distribution, [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] and [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]. We choose [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool], because [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] does not contain XA capability. XA classes, the whole [managed package from Apache Commons DBCP2|https://github.com/apache/commons-dbcp/tree/master/src/main/java/org/apache/commons/dbcp2/managed] is removed in the Tomcat distribution. h3. Configuration With this [simple recovery test application|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat/tomcat-jta/src/test/java/org/jboss/narayana/tomcat/jta/integration/app], the following is our configuration (PostgreSQL flavored): [context.xml|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397]. Note the disabled Arjuna connection pooling on [line 37|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L37] and Tomcat JDBC Pool DataSourceFactory on [line 41|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L41]. h3. Test The test as it is written right now works just fine except for an IllegalStateException thrown while Tomcat is being shut down, see [line 494|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L494]. If you [run it with PostgreSQL Docker container as described in the doc|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] the test passes, i.e. the recovery works just fine. See the log including [database trace|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L611]. h3. Failure You can either [run the test suite|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] or you can do it manually according to what I prepared here for you. The only expected thing is a modern Linux kernel, docker installed and this rather insecure setup in your /etc/sysconfig/docker, add: {{-H tcp://127.0.0.1:2375 -H unix:///var/run/docker.sock}} to {{OPTIONS}}. The setup script looks like this: [setup.sh|https://gist.github.com/Karm/f220076e435124f60256f29ceca9826f] Download the attached built [^test.war] to the same dir as the script. When you run the script yo should have PostgreSQL in container running and also Tomcat 9.0.4 configured and running. The first "test" is JNDI lookup and it is fine: {noformat} karm at local:~$ curl localhost:8080/test/executor/jndi -i HTTP/1.1 204 Date: Wed, 28 Mar 2018 12:35:55 GMT {noformat} Then the recovery test, when executed *once and for the first time* also passes: {noformat} karm at local:~$ curl localhost:8080/test/executor/recovery -i HTTP/1.1 204 Date: Wed, 28 Mar 2018 12:36:13 GMT {noformat} You can observe trace log on Tomcat's log and also take a look into the database trace. For the purpose of convenience in the test suite, the container as it is started right now does not log to std out, it logs into a file inside itself, see: {noformat} karm at local:~/workspaceRH/narayana-play$ docker -H=tcp://127.0.0.1:2375 exec -it narayana_db bash root at fb6e220cded5:/# tail -f /tmp/db.log 2018-03-28 12:27:23.730 UTC transaction_id:0LOG: database system was shut down at 2018-03-28 12:27:23 UTC 2018-03-28 12:27:23.742 UTC transaction_id:0LOG: database system is ready to accept connections {noformat} h4. Connection is already associated with a different transaction! When you call the app second time, it fails: {noformat} karm at local:~$ curl localhost:8080/test/executor/recovery -i HTTP/1.1 500 Content-Type: text/html;charset=utf-8 Content-Language: en Content-Length: 5725 Date: Wed, 28 Mar 2018 12:36:24 GMT Connection: close 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. org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:77) org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:220) org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:175) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:418) org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209) org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) javax.servlet.http.HttpServlet.service(HttpServlet.java:741) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)

Root Cause

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.
    com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1041)
    com.arjuna.ats.internal.jdbc.ConnectionImple.createStatement(ConnectionImple.java:153)
    jdk.internal.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
    java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.base/java.lang.reflect.Method.invoke(Method.java:564)
    org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
    org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
    org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
    org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
    org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:152)
    org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
    org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:40)
    org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
    org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
    org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
    org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:81)
    com.sun.proxy.$Proxy33.createStatement(Unknown Source)
    org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.writeToTheDatabase(TestExecutor.java:159)
    org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.verifyRecovery(TestExecutor.java:106)
    java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.base/java.lang.reflect.Method.invoke(Method.java:564)
    org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
    org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295)
    org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
    org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236)
    org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402)
    org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
    org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
    org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
    org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
    org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
{noformat}


One can play with the context.xml in the test.war and tweak the configuration.

h3. Call to action
Could you take a look at it and either help us configure the context.xml inside [^test.war] or contribute a fix for the Narayana Tomcat integration so as it could properly handle [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]?
I would kindly ask you [to use my fork for the time being|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat] so as we can quickly iterate.

Thanks :)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)

From issues at jboss.org  Wed Mar 28 08:56:01 2018
From: issues at jboss.org (Michal Karm Babacek (JIRA))
Date: Wed, 28 Mar 2018 08:56:01 -0400 (EDT)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3004) "Connection is already
 associated with a different transaction" with Tomcat JDBC pool, XA
In-Reply-To: 
References: 
	
Message-ID: 


     [ https://issues.jboss.org/browse/JBTM-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Karm Babacek updated JBTM-3004:
--------------------------------------
    Attachment: test.war


> "Connection is already associated with a different transaction" with Tomcat JDBC pool, XA
> -----------------------------------------------------------------------------------------
>
>                 Key: JBTM-3004
>                 URL: https://issues.jboss.org/browse/JBTM-3004
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>    Affects Versions: 5.next
>         Environment: Tomcat 9.0.4, Tomcat JDBC Pool, PostgreSQL 10, Oracle JDK 8, Centos 7 x86_64
>            Reporter: Michal Karm Babacek
>            Assignee: Amos Feng
>            Priority: Critical
>              Labels: tomcat
>         Attachments: test.war
>
>
> h2. Goal
> To have a transaction manager taking care of XA capable data source with pooled connection to the database.
> h2. Means
> There are two pools in the Tomcat distribution, [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] and [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]. We choose [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool], because  [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] does not contain XA capability. XA classes, the whole [managed package from Apache Commons DBCP2|https://github.com/apache/commons-dbcp/tree/master/src/main/java/org/apache/commons/dbcp2/managed] is removed in the Tomcat distribution.
> h3. Configuration
> With this [simple recovery test application|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat/tomcat-jta/src/test/java/org/jboss/narayana/tomcat/jta/integration/app], the following is our configuration (PostgreSQL flavored): [context.xml|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397]. Note the disabled Arjuna connection pooling on [line 37|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L37] and Tomcat JDBC Pool DataSourceFactory on [line 41|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L41].
> h3. Test
> The test as it is written right now works just fine except for an IllegalStateException thrown while Tomcat is being shut down, see [line 494|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L494]. If you [run it with PostgreSQL Docker container as described in the doc|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] the test passes, i.e. the recovery works just fine. See the log including [database trace|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L611].
> h3. Failure
> You can either [run the test suite|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] or you can do it manually according to what I prepared here for you. The only expected thing is a modern Linux kernel, docker installed and this rather
> insecure setup in your /etc/sysconfig/docker, add: {{-H tcp://127.0.0.1:2375 -H unix:///var/run/docker.sock}} to {{OPTIONS}}.
> The setup script looks like this: [setup.sh|https://gist.github.com/Karm/f220076e435124f60256f29ceca9826f]
> Download the attached built [^test.war] to the same dir as the script.
> When you run the script yo should have PostgreSQL in container running and also Tomcat 9.0.4 configured and running.
> The first "test" is JNDI lookup and it is fine:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/jndi -i
> HTTP/1.1 204 
> Date: Wed, 28 Mar 2018 12:35:55 GMT
> {noformat}
> Then the recovery test, when executed *once and for the first time* also passes:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/recovery -i
> HTTP/1.1 204 
> Date: Wed, 28 Mar 2018 12:36:13 GMT
> {noformat}
> You can observe trace log on Tomcat's log and also take a look into the database trace. For the purpose of convenience in the test suite, the container as it is started right now does not log to std out, it logs into a file inside itself, see:
> {noformat}
> karm at local:~/workspaceRH/narayana-play$ docker -H=tcp://127.0.0.1:2375 exec -it narayana_db bash
> root at fb6e220cded5:/# tail -f /tmp/db.log
> 2018-03-28 12:27:23.730 UTC transaction_id:0LOG:  database system was shut down at 2018-03-28 12:27:23 UTC
> 2018-03-28 12:27:23.742 UTC transaction_id:0LOG:  database system is ready to accept connections
> {noformat}
> h4. Connection is already associated with a different transaction!
> When you call the app second time, it fails:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/recovery -i
> HTTP/1.1 500 
> Content-Type: text/html;charset=utf-8
> Content-Language: en
> Content-Length: 5725
> Date: Wed, 28 Mar 2018 12:36:24 GMT
> Connection: close
> 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.
>     org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:77)
>     org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:220)
>     org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:175)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:418)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
>     org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
>     org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
>

Root Cause

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.
>     com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1041)
>     com.arjuna.ats.internal.jdbc.ConnectionImple.createStatement(ConnectionImple.java:153)
>     jdk.internal.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
>     java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     java.base/java.lang.reflect.Method.invoke(Method.java:564)
>     org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:152)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:40)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:81)
>     com.sun.proxy.$Proxy33.createStatement(Unknown Source)
>     org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.writeToTheDatabase(TestExecutor.java:159)
>     org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.verifyRecovery(TestExecutor.java:106)
>     java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     java.base/java.lang.reflect.Method.invoke(Method.java:564)
>     org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
>     org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
>     org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> {noformat}
> One can play with the context.xml in the test.war and tweak the configuration.
> h3. Call to action
> Could you take a look at it and either help us configure the context.xml inside [^test.war] or contribute a fix for the Narayana Tomcat integration so as it could properly handle [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]?
> I would kindly ask you [to use my fork for the time being|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat] so as we can quickly iterate.
> Thanks :)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)

From issues at jboss.org  Wed Mar 28 08:58:00 2018
From: issues at jboss.org (Ondra Chaloupka (JIRA))
Date: Wed, 28 Mar 2018 08:58:00 -0400 (EDT)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3001) MBean representing a
 transaction should consider state when is to be removed
In-Reply-To: 
References: 
	
Message-ID: 


     [ https://issues.jboss.org/browse/JBTM-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka closed JBTM-3001.
---------------------------------
    Resolution: Rejected


It was found current behaviour is correct and expected one. In summary I would quote our internal discussion

{quote}
It is the admins responsibility to be satisfied that the delete operation is safe in the sense that if there are prepared branches then it his responsibility to either wait for recovery to process them or abort them using the vendors tooling.
{quote}

> MBean representing a transaction should consider state when is to be removed
> ----------------------------------------------------------------------------
>
>                 Key: JBTM-3001
>                 URL: https://issues.jboss.org/browse/JBTM-3001
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 5.8.0.Final
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>         Attachments: data-subordinate.zip, data-tooling.zip, standalone-full.xml
>
>
> When transaction mbean is to be removed by tooling - there is a transaction available in the object store and recovery does not catch it for deletion (the reason could be various - either the transaction is set with heuristic outcome, or transaction was subordinate and recovery waits for the outer player to finish transaction but there is nobody coming, or there is record in txn log store but the RA already forgot about transaction and we want to clean the transaction manager log store) - then currently the transaction manager just tries to call [XAResource.forget|https://docs.oracle.com/javaee/7/api/javax/transaction/xa/XAResource.html#forget-javax.transaction.xa.Xid-]. But the forget call is available (correct by the XA specification) only when the participant finished with in the heuristic state.
> But deleting transaction by the tooling (even that should be only the tool of the last resort as normally recovery manager handles this automatically) should cause the transaction and all participants are correctly finished (forget or rolled-back) even the transaction is in prepared state (not in heuristic one).
> When {{forget}} is called on prepared transaction branch then (e.g. for Artemis ActiveMQ) the {{XAException.XAER_NOTA}} is thrown[1].
> * The mbean should consider the state of the participant and choose if to rollback ({{prepared}} state) or if to forget ({{heuristic}} state).
> * The mbean should consider to check {{XAException}} error code as when {{XAResource.forget}} returns {{XAER_NOTA}} (pubs.opengroup.org/onlinepubs/009680699/toc.pdf, {{The specified XID is not known by the resource manager as a heuristically completed XID.}}) then the branch is in incorrect state - probably it's prepared thus rollback could be run.
> {code}
> 2018-03-20 11:06:06,614 TRACE [com.arjuna.ats.jta] (management-handler-thread - 1) XAResourceRecord.forget for XAResourceRecord < resource:org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper at 25091a7a, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a2805b6:-19805d73:5ab0d062:1c, node_name=1, branch_uid=0:ffff0a2805b6:-19805d73:5ab0d062:23, subordinatenodename=null, eis_name=forgot eis name for: 1 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: ActiveMQ Artemis/2.0, jndiName: java:/JmsXA NodeId:c07b7f00-2c1e-11e8-9014-54e1ad661a0b com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 69af92f1 >
> 2018-03-20 11:06:06,636 WARN  [com.arjuna.ats.jta] (management-handler-thread - 1) ARJUNA016006: XAResourceRecord forget failed: - forget threw exception: javax.transaction.xa.XAException
>   at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.xaForget(ActiveMQSessionContext.java:490)
>   at org.apache.activemq.artemis.core.client.impl.ClientSessionImpl.forget(ClientSessionImpl.java:1196)
>   at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.forget(ActiveMQXAResourceWrapper.java:123)
>   at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.forget(ActiveMQXAResourceWrapperImpl.java:86)
>   at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forget(XAResourceRecord.java:806)
>   at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.forgetHeuristic(XAResourceRecord.java:792)
>   at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.removeFromList(LogRecordWrapper.java:238)
>   at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean$GenericAtomicActionWrapper.remove(ActionBean.java:463)
>   at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:327)
>   at com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper.remove(LogRecordWrapper.java:218)
>   at com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean.remove(ActionBean.java:149)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
>   at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
>   at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
>   at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
>   at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
>   at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
>   at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
>   at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
>   at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
>   at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1475)
>   at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:724)
>   at org.jboss.as.txn.subsystem.LogStoreTransactionDeleteHandler.execute(LogStoreTransactionDeleteHandler.java:59)
>   at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982)
>   at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726)
>   at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450)
>   at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408)
>   at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423)
>   at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
>   at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263)
>   at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229)
>   at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
>   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
>   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
>   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
>   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
>   at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287)
>   at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244)
>   at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
>   at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
>   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
>   at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
>   at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
>   at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
>   at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
>   at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
>   at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
>   at java.lang.Thread.run(Thread.java:748)
>   at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)

From issues at jboss.org  Wed Mar 28 08:58:01 2018
From: issues at jboss.org (Michal Karm Babacek (JIRA))
Date: Wed, 28 Mar 2018 08:58:01 -0400 (EDT)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3004) "Connection is already
 associated with a different transaction" with Tomcat JDBC pool, XA
In-Reply-To: 
References: 
	
Message-ID: 


    [ https://issues.jboss.org/browse/JBTM-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552842#comment-13552842 ] 

Michal Karm Babacek commented on JBTM-3004:
-------------------------------------------

[~rmaucher], could you also take a look as JWS Developer and help [~zhfeng], please?

> "Connection is already associated with a different transaction" with Tomcat JDBC pool, XA
> -----------------------------------------------------------------------------------------
>
>                 Key: JBTM-3004
>                 URL: https://issues.jboss.org/browse/JBTM-3004
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>    Affects Versions: 5.next
>         Environment: Tomcat 9.0.4, Tomcat JDBC Pool, PostgreSQL 10, Oracle JDK 8, Centos 7 x86_64
>            Reporter: Michal Karm Babacek
>            Assignee: Amos Feng
>            Priority: Critical
>              Labels: tomcat
>         Attachments: test.war
>
>
> h2. Goal
> To have a transaction manager taking care of XA capable data source with pooled connection to the database.
> h2. Means
> There are two pools in the Tomcat distribution, [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] and [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]. We choose [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool], because  [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] does not contain XA capability. XA classes, the whole [managed package from Apache Commons DBCP2|https://github.com/apache/commons-dbcp/tree/master/src/main/java/org/apache/commons/dbcp2/managed] is removed in the Tomcat distribution.
> h3. Configuration
> With this [simple recovery test application|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat/tomcat-jta/src/test/java/org/jboss/narayana/tomcat/jta/integration/app], the following is our configuration (PostgreSQL flavored): [context.xml|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397]. Note the disabled Arjuna connection pooling on [line 37|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L37] and Tomcat JDBC Pool DataSourceFactory on [line 41|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L41].
> h3. Test
> The test as it is written right now works just fine except for an IllegalStateException thrown while Tomcat is being shut down, see [line 494|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L494]. If you [run it with PostgreSQL Docker container as described in the doc|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] the test passes, i.e. the recovery works just fine. See the log including [database trace|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L611].
> h3. Failure
> You can either [run the test suite|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] or you can do it manually according to what I prepared here for you. The only expected thing is a modern Linux kernel, docker installed and this rather
> insecure setup in your /etc/sysconfig/docker, add: {{-H tcp://127.0.0.1:2375 -H unix:///var/run/docker.sock}} to {{OPTIONS}}.
> The setup script looks like this: [setup.sh|https://gist.github.com/Karm/f220076e435124f60256f29ceca9826f]
> Download the attached built [^test.war] to the same dir as the script.
> When you run the script yo should have PostgreSQL in container running and also Tomcat 9.0.4 configured and running.
> The first "test" is JNDI lookup and it is fine:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/jndi -i
> HTTP/1.1 204 
> Date: Wed, 28 Mar 2018 12:35:55 GMT
> {noformat}
> Then the recovery test, when executed *once and for the first time* also passes:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/recovery -i
> HTTP/1.1 204 
> Date: Wed, 28 Mar 2018 12:36:13 GMT
> {noformat}
> You can observe trace log on Tomcat's log and also take a look into the database trace. For the purpose of convenience in the test suite, the container as it is started right now does not log to std out, it logs into a file inside itself, see:
> {noformat}
> karm at local:~/workspaceRH/narayana-play$ docker -H=tcp://127.0.0.1:2375 exec -it narayana_db bash
> root at fb6e220cded5:/# tail -f /tmp/db.log
> 2018-03-28 12:27:23.730 UTC transaction_id:0LOG:  database system was shut down at 2018-03-28 12:27:23 UTC
> 2018-03-28 12:27:23.742 UTC transaction_id:0LOG:  database system is ready to accept connections
> {noformat}
> h4. Connection is already associated with a different transaction!
> When you call the app second time, it fails:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/recovery -i
> HTTP/1.1 500 
> Content-Type: text/html;charset=utf-8
> Content-Language: en
> Content-Length: 5725
> Date: Wed, 28 Mar 2018 12:36:24 GMT
> Connection: close
> 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.
>     org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:77)
>     org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:220)
>     org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:175)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:418)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
>     org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
>     org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
>

Root Cause

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.
>     com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1041)
>     com.arjuna.ats.internal.jdbc.ConnectionImple.createStatement(ConnectionImple.java:153)
>     jdk.internal.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
>     java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     java.base/java.lang.reflect.Method.invoke(Method.java:564)
>     org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:152)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:40)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:81)
>     com.sun.proxy.$Proxy33.createStatement(Unknown Source)
>     org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.writeToTheDatabase(TestExecutor.java:159)
>     org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.verifyRecovery(TestExecutor.java:106)
>     java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     java.base/java.lang.reflect.Method.invoke(Method.java:564)
>     org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
>     org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
>     org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> {noformat}
> One can play with the context.xml in the test.war and tweak the configuration.
> h3. Call to action
> Could you take a look at it and either help us configure the context.xml inside [^test.war] or contribute a fix for the Narayana Tomcat integration so as it could properly handle [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]?
> I would kindly ask you [to use my fork for the time being|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat] so as we can quickly iterate.
> Thanks :)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)

From issues at jboss.org  Wed Mar 28 10:22:01 2018
From: issues at jboss.org (Tom Jenkinson (JIRA))
Date: Wed, 28 Mar 2018 10:22:01 -0400 (EDT)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3004) "Connection is already
 associated with a different transaction" with Tomcat JDBC pool, XA
In-Reply-To: 
References: 
	
Message-ID: 


    [ https://issues.jboss.org/browse/JBTM-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552919#comment-13552919 ] 

Tom Jenkinson commented on JBTM-3004:
-------------------------------------

This is using the TransactionalDriver you can tell this because of the ConnectionImple.

> "Connection is already associated with a different transaction" with Tomcat JDBC pool, XA
> -----------------------------------------------------------------------------------------
>
>                 Key: JBTM-3004
>                 URL: https://issues.jboss.org/browse/JBTM-3004
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>    Affects Versions: 5.next
>         Environment: Tomcat 9.0.4, Tomcat JDBC Pool, PostgreSQL 10, Oracle JDK 8, Centos 7 x86_64
>            Reporter: Michal Karm Babacek
>            Assignee: Amos Feng
>            Priority: Critical
>              Labels: tomcat
>         Attachments: test.war
>
>
> h2. Goal
> To have a transaction manager taking care of XA capable data source with pooled connection to the database.
> h2. Means
> There are two pools in the Tomcat distribution, [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] and [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]. We choose [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool], because  [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] does not contain XA capability. XA classes, the whole [managed package from Apache Commons DBCP2|https://github.com/apache/commons-dbcp/tree/master/src/main/java/org/apache/commons/dbcp2/managed] is removed in the Tomcat distribution.
> h3. Configuration
> With this [simple recovery test application|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat/tomcat-jta/src/test/java/org/jboss/narayana/tomcat/jta/integration/app], the following is our configuration (PostgreSQL flavored): [context.xml|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397]. Note the disabled Arjuna connection pooling on [line 37|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L37] and Tomcat JDBC Pool DataSourceFactory on [line 41|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L41].
> h3. Test
> The test as it is written right now works just fine except for an IllegalStateException thrown while Tomcat is being shut down, see [line 494|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L494]. If you [run it with PostgreSQL Docker container as described in the doc|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] the test passes, i.e. the recovery works just fine. See the log including [database trace|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L611].
> h3. Failure
> You can either [run the test suite|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] or you can do it manually according to what I prepared here for you. The only expected thing is a modern Linux kernel, docker installed and this rather
> insecure setup in your /etc/sysconfig/docker, add: {{-H tcp://127.0.0.1:2375 -H unix:///var/run/docker.sock}} to {{OPTIONS}}.
> The setup script looks like this: [setup.sh|https://gist.github.com/Karm/f220076e435124f60256f29ceca9826f]
> Download the attached built [^test.war] to the same dir as the script.
> When you run the script yo should have PostgreSQL in container running and also Tomcat 9.0.4 configured and running.
> The first "test" is JNDI lookup and it is fine:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/jndi -i
> HTTP/1.1 204 
> Date: Wed, 28 Mar 2018 12:35:55 GMT
> {noformat}
> Then the recovery test, when executed *once and for the first time* also passes:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/recovery -i
> HTTP/1.1 204 
> Date: Wed, 28 Mar 2018 12:36:13 GMT
> {noformat}
> You can observe trace log on Tomcat's log and also take a look into the database trace. For the purpose of convenience in the test suite, the container as it is started right now does not log to std out, it logs into a file inside itself, see:
> {noformat}
> karm at local:~/workspaceRH/narayana-play$ docker -H=tcp://127.0.0.1:2375 exec -it narayana_db bash
> root at fb6e220cded5:/# tail -f /tmp/db.log
> 2018-03-28 12:27:23.730 UTC transaction_id:0LOG:  database system was shut down at 2018-03-28 12:27:23 UTC
> 2018-03-28 12:27:23.742 UTC transaction_id:0LOG:  database system is ready to accept connections
> {noformat}
> h4. Connection is already associated with a different transaction!
> When you call the app second time, it fails:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/recovery -i
> HTTP/1.1 500 
> Content-Type: text/html;charset=utf-8
> Content-Language: en
> Content-Length: 5725
> Date: Wed, 28 Mar 2018 12:36:24 GMT
> Connection: close
> 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.
>     org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:77)
>     org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:220)
>     org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:175)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:418)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
>     org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
>     org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
>

Root Cause

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.
>     com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1041)
>     com.arjuna.ats.internal.jdbc.ConnectionImple.createStatement(ConnectionImple.java:153)
>     jdk.internal.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
>     java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     java.base/java.lang.reflect.Method.invoke(Method.java:564)
>     org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:152)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:40)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:81)
>     com.sun.proxy.$Proxy33.createStatement(Unknown Source)
>     org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.writeToTheDatabase(TestExecutor.java:159)
>     org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.verifyRecovery(TestExecutor.java:106)
>     java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     java.base/java.lang.reflect.Method.invoke(Method.java:564)
>     org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
>     org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
>     org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> {noformat}
> One can play with the context.xml in the test.war and tweak the configuration.
> h3. Call to action
> Could you take a look at it and either help us configure the context.xml inside [^test.war] or contribute a fix for the Narayana Tomcat integration so as it could properly handle [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]?
> I would kindly ask you [to use my fork for the time being|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat] so as we can quickly iterate.
> Thanks :)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)

From issues at jboss.org  Wed Mar 28 22:14:00 2018
From: issues at jboss.org (Amos Feng (JIRA))
Date: Wed, 28 Mar 2018 22:14:00 -0400 (EDT)
Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3004) "Connection is already
 associated with a different transaction" with Tomcat JDBC pool, XA
In-Reply-To: 
References: 
	
Message-ID: 


    [ https://issues.jboss.org/browse/JBTM-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553322#comment-13553322 ] 

Amos Feng commented on JBTM-3004:
---------------------------------

[~mbabacek] I think the TransactionalDriver can not work with the Tomcat JDBC currently as the Tomcat JDBC will not reset the transaction to null when returning to the pool. That could be the reason for the ARJUNA017003. So if you want to support both XA and pooling, you should choose the DBCP2. And I think only the DBCP2 can support the XA with [ManagedConnection|https://github.com/apache/commons-dbcp/blob/master/src/main/java/org/apache/commons/dbcp2/managed/ManagedConnection.java].

> "Connection is already associated with a different transaction" with Tomcat JDBC pool, XA
> -----------------------------------------------------------------------------------------
>
>                 Key: JBTM-3004
>                 URL: https://issues.jboss.org/browse/JBTM-3004
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>    Affects Versions: 5.next
>         Environment: Tomcat 9.0.4, Tomcat JDBC Pool, PostgreSQL 10, Oracle JDK 8, Centos 7 x86_64
>            Reporter: Michal Karm Babacek
>            Assignee: Amos Feng
>            Priority: Critical
>              Labels: tomcat
>         Attachments: test.war
>
>
> h2. Goal
> To have a transaction manager taking care of XA capable data source with pooled connection to the database.
> h2. Means
> There are two pools in the Tomcat distribution, [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] and [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]. We choose [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool], because  [Tomcat DBCP2|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/java/org/apache/tomcat/dbcp/dbcp2] does not contain XA capability. XA classes, the whole [managed package from Apache Commons DBCP2|https://github.com/apache/commons-dbcp/tree/master/src/main/java/org/apache/commons/dbcp2/managed] is removed in the Tomcat distribution.
> h3. Configuration
> With this [simple recovery test application|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat/tomcat-jta/src/test/java/org/jboss/narayana/tomcat/jta/integration/app], the following is our configuration (PostgreSQL flavored): [context.xml|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397]. Note the disabled Arjuna connection pooling on [line 37|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L37] and Tomcat JDBC Pool DataSourceFactory on [line 41|https://gist.github.com/Karm/0b3b06f1cd4dd359eaa0868c28c83397#file-context-xml-L41].
> h3. Test
> The test as it is written right now works just fine except for an IllegalStateException thrown while Tomcat is being shut down, see [line 494|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L494]. If you [run it with PostgreSQL Docker container as described in the doc|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] the test passes, i.e. the recovery works just fine. See the log including [database trace|https://gist.github.com/Karm/6854a09b113474f5c464282bba1c706c#file-gistfile1-txt-L611].
> h3. Failure
> You can either [run the test suite|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat#3-container---postgres-1] or you can do it manually according to what I prepared here for you. The only expected thing is a modern Linux kernel, docker installed and this rather
> insecure setup in your /etc/sysconfig/docker, add: {{-H tcp://127.0.0.1:2375 -H unix:///var/run/docker.sock}} to {{OPTIONS}}.
> The setup script looks like this: [setup.sh|https://gist.github.com/Karm/f220076e435124f60256f29ceca9826f]
> Download the attached built [^test.war] to the same dir as the script.
> When you run the script yo should have PostgreSQL in container running and also Tomcat 9.0.4 configured and running.
> The first "test" is JNDI lookup and it is fine:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/jndi -i
> HTTP/1.1 204 
> Date: Wed, 28 Mar 2018 12:35:55 GMT
> {noformat}
> Then the recovery test, when executed *once and for the first time* also passes:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/recovery -i
> HTTP/1.1 204 
> Date: Wed, 28 Mar 2018 12:36:13 GMT
> {noformat}
> You can observe trace log on Tomcat's log and also take a look into the database trace. For the purpose of convenience in the test suite, the container as it is started right now does not log to std out, it logs into a file inside itself, see:
> {noformat}
> karm at local:~/workspaceRH/narayana-play$ docker -H=tcp://127.0.0.1:2375 exec -it narayana_db bash
> root at fb6e220cded5:/# tail -f /tmp/db.log
> 2018-03-28 12:27:23.730 UTC transaction_id:0LOG:  database system was shut down at 2018-03-28 12:27:23 UTC
> 2018-03-28 12:27:23.742 UTC transaction_id:0LOG:  database system is ready to accept connections
> {noformat}
> h4. Connection is already associated with a different transaction!
> When you call the app second time, it fails:
> {noformat}
> karm at local:~$ curl localhost:8080/test/executor/recovery -i
> HTTP/1.1 500 
> Content-Type: text/html;charset=utf-8
> Content-Language: en
> Content-Length: 5725
> Date: Wed, 28 Mar 2018 12:36:24 GMT
> Connection: close
> 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.
>     org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:77)
>     org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:220)
>     org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:175)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:418)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
>     org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
>     org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
>

Root Cause

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.
>     com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1041)
>     com.arjuna.ats.internal.jdbc.ConnectionImple.createStatement(ConnectionImple.java:153)
>     jdk.internal.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
>     java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     java.base/java.lang.reflect.Method.invoke(Method.java:564)
>     org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.ConnectionState.invoke(ConnectionState.java:152)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:40)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:75)
>     org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:108)
>     org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:81)
>     com.sun.proxy.$Proxy33.createStatement(Unknown Source)
>     org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.writeToTheDatabase(TestExecutor.java:159)
>     org.jboss.narayana.tomcat.jta.integration.app.TestExecutor.verifyRecovery(TestExecutor.java:106)
>     java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     java.base/java.lang.reflect.Method.invoke(Method.java:564)
>     org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249)
>     org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402)
>     org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209)
>     org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
>     org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
>     javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
>     org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> {noformat}
> One can play with the context.xml in the test.war and tweak the configuration.
> h3. Call to action
> Could you take a look at it and either help us configure the context.xml inside [^test.war] or contribute a fix for the Narayana Tomcat integration so as it could properly handle [Tomcat JDBC|https://github.com/apache/tomcat/tree/TOMCAT_9_0_4/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool]?
> I would kindly ask you [to use my fork for the time being|https://github.com/Karm/narayana/tree/narayana-tomcat-ts/tomcat] so as we can quickly iterate.
> Thanks :)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)