January 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2989) Replace to use the DBCP2 in the spring quickstarts

by Amos Feng (JIRA)

Amos Feng created JBTM-2989: ------------------------------- Summary: Replace to use the DBCP2 in the spring quickstarts Key: JBTM-2989 URL: https://issues.jboss.org/browse/JBTM-2989 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Demonstrator Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next It could be helpful to replace the transational driver when using with the spring. The transactional driver might be only used in the standalone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2987) Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2987?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Prim created pull request #1274 in GitHub ----------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager > -------------------------------------------------------------------------------------- > > Key: JBTM-2987 > URL: https://issues.jboss.org/browse/JBTM-2987 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Affects Versions: 5.7.2.Final > Reporter: Alon Greenland > > As discussed in https://developer.jboss.org/thread/266729, when Recovery Manager executes xaResource.rollback(xid), if it receives error code XAER_NOTA it is not really an error or warning. > Currently it is logged as warning. It can be logged with debug level instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2988) Update activemq-artemis in the performance repo

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2988: -------------------------------------- Summary: Update activemq-artemis in the performance repo Key: JBTM-2988 URL: https://issues.jboss.org/browse/JBTM-2988 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Affects Versions: 5.7.2.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Make sure that the artemis dependency in the performance repo matches what we use on master. So we are currently on 1.5.5.jbossorg-008 so change <version.org.apache.activemq> in the pom in our performance repo to use this version. Important: make sure that we also *replace* the native AIO library which is located in ArjunaJTA/jta/etc -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2983) Commit failure in WFLY LocalResource does not return error to the caller

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2983?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2983: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Commit failure in WFLY LocalResource does not return error to the caller > ------------------------------------------------------------------------ > > Key: JBTM-2983 > URL: https://issues.jboss.org/browse/JBTM-2983 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.7.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > > In case that an exception is thrown during one-phase commit of non-XA transaction participant the error is swallowed and not returned to the caller. When tested with WFLY the excpetion is shown in the log, the commit fails but the client thinks that everything worked well. > The relevant part of the exception stacktrace when error on commit occurs is > {code} > at com.mysql.jdbc.ConnectionImpl.commit(ConnectionImpl.java:1549) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnection.commit(LocalManagedConnection.java:96) > at org.jboss.jca.core.tx.jbossts.LocalXAResourceImpl.commit(LocalXAResourceImpl.java:172) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAOnePhaseResource.commit(XAOnePhaseResource.java:120) > at com.arjuna.ats.internal.arjuna.abstractrecords.LastResourceRecord.topLevelPrepare(LastResourceRecord.java:152) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.topLevelOnePhaseCommit(AbstractRecord.java:428) > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2386) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1497) > {code} > It seems that there is issue at > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com... > which does say something about recovery but for one phase nonXA there will be no recovery. > The decision that the {{XAOnePhaseResource}} is used for the txn work is done at > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com... > where depending how the setup of {{jtaEnvironmentBean.setLastResourceOptimisationInterfaceClassName}} was done. This is done in WFLY at > https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2928) Provide WS-AT Integration with .NET

by Ricardo Martin Camarero (JIRA)

[ https://issues.jboss.org/browse/JBTM-2928?page=com.atlassian.jira.plugin.... ] Ricardo Martin Camarero commented on JBTM-2928: ----------------------------------------------- When the WS-TX is initiated in the windows side, a windows client creates a context with the windows coordinator service and later it calls to a wildfly WS, the process fails at Registration operation. The JBOSS/Wildfly side tries to execute the Registration operation as a client and windows just responds 202 (no content, no XML is returned) which throws a NPE. The XML sent in the request is the following: {code:xml} <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register</Action> <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:a632e947aaf3aca5:d586ffa:15edccdf0ca:-8000</MessageID> <To xmlns="http://www.w3.org/2005/08/addressing">https://windows.sample.com/WsatService/Registration/Coordinator11/</To> <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://www.w3.org/2005/08/addressing/anonymous</Address> </ReplyTo> <mstx:RegisterInfo xmlns="http://www.w3.org/2005/08/addressing" xmlns:mstx="http://schemas.microsoft.com/ws/2006/02/transactions" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1"> <mstx:LocalTransactionId>edd12908-c2f4-427a-86d6-4fab6dde3d32</mstx:LocalTransactionId> </mstx:RegisterInfo> </soap:Header> <soap:Body> <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> <ProtocolIdentifier>http://docs.oasis-open.org/ws-tx/wsat/2006/06/Durable2PC</ProtocolIdentifier> <ParticipantProtocolService> <ns2:Address>https://jboss.sample.com:8443/ws-t11-participant/ParticipantService</ns2:Address> <ns2:ReferenceParameters> <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">restaurantServiceAT:f40f5b70-51c3-46f3-99c6-6052df7efa3f</wsarj:InstanceIdentifier> </ns2:ReferenceParameters> <ns2:Metadata> <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsat="http://docs.oasis-open.org/ws-tx/wsat/2006/06" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" EndpointName="ParticipantPortType">wsat:ParticipantService</wsam:ServiceName> </ns2:Metadata> </ParticipantProtocolService> </Register> </soap:Body> </soap:Envelope> {code} After some tests it seems that windows implementation does not understand the _"http://www.w3.org/2005/08/addressing/anonymous"_ as *ReplyTo*. The request should send a *ReplyTo* with a valid URL and the Microsoft implementation calls back to that URL with the RegisterResponse type. We think that "anonymous" behavior is covered by the standard (it means synchronous execution) and that the windows implementation is an extreme interpretation of the specification (with that idea any partner, even an standalone application that calls to two web services with WS-TX support, needs to have endpoints and be a web server too). References of the ws-addressing spec about anonymous in [current|https://www.w3.org/TR/2006/REC-ws-addr-core-20060509/#eprinfomodel] and [previous spec|https://www.w3.org/Submission/ws-addressing/#_Toc77464322]. > Provide WS-AT Integration with .NET > ----------------------------------- > > Key: JBTM-2928 > URL: https://issues.jboss.org/browse/JBTM-2928 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Jörg Bäsner > > Provide WS-AT integration for .NET -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2987) Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager

by Alon Greenland (JIRA)

[ https://issues.jboss.org/browse/JBTM-2987?page=com.atlassian.jira.plugin.... ] Alon Greenland updated JBTM-2987: --------------------------------- Summary: Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager (was: Treat XAER_NOTA return code as fsdfds, during rollback issued by Recovery Manager) > Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager > -------------------------------------------------------------------------------------- > > Key: JBTM-2987 > URL: https://issues.jboss.org/browse/JBTM-2987 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Affects Versions: 5.7.2.Final > Reporter: Alon Greenland > > As discussed in https://developer.jboss.org/thread/266729, when Recovery Manager executes xaResource.rollback(xid), if it receives error code XAER_NOTA it is not really an error or warning. > Currently it is logged as warning. It can be logged with debug level instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2987) Treat XAER_NOTA return code as fsdfds, during rollback issued by Recovery Manager

by Alon Greenland (JIRA)

Alon Greenland created JBTM-2987: ------------------------------------ Summary: Treat XAER_NOTA return code as fsdfds, during rollback issued by Recovery Manager Key: JBTM-2987 URL: https://issues.jboss.org/browse/JBTM-2987 Project: JBoss Transaction Manager Issue Type: Task Components: JTA Affects Versions: 5.7.2.Final Reporter: Alon Greenland As discussed in https://developer.jboss.org/thread/266729, when Recovery Manager executes xaResource.rollback(xid), if it receives error code XAER_NOTA it is not really an error or warning. Currently it is logged as warning. It can be logged with debug level instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2986) Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2986?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2986: --------------------------------------- [~mbabacek] the workaround if skipping IT tests (-Dmaven.test.skip=true) does not work as the post-integration phase is still executed even the tests theirselves are skipped. Maybe we could add a profile (https://stackoverflow.com/a/31431557/187035) for the post integration step would not be executed. > Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2986 > URL: https://issues.jboss.org/browse/JBTM-2986 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.2.Final > Environment: IBM JDK 8 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > Fix For: 5.7.2.Final > > Attachments: maven.log.zip > > > I would like to build and test Narayana on IBM JDK and it seems the LRA test module is looking for {{jps}} that doesn't exist on IBM JDK. There should be some profile/wrapper to skip or port this part so as it works on IBM JDK without an explicit path to bin/jps. > See [^maven.log.zip]. > h3. Excerpt > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (stop) > on project lra-test: An Ant BuildException has occured: Execute failed: > java.io.IOException: Cannot run program "/qa/tools/opt/x86_64/ibm-java-80/bin/jps" > (in directory "/opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test"): > error=2, No such file or directory > [ERROR] around Ant part ...<exec executable="/qa/tools/opt/x86_64/ibm-java-80/bin/jps">... > @ 4:63 in /opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test/target/antrun/build-main.xml > {noformat} > I tried to "workaround" it temporarily with {{-DskipTests -Dmaven.test.skip=true}}; no luck. > WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2986) Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2986?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2986: --------------------------------------- the reason is that the lra integration tests uses {{post-integration-test}} in the [pom.xml|https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-test/...] {{jps}} command to check running swarm container and by jps it finds out the id of process which is killed in the next {{exec}} step. I need to review way of not using {{jps}} for getting process id for this would work on IBM JDK where {{jps}} command is not provided. > Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2986 > URL: https://issues.jboss.org/browse/JBTM-2986 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.2.Final > Environment: IBM JDK 8 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > Fix For: 5.7.2.Final > > Attachments: maven.log.zip > > > I would like to build and test Narayana on IBM JDK and it seems the LRA test module is looking for {{jps}} that doesn't exist on IBM JDK. There should be some profile/wrapper to skip or port this part so as it works on IBM JDK without an explicit path to bin/jps. > See [^maven.log.zip]. > h3. Excerpt > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (stop) > on project lra-test: An Ant BuildException has occured: Execute failed: > java.io.IOException: Cannot run program "/qa/tools/opt/x86_64/ibm-java-80/bin/jps" > (in directory "/opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test"): > error=2, No such file or directory > [ERROR] around Ant part ...<exec executable="/qa/tools/opt/x86_64/ibm-java-80/bin/jps">... > @ 4:63 in /opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test/target/antrun/build-main.xml > {noformat} > I tried to "workaround" it temporarily with {{-DskipTests -Dmaven.test.skip=true}}; no luck. > WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2986) Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/JBTM-2986?page=com.atlassian.jira.plugin.... ] Michal Karm Babacek updated JBTM-2986: -------------------------------------- Tester: Ondrej Kotek > Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2986 > URL: https://issues.jboss.org/browse/JBTM-2986 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.2.Final > Environment: IBM JDK 8 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > Fix For: 5.7.2.Final > > Attachments: maven.log.zip > > > I would like to build and test Narayana on IBM JDK and it seems the LRA test module is looking for {{jps}} that doesn't exist on IBM JDK. There should be some profile/wrapper to skip or port this part so as it works on IBM JDK without an explicit path to bin/jps. > See [^maven.log.zip]. > h3. Excerpt > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (stop) > on project lra-test: An Ant BuildException has occured: Execute failed: > java.io.IOException: Cannot run program "/qa/tools/opt/x86_64/ibm-java-80/bin/jps" > (in directory "/opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test"): > error=2, No such file or directory > [ERROR] around Ant part ...<exec executable="/qa/tools/opt/x86_64/ibm-java-80/bin/jps">... > @ 4:63 in /opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test/target/antrun/build-main.xml > {noformat} > I tried to "workaround" it temporarily with {{-DskipTests -Dmaven.test.skip=true}}; no luck. > WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues January 2018