February 2018 - jbossts-issues - Jboss List Archives

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

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2989: --------------------------------- yeah, I think it can be resolved. > 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.8.0.Final > > > 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, 9 months

1
0
0 / 0

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

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2989: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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.8.0.Final > > > 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, 9 months

1
0
0 / 0

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

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2989: ---------------------------- Fix Version/s: 5.8.0.Final (was: 5.next) > 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.8.0.Final > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #76 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > 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.<init>(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.<init>(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.<init>(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.<init>(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.<init>(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)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2991) Deprecate old StartXAResource interface

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2991?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2991: ---------------------------------- Fix Version/s: 5.8.0.Final > Deprecate old StartXAResource interface > --------------------------------------- > > Key: JBTM-2991 > URL: https://issues.jboss.org/browse/JBTM-2991 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Fix For: 5.8.0.Final > > > All support for this was moved to org.jboss.tm.FirstResource in the SPI -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2991) Deprecate old StartXAResource interface

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2991?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2991: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Deprecate old StartXAResource interface > --------------------------------------- > > Key: JBTM-2991 > URL: https://issues.jboss.org/browse/JBTM-2991 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Fix For: 5.8.0.Final > > > All support for this was moved to org.jboss.tm.FirstResource in the SPI -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

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

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2988?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2988: --------------------------------------- hi [~mmusgrov], checking jiras for the 5.8.0.Final release. As I can see PRs being merged, do you think this is fixed and could be marked as resolved with the appropriate fix version? > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2621) Tests that rely on the old perf benchmark harness need porting to use JMH

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2621?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2621: --------------------------------------- hi [~mmusgrov], checking jiras for the 5.8.0.Final release. As I can see PRs being merged, do you think this is fixed and could be marked as resolved with the appropriate fix version? > Tests that rely on the old perf benchmark harness need porting to use JMH > ------------------------------------------------------------------------- > > Key: JBTM-2621 > URL: https://issues.jboss.org/browse/JBTM-2621 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > The relevant tests are: > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance1 > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance3 > if there are no others then once ported the old performance benchmark harness can be removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2925) TM jdbc driver list should be enriched with driver name for DB2 driver

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2925?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2925: ---------------------------------- Fix Version/s: 5.7.0.Final > TM jdbc driver list should be enriched with driver name for DB2 driver > ---------------------------------------------------------------------- > > Key: JBTM-2925 > URL: https://issues.jboss.org/browse/JBTM-2925 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Affects Versions: 5.6.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.7.0.Final > > > The list of the "supported" jdbc driver names should be enhanced with DB2 driver name which is {{IBM Data Server Driver for JDBC and SQLJ}}. > In case the need to verify the connection metadata you can try to check small tool here > https://github.com/ochaloup/jdbc-driver-load -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2925) TM jdbc driver list should be enriched with driver name for DB2 driver

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2925?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2925: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TM jdbc driver list should be enriched with driver name for DB2 driver > ---------------------------------------------------------------------- > > Key: JBTM-2925 > URL: https://issues.jboss.org/browse/JBTM-2925 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Affects Versions: 5.6.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.7.0.Final > > > The list of the "supported" jdbc driver names should be enhanced with DB2 driver name which is {{IBM Data Server Driver for JDBC and SQLJ}}. > In case the need to verify the connection metadata you can try to check small tool here > https://github.com/ochaloup/jdbc-driver-load -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 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 February 2018