February 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2341) Add two more statistics

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2341: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/808, https://github.com/jbosstm/documentation/pull/29 (was: https://github.com/jbosstm/narayana/pull/806) > Add two more statistics > ----------------------- > > Key: JBTM-2341 > URL: https://issues.jboss.org/browse/JBTM-2341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Add the following two statistics: > System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log); > Average Commit Time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2343) New interface for tracking thread-to-transaction association changes

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2343: -------------------------------------- Summary: New interface for tracking thread-to-transaction association changes Key: JBTM-2343 URL: https://issues.jboss.org/browse/JBTM-2343 Project: JBoss Transaction Manager Issue Type: Feature Request Components: SPI Affects Versions: 5.0.4 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.5 We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2342) Add callbacks for thread-to-transaction association changes

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2342: -------------------------------------- Summary: Add callbacks for thread-to-transaction association changes Key: JBTM-2342 URL: https://issues.jboss.org/browse/JBTM-2342 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Application Server Integration Affects Versions: 5.0.4 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.5 This feature calls for a mechanism to avoid issues around concurrent access to a JPA EM if a transaction times out. Currently EM cleanup happens in AC callbacks - if those callbacks happen on the application thread there is no issue but if they happen on the reaper thread then it is possible for the EM to be manipulated whilst the application is still using it. The linked forum thread came up with 4 proposals to handle the problem: # Reaper marks transaction as set rollback only: this solution has potentially insurmountable issues (eg JVM1 -> JVM2, JVM1 crashes, txn never gets commit/rollback called on it). In addition it would need to be configurable - some users want the reaper to do the timely rollback; # WildFly wraps the TM/TSR and coordinates the running of all Synchronization callbacks. This solution is complex and does the AS have sufficient knowledge to coordinate callbacks correctly. Option 4 below is similar but the decision about what to do and when to do it is left in the hands of the relevant callbacks where the knowlege resides; # Start a discussion on the JPA expert group to get certain thread unsafe Synchronization JPA callbacks used by EE container/Persistence providers changed. This is an option for the future; # Trigger callbacks when the transaction is disassociated from a thread. For example, detaching any loaded entities and closing the EM can be done when all relevant callbacks, namely the afterCompletion callback (triggered on the reaper thread) and the txn disassociated callback (triggered on the application thread) have been seen. This JIRA will implement option 4. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2300) XATMI implemenation tests failed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2300?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2300: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana... HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] > XATMI implemenation tests failed > -------------------------------- > > Key: JBTM-2300 > URL: https://issues.jboss.org/browse/JBTM-2300 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/694/PROFIL... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2341) Add two more statistics

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-2341: --------------------------------- Hi Mike, as per Marks comment on the forum I don't think https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... is clear the method is calculating the timing of the commit() call not the time from begin -> commit(). > Add two more statistics > ----------------------- > > Key: JBTM-2341 > URL: https://issues.jboss.org/browse/JBTM-2341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Add the following two statistics: > System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log); > Average Commit Time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2341) Add two more statistics

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2341: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add two more statistics > ----------------------- > > Key: JBTM-2341 > URL: https://issues.jboss.org/browse/JBTM-2341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Add the following two statistics: > System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log); > Average Commit Time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2341) Add two more statistics

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2341: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/806 > Add two more statistics > ----------------------- > > Key: JBTM-2341 > URL: https://issues.jboss.org/browse/JBTM-2341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Add the following two statistics: > System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log); > Average Commit Time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2326) Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2326?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2326: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1178798|https://bugzilla.redhat.com/show_bug.cgi?id=1178798] from ON_QA to VERIFIED > Provide a management interface to see a list of Xids that are being being considered for recovery by the recovery manager > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2326 > URL: https://issues.jboss.org/browse/JBTM-2326 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Tooling > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > Although it is possible to see the list of current transactions in the CLI, for those branches that are available for recovery it can be useful to see the list that the recovery manager is considering. I have often looked in the debugger at this state: > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com... so it might be useful to others. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2341) Add two more statistics

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2341: -------------------------------- Forum Reference: https://developer.jboss.org/message/918972#918972 > Add two more statistics > ----------------------- > > Key: JBTM-2341 > URL: https://issues.jboss.org/browse/JBTM-2341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Add the following two statistics: > System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log); > Average Commit Time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2341) Add two more statistics

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2341: -------------------------------------- Summary: Add two more statistics Key: JBTM-2341 URL: https://issues.jboss.org/browse/JBTM-2341 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Transaction Core Affects Versions: 5.0.4 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.5 Add the following two statistics: System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log); Average Commit Time. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 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 2015