December 2014 - jbossts-issues - Jboss List Archives

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2308: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/795 > 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.0.5 > > > 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.11#6341)

10 years

1
0
0 / 0

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2308: ----------------------------------- Fix Version/s: 4.17.27 > 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.0.5 > > > 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.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2124: ----------------------------------- If context propagation is used then there are two possible scenarios: (i) the application code uses the Explicit Interposition class with the context passed in via the method parameter - in which case we're in the same situation as with interposition. (ii) the application code uses the context passed in to register resources, play with the coordinator ref in some way, and (depending upon whether the field is null or not) play with the terminator ref in some way. In this case we're in the same situation as if the resource were local to the coordinator (or at least the coordinator that is referenced in the context passed in, which could of course be something other than the root coordinator). In this case there's nothing special going on under the covers - no interposition, no subordinate coordinator, no log entry other than one the resource creates and which it would've created if it were in the same address space as the coordinator referenced in the context. The tooling approach should work fine in both of these cases. > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondřej Chaloupka > Assignee: Gytis Trikleris > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2323) Resume dualstack testing on the NCL CI cluster

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2323: ----------------------------------- Summary: Resume dualstack testing on the NCL CI cluster Key: JBTM-2323 URL: https://issues.jboss.org/browse/JBTM-2323 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.0.5 The new CI nodes are not configured for IPv6. As this is a bit specialised it would make sense to keep this job back on the Newcastle cluster. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2322) Add el7 to the Narayana CI matrix for BlackTie

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2322: ----------------------------------- Summary: Add el7 to the Narayana CI matrix for BlackTie Key: JBTM-2322 URL: https://issues.jboss.org/browse/JBTM-2322 Project: JBoss Transaction Manager Issue Type: Task Components: BlackTie Reporter: Tom Jenkinson Assignee: Amos Feng Fix For: 5.0.5 Currently we do not build blacktie on the EL7 node (sansa). We should do this and add it to the narayana matrix job: http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2124: ------------------------------------- We need to consider whether this can work for both interposition and context propagation and whether there are caveats. > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondřej Chaloupka > Assignee: Gytis Trikleris > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2124: ----------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondřej Chaloupka > Assignee: Gytis Trikleris > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2321) apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2321: ------------------------------------- Summary: apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build Key: JBTM-2321 URL: https://issues.jboss.org/browse/JBTM-2321 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie, Build System Reporter: Gytis Trikleris Assignee: Amos Feng Fix For: 5.0.5 http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-quickstart... {code} [ERROR] Failed to execute goal on project blacktie-C: Could not resolve dependencies for project org.jboss.narayana.blacktie:blacktie-C:pom:5.0.5.Final-SNAPSHOT: Could not find artifact apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 in jbossThirdParty (https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/) -> [Help 1] {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2319) Annotation-less STM

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2319?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2319: ----------------------------------- Create a different type of Container class (e.g., Receptable or Vessel) that doesn't expect annotations to be used and a new InvocationHandler (e.g., CallHandler) that uses a separately provided configuration object which contains the equivalent information that annotations would normally provide. > Annotation-less STM > ------------------- > > Key: JBTM-2319 > URL: https://issues.jboss.org/browse/JBTM-2319 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Mark Little > > Vert.x 3 works by auto-generating code for different language bindings to modules. Some of these languages don't support annotations. Hence the current STM implementation won't be applicable. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2319) Annotation-less STM

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2319?page=com.atlassian.jira.plugin.... ] Work on JBTM-2319 started by Mark Little. ----------------------------------------- > Annotation-less STM > ------------------- > > Key: JBTM-2319 > URL: https://issues.jboss.org/browse/JBTM-2319 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.4 > Reporter: Mark Little > Assignee: Mark Little > > Vert.x 3 works by auto-generating code for different language bindings to modules. Some of these languages don't support annotations. Hence the current STM implementation won't be applicable. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2014