May 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2349) CompensationContext is destroyed once the first handler is invoked

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2349?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2349. ------------------------------- > CompensationContext is destroyed once the first handler is invoked > ------------------------------------------------------------------ > > Key: JBTM-2349 > URL: https://issues.jboss.org/browse/JBTM-2349 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.1.0 > > > https://github.com/jbosstm/narayana/blob/master/compensations/src/main/ja... > https://github.com/jbosstm/narayana/blob/master/compensations/src/main/ja... > If there are two handlers (compensation or confirmation), which need to access the same compensation scoped object, only the first one will succeed. Once the first handler is invoked from the ParticipantImpl, CompensationScope is destroyed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2356) REST-AT recovery failure

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2356?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2356. ------------------------------- > REST-AT recovery failure > ------------------------ > > Key: JBTM-2356 > URL: https://issues.jboss.org/browse/JBTM-2356 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.1.0 > > > See linked forum post: > Start two serves A and B with the coordinator running on A and a participant on server B. Crash server B just before commit. When server B comes back up the coordinator fails to recover the transaction and returns 404 when asked about the transaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2101) Blacktie integration CSTest hang

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2101?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2101. ------------------------------- > Blacktie integration CSTest hang > -------------------------------- > > Key: JBTM-2101 > URL: https://issues.jboss.org/browse/JBTM-2101 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.1.0 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/427/PROFILE=BLACK... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2316) Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2316?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2316. ------------------------------- > Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage > --------------------------------------------------------------------- > > Key: JBTM-2316 > URL: https://issues.jboss.org/browse/JBTM-2316 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > I can't see the transactional driver or JTAx stuff in the code-coverage report and I also don't think its worth aggregating in the performance test harness into the coverage numbers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2367) Move ClassLoadingUtil from core to common

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2367?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2367. ------------------------------- > Move ClassLoadingUtil from core to common > ----------------------------------------- > > Key: JBTM-2367 > URL: https://issues.jboss.org/browse/JBTM-2367 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Common > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.1.0 > > > It can be moved down the hierarchy to remove the need for orbportability to depend on arjunacore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2374) Blacktie XATIM TestConnection test hanging

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2374?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2374. ------------------------------- > Blacktie XATIM TestConnection test hanging > ------------------------------------------ > > Key: JBTM-2374 > URL: https://issues.jboss.org/browse/JBTM-2374 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/804/ > Stack dump: http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/804/PROFIL... > {code} > Running org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.TestConnection > [0m18:35:21,173 INFO [org.codehaus.stomp.jms.StompConnect] (StompConnect Server Thread: tcp://127.0.0.1:61613) Looking up name: java:/ConnectionFactory in JNDI InitialContext for JMS ConnectionFactory > [0m[0m18:35:21,177 INFO [org.codehaus.stomp.jms.StompConnect] (StompConnect Server Thread: tcp://127.0.0.1:61613) Looking up name: java:/JmsXA in JNDI InitialContext for JMS ConnectionFactory > [0m[31m18:35:21,179 ERROR [org.codehaus.stomp.tcp.TcpTransportServer] (StompConnect Server Thread: tcp://127.0.0.1:61613) Received accept error: javax.naming.NameNotFoundException: JmsXA -- service jboss.naming.context.java.JmsXA: javax.naming.NameNotFoundException: JmsXA -- service jboss.naming.context.java.JmsXA > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:411) > at javax.naming.InitialContext.lookup(InitialContext.java:411) > at org.codehaus.stomp.jms.StompConnect.createXAConnectionFactory(StompConnect.java:195) > at org.codehaus.stomp.jms.StompConnect.getXAConnectionFactory(StompConnect.java:84) > at org.codehaus.stomp.jms.StompConnect.assignProtocolConverter(StompConnect.java:64) > at org.codehaus.stomp.tcp.TcpTransportServer.run(TcpTransportServer.java:82) > at java.lang.Thread.run(Thread.java:744) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1572) a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1572?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1572. ------------------------------- > a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't > ------------------------------------------------------------------------------------------------ > > Key: JBTM-1572 > URL: https://issues.jboss.org/browse/JBTM-1572 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.1.0 > > Attachments: client.valgrind, JBTM-1572.txt, JBTM-1572.zip, server.valgrind, windbg.out > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Note, it will definitely be worth doing this in a branch/pull as I suspect the database isn't running atm so that will need a kick too -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2141) Narayana WildFly branch pull request CI testing does not work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2141?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2141. ------------------------------- > Narayana WildFly branch pull request CI testing does not work > ------------------------------------------------------------- > > Key: JBTM-2141 > URL: https://issues.jboss.org/browse/JBTM-2141 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.1.0 > > > Firstly, poller does not pass the correct branch to build. > Secondly, if correct branch is passed, the testing job fails to rebase WildFly. > CI failure after wrong branch passed: http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-wildfly/1... > CI failure after rebase failure: http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-wildfly/1... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2308. ------------------------------- > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.1.0 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2330) Document the procedure to discover and resolve heuristically completed branches in Narayana

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2330?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2330. ------------------------------- > Document the procedure to discover and resolve heuristically completed branches in Narayana > ------------------------------------------------------------------------------------------- > > Key: JBTM-2330 > URL: https://issues.jboss.org/browse/JBTM-2330 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > Our documentation is not complete in this area. We need to describe how users can detect heuristically completed branches in the system. It would be useful to consider this in standalone and embedded wildfly modes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 2 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 May 2015