February 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2853) Transaction bridging for WS not working because of switch to new wfly transaction client

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2853?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when chalda created pull request #19 in GitHub ----------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Transaction bridging for WS not working because of switch to new wfly transaction client > ---------------------------------------------------------------------------------------- > > Key: JBTM-2853 > URL: https://issues.jboss.org/browse/JBTM-2853 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > > Transaction bridging (WS transaction <-> global container transaction) does not work currently as container is impacted by switch from transaction spi (https://github.com/jbosstm/jboss-transaction-spi) to wildfly transaction client (https://github.com/wildfly/wildfly-transaction-client). > The cause code change could be checked here > https://github.com/wildfly/wildfly/commit/5eb816e0b58da3e99bfee81715ba27b... > Narayana needs to be enhanced to use the new transaction client to import transaction and bridge the ws to container transaction that way. The similar thing will probably need to be done for opposite side. > Container integration code in jboss container needs to be changed in way to provide the transaction context to Narayana. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2852) Transaction integration failures with CDI

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2852?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when chalda created pull request #19 in GitHub ----------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Transaction integration failures with CDI > ----------------------------------------- > > Key: JBTM-2852 > URL: https://issues.jboss.org/browse/JBTM-2852 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > > There are failures in integration of transaction and cdi because of introducing of new wildfly transaction client. > The new client does not verify transaction availability where JTA-CDI requires IllegalStateException. > Related test case could be > https://github.com/scottmarlow/wildfly/commit/34385c25a2b0126eafe791914ef... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2854) XATerminatorImple.importTransaction can produce ArrayIndexOutOfBoundsException

by David Lloyd (JIRA)

David Lloyd created JBTM-2854: --------------------------------- Summary: XATerminatorImple.importTransaction can produce ArrayIndexOutOfBoundsException Key: JBTM-2854 URL: https://issues.jboss.org/browse/JBTM-2854 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Reporter: David Lloyd Priority: Blocker Here is what the stack trace looks like: {noformat} Caused by: Remote exception java.lang.ArrayIndexOutOfBoundsException: 32 at com.arjuna.ats.jta.xa.XATxConverter.getSubordinateNodeName(XATxConverter.java:204) at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca.SubordinateAtomicAction.<init>(SubordinateAtomicAction.java:115) at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca.TransactionImple.<init>(TransactionImple.java:57) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple.addImportedTransaction(TransactionImporterImple.java:281) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple.importRemoteTransaction(TransactionImporterImple.java:105) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.importTransaction(XATerminatorImple.java:599) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$XAImporterImpl.findOrImportTransaction(JBossLocalTransactionProvider.java:585) ... 11 more {noformat} It appears that there is no protection against an XID of inadequate length in XATxConverter#setSubordinateNodeName. At present the protocol is attempting to import an XID which contains only the gtid from the master node (based on what I discussed with [~tomjenkinson] some time ago at a previous meeting). This can be changed if it is wrong, but either way this method should fail with a friendlier exception if the XID is not valid for some reason. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2853) Transaction bridging for WS not working because of switch to new wfly transaction client

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2853?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2853: ---------------------------------- Affects Version/s: 5.5.2.Final > Transaction bridging for WS not working because of switch to new wfly transaction client > ---------------------------------------------------------------------------------------- > > Key: JBTM-2853 > URL: https://issues.jboss.org/browse/JBTM-2853 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > > Transaction bridging (WS transaction <-> global container transaction) does not work currently as container is impacted by switch from transaction spi (https://github.com/jbosstm/jboss-transaction-spi) to wildfly transaction client (https://github.com/wildfly/wildfly-transaction-client). > The cause code change could be checked here > https://github.com/wildfly/wildfly/commit/5eb816e0b58da3e99bfee81715ba27b... > Narayana needs to be enhanced to use the new transaction client to import transaction and bridge the ws to container transaction that way. The similar thing will probably need to be done for opposite side. > Container integration code in jboss container needs to be changed in way to provide the transaction context to Narayana. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2853) Transaction bridging for WS not working because of switch to new wfly transaction client

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2853?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2853: ---------------------------------- Component/s: TxBridge > Transaction bridging for WS not working because of switch to new wfly transaction client > ---------------------------------------------------------------------------------------- > > Key: JBTM-2853 > URL: https://issues.jboss.org/browse/JBTM-2853 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > > Transaction bridging (WS transaction <-> global container transaction) does not work currently as container is impacted by switch from transaction spi (https://github.com/jbosstm/jboss-transaction-spi) to wildfly transaction client (https://github.com/wildfly/wildfly-transaction-client). > The cause code change could be checked here > https://github.com/wildfly/wildfly/commit/5eb816e0b58da3e99bfee81715ba27b... > Narayana needs to be enhanced to use the new transaction client to import transaction and bridge the ws to container transaction that way. The similar thing will probably need to be done for opposite side. > Container integration code in jboss container needs to be changed in way to provide the transaction context to Narayana. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2853) Transaction bridging for WS not working because of switch to new wfly transaction client

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2853?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned JBTM-2853: ------------------------------------- Assignee: Ondra Chaloupka > Transaction bridging for WS not working because of switch to new wfly transaction client > ---------------------------------------------------------------------------------------- > > Key: JBTM-2853 > URL: https://issues.jboss.org/browse/JBTM-2853 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > > Transaction bridging (WS transaction <-> global container transaction) does not work currently as container is impacted by switch from transaction spi (https://github.com/jbosstm/jboss-transaction-spi) to wildfly transaction client (https://github.com/wildfly/wildfly-transaction-client). > The cause code change could be checked here > https://github.com/wildfly/wildfly/commit/5eb816e0b58da3e99bfee81715ba27b... > Narayana needs to be enhanced to use the new transaction client to import transaction and bridge the ws to container transaction that way. The similar thing will probably need to be done for opposite side. > Container integration code in jboss container needs to be changed in way to provide the transaction context to Narayana. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2853) Transaction bridging for WS not working because of switch to new wfly transaction client

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-2853: ------------------------------------- Summary: Transaction bridging for WS not working because of switch to new wfly transaction client Key: JBTM-2853 URL: https://issues.jboss.org/browse/JBTM-2853 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Ondra Chaloupka Priority: Blocker Transaction bridging (WS transaction <-> global container transaction) does not work currently as container is impacted by switch from transaction spi (https://github.com/jbosstm/jboss-transaction-spi) to wildfly transaction client (https://github.com/wildfly/wildfly-transaction-client). The cause code change could be checked here https://github.com/wildfly/wildfly/commit/5eb816e0b58da3e99bfee81715ba27b... Narayana needs to be enhanced to use the new transaction client to import transaction and bridge the ws to container transaction that way. The similar thing will probably need to be done for opposite side. Container integration code in jboss container needs to be changed in way to provide the transaction context to Narayana. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2852) Transaction integration failures with CDI

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2852?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka moved JBEAP-9047 to JBTM-2852: ---------------------------------------------- Project: JBoss Transaction Manager (was: JBoss Enterprise Application Platform) Key: JBTM-2852 (was: JBEAP-9047) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JTA (was: Transactions) Affects Version/s: 5.5.2.Final (was: 7.1.0.DR12) > Transaction integration failures with CDI > ----------------------------------------- > > Key: JBTM-2852 > URL: https://issues.jboss.org/browse/JBTM-2852 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > > There are failures in integration of transaction and cdi because of introducing of new wildfly transaction client. > The new client does not verify transaction availability where JTA-CDI requires IllegalStateException. > Related test case could be > https://github.com/scottmarlow/wildfly/commit/34385c25a2b0126eafe791914ef... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2851) Upgrade BlackTie to a version of WildFly that works with JDK9 (when available)

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2851?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2851: ---------------------------- Description: The blacktie-admin-service-ear will failed when deploying the ear to the wildfly running with the JDK9. It could be an issue [1] and should be fix in [2]. So we have to build the openjdk-orb 8.0.8.Beta1-SNAPSHOT or wait it for the final release. [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007698.html [2] https://github.com/jboss/openjdk-orb/pull/4 > Upgrade BlackTie to a version of WildFly that works with JDK9 (when available) > ------------------------------------------------------------------------------ > > Key: JBTM-2851 > URL: https://issues.jboss.org/browse/JBTM-2851 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > The blacktie-admin-service-ear will failed when deploying the ear to the wildfly running with the JDK9. It could be an issue [1] and should be fix in [2]. > So we have to build the openjdk-orb 8.0.8.Beta1-SNAPSHOT or wait it for the final release. > [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007698.html > [2] https://github.com/jboss/openjdk-orb/pull/4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2851) Upgrade BlackTie to a version of WildFly that works with JDK9 (when available)

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2851?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2851: ---------------------------- Description: The blacktie-admin-service-ear is failed when deploying the ear to the wildfly running with the JDK9. It could be an issue [1] and should be fix in [2]. So we have to build the openjdk-orb 8.0.8.Beta1-SNAPSHOT or wait it for the final release. [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007698.html [2] https://github.com/jboss/openjdk-orb/pull/4 was: The blacktie-admin-service-ear will failed when deploying the ear to the wildfly running with the JDK9. It could be an issue [1] and should be fix in [2]. So we have to build the openjdk-orb 8.0.8.Beta1-SNAPSHOT or wait it for the final release. [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007698.html [2] https://github.com/jboss/openjdk-orb/pull/4 > Upgrade BlackTie to a version of WildFly that works with JDK9 (when available) > ------------------------------------------------------------------------------ > > Key: JBTM-2851 > URL: https://issues.jboss.org/browse/JBTM-2851 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > The blacktie-admin-service-ear is failed when deploying the ear to the wildfly running with the JDK9. It could be an issue [1] and should be fix in [2]. > So we have to build the openjdk-orb 8.0.8.Beta1-SNAPSHOT or wait it for the final release. > [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007698.html > [2] https://github.com/jboss/openjdk-orb/pull/4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2017