June 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2428) JTS client side transaction context seems not being propagated to EAP server

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/JBTM-2428?page=com.atlassian.jira.plugin.... ] Tomasz Adamski reassigned JBTM-2428: ------------------------------------ Assignee: Ondřej Chaloupka (was: Tomasz Adamski) > JTS client side transaction context seems not being propagated to EAP server > ---------------------------------------------------------------------------- > > Key: JBTM-2428 > URL: https://issues.jboss.org/browse/JBTM-2428 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.1.1 > Reporter: Ondřej Chaloupka > Assignee: Ondřej Chaloupka > > It seems that transaction context is not propagated when JTS transaction is started on client. > This was working for EAP 6.4 where iiop corba implementation was used. The testing client is based on guide [1]. > The call from client to server via IIOP [4] works fine but when I'm trying to start transaction on client side and then expecting being propagated to server, server proclaims that there is no txn in the context. > This is how the orb is set up [2] > This is how the transaction is started [3] > This is how the remote call on ejb app server is done [4] > [1] https://developer.jboss.org/wiki/TransactionPropagationWithJBoss > [2] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-tra... > [3] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-tra... > [4] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-tra... > [5] [com.arjuna.ats.jts] (main) ARJUNA022251: The ORBManager is already associated with an ORB/OA. > FINE [javax.enterprise.resource.corba._DEFAULT_.rpc.protocol] (main) "IOP01600014: (BAD_INV_ORDER) Cannot access this attribute or method at this point": org.omg.CORBA.BAD_INV_ORDER: vmcid: OMG minor code: 14 completed: No > -- or -- > FINE [javax.enterprise.resource.corba._CORBA_.rpc.presentation] (main) "IOP00110227: (BAD_PARAM) ORBDynamicStubFactoryFactoryClass property had value com.sun.corba.se.impl.presentation.rmi.bcel.StubFactoryFactoryBCELImpl, which could not be loaded by the ORB ClassLoader": org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 227 completed: No -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2442) Update to use activemq-messaging subsystem in the standalone-blacktie.xml

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2442?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2442: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/880 > Update to use activemq-messaging subsystem in the standalone-blacktie.xml > ------------------------------------------------------------------------- > > Key: JBTM-2442 > URL: https://issues.jboss.org/browse/JBTM-2442 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration, BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > currently the wildfly 10.0.0.Alpha4 changes to use the activemq-messaging and the default resource adapter of the MDB changed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2398) Support VolatileStore.allObjUids

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2398?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2398: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support VolatileStore.allObjUids > --------------------------------- > > Key: JBTM-2398 > URL: https://issues.jboss.org/browse/JBTM-2398 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Performance Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.later > > > This method is used by REST-AT and would be a useful addition for baselining the performance of the coordinator for comparison with non transactional and empty transaction requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2448) Upgrade wildfly to 10.0.0.Alpha5-SNAPSHOT

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2448?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2448: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade wildfly to 10.0.0.Alpha5-SNAPSHOT > ----------------------------------------- > > Key: JBTM-2448 > URL: https://issues.jboss.org/browse/JBTM-2448 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2448) Upgrade wildfly to 10.0.0.Alpha5-SNAPSHOT

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2448?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2448: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/879 > Upgrade wildfly to 10.0.0.Alpha5-SNAPSHOT > ----------------------------------------- > > Key: JBTM-2448 > URL: https://issues.jboss.org/browse/JBTM-2448 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2448) Upgrade wildfly to 10.0.0.Alpha5-SNAPSHOT

by Amos Feng (JIRA)

Amos Feng created JBTM-2448: ------------------------------- Summary: Upgrade wildfly to 10.0.0.Alpha5-SNAPSHOT Key: JBTM-2448 URL: https://issues.jboss.org/browse/JBTM-2448 Project: JBoss Transaction Manager Issue Type: Task Components: Application Server Integration Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2447) BlackTie build failure - requires investigation

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2447: ----------------------------------- Summary: BlackTie build failure - requires investigation Key: JBTM-2447 URL: https://issues.jboss.org/browse/JBTM-2447 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Tom Jenkinson Assignee: Amos Feng http://albany.eng.hst.ams2.redhat.com/job/narayana/745/PROFILE=BLACKTIE,j... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2238) Tooling does not expose CMR records

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2238?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2238: ------------------------------------- Work in progress quickstart: https://github.com/jbosstm/quickstart/pull/128/ > Tooling does not expose CMR records > ----------------------------------- > > Key: JBTM-2238 > URL: https://issues.jboss.org/browse/JBTM-2238 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.3 > > > CMR resources are not being exposed as MBeans via the (com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser) tooling. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2444) jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2444?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2444: --------------------------------------- REAT-AT Bridge test with JMS fails now. It's because they haven't updated standalone-rts.xml and standalone-xts.xml configurations to use ActiveMQ. I've checked it locally and that is the issue. Seems that they have planned backwards compatibility, but it's not yet implemented: https://issues.jboss.org/browse/WFLY-4586. I have notified Jeff about this: https://issues.jboss.org/browse/WFLY-4584. > jta-1_2-in-wildfly quickstart is failing - presume related to update from HornetQ to ActiveMQ > --------------------------------------------------------------------------------------------- > > Key: JBTM-2444 > URL: https://issues.jboss.org/browse/JBTM-2444 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.next > > > {code} > Running org.jboss.narayana.quickstarts.jta.TestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.563 sec <<< FAILURE! > Results : > Tests in error: > org.jboss.narayana.quickstarts.jta.TestCase: Cannot deploy: test.war > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 > {code} > The log file says: > {code} > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /home/hudson/workspace/narayana-quickstarts/wildfly-10.0.0.Alpha4-SNAPSHOT/standalone/tmp/vfs/temp/temp174d29cf17a7dbea/content-a7b7e754b2627502/WEB-INF/test-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[23,1] > Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}} > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42) > at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55) > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77) > ... 96 more > {code} > Which leads me to believe it is likely due to the parsing in test-jms.xml. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2442) Update to use activemq-messaging subsystem in the standalone-blacktie.xml

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2442?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2442: ---------------------------- Fix Version/s: 5.next (was: 5.later) > Update to use activemq-messaging subsystem in the standalone-blacktie.xml > ------------------------------------------------------------------------- > > Key: JBTM-2442 > URL: https://issues.jboss.org/browse/JBTM-2442 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration, BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > currently the wildfly 10.0.0.Alpha4 changes to use the activemq-messaging and the default resource adapter of the MDB changed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 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 June 2015