September 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2514) TransactionManagerService stop does not run orb and oa shutdown hooks

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2514?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2514: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/914 (was: https://github.com/jbosstm/narayana/pull/911, https://github.com/jbosstm/narayana/pull/913) > TransactionManagerService stop does not run orb and oa shutdown hooks > --------------------------------------------------------------------- > > Key: JBTM-2514 > URL: https://issues.jboss.org/browse/JBTM-2514 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.0.4, 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next, 5.0.7 > > > The transaction manager service that we use for integration with app servers in JTS mode (com.arjuna.ats.jbossatx.jts.TransactionManagerService()) does not run any of our orb shutdown hooks in its stop method. The reason for this is that we use an orb supplied by the app server which we do not wrap so none of the shutdown hooks in our wrappers get called. In particular the JavaIdlRCShutdown hook isn't called so it is not possible to restart the RecoveryService (see JavaIdlRCServiceInit) with the consequence that the wildfly reload management operation fails. > In summary, the scope of the fix is: > * ensure that our (orb portablility layer) shutdown hooks are called when the TM service is stopped > * ensure that we do not shutdown an externally supplied orb -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2518) Product comparison benchmark CI job fails with OutOfMemoryError

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2518: -------------------------------------- Summary: Product comparison benchmark CI job fails with OutOfMemoryError Key: JBTM-2518 URL: https://issues.jboss.org/browse/JBTM-2518 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Affects Versions: 5.2.2 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmar... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2517) Update the Narayana Release Process doc to include performance figures

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2517: -------------------------------------- Summary: Update the Narayana Release Process doc to include performance figures Key: JBTM-2517 URL: https://issues.jboss.org/browse/JBTM-2517 Project: JBoss Transaction Manager Issue Type: Task Components: Release Process Affects Versions: 5.2.2 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next Include a description in the NRP document of how to blog about performance figures when releasing a new version of Narayana -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2516) Privileged actions in XTS

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2516?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2516: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/915 > Privileged actions in XTS > ------------------------- > > Key: JBTM-2516 > URL: https://issues.jboss.org/browse/JBTM-2516 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > In some places we need to use PrivilegedAction in order to make XTS work with enabled security manager. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2516) Privileged actions in XTS

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2516: ------------------------------------- Summary: Privileged actions in XTS Key: JBTM-2516 URL: https://issues.jboss.org/browse/JBTM-2516 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next In some places we need to use PrivilegedAction in order to make XTS work with enabled security manager. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2514) TransactionManagerService stop does not run orb and oa shutdown hooks

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2514?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2514: ----------------------------------- Fix Version/s: 5.0.7 > TransactionManagerService stop does not run orb and oa shutdown hooks > --------------------------------------------------------------------- > > Key: JBTM-2514 > URL: https://issues.jboss.org/browse/JBTM-2514 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.0.4, 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next, 5.0.7 > > > The transaction manager service that we use for integration with app servers in JTS mode (com.arjuna.ats.jbossatx.jts.TransactionManagerService()) does not run any of our orb shutdown hooks in its stop method. The reason for this is that we use an orb supplied by the app server which we do not wrap so none of the shutdown hooks in our wrappers get called. In particular the JavaIdlRCShutdown hook isn't called so it is not possible to restart the RecoveryService (see JavaIdlRCServiceInit) with the consequence that the wildfly reload management operation fails. > In summary, the scope of the fix is: > * ensure that our (orb portablility layer) shutdown hooks are called when the TM service is stopped > * ensure that we do not shutdown an externally supplied orb -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2514) TransactionManagerService stop does not run orb and oa shutdown hooks

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2514?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2514: ----------------------------------- Fix Version/s: 5.next > TransactionManagerService stop does not run orb and oa shutdown hooks > --------------------------------------------------------------------- > > Key: JBTM-2514 > URL: https://issues.jboss.org/browse/JBTM-2514 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.0.4, 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The transaction manager service that we use for integration with app servers in JTS mode (com.arjuna.ats.jbossatx.jts.TransactionManagerService()) does not run any of our orb shutdown hooks in its stop method. The reason for this is that we use an orb supplied by the app server which we do not wrap so none of the shutdown hooks in our wrappers get called. In particular the JavaIdlRCShutdown hook isn't called so it is not possible to restart the RecoveryService (see JavaIdlRCServiceInit) with the consequence that the wildfly reload management operation fails. > In summary, the scope of the fix is: > * ensure that our (orb portablility layer) shutdown hooks are called when the TM service is stopped > * ensure that we do not shutdown an externally supplied orb -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2514) TransactionManagerService stop does not run orb and oa shutdown hooks

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2514?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2514: ----------------------------------- Affects Version/s: 5.0.4 > TransactionManagerService stop does not run orb and oa shutdown hooks > --------------------------------------------------------------------- > > Key: JBTM-2514 > URL: https://issues.jboss.org/browse/JBTM-2514 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.0.4, 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > The transaction manager service that we use for integration with app servers in JTS mode (com.arjuna.ats.jbossatx.jts.TransactionManagerService()) does not run any of our orb shutdown hooks in its stop method. The reason for this is that we use an orb supplied by the app server which we do not wrap so none of the shutdown hooks in our wrappers get called. In particular the JavaIdlRCShutdown hook isn't called so it is not possible to restart the RecoveryService (see JavaIdlRCServiceInit) with the consequence that the wildfly reload management operation fails. > In summary, the scope of the fix is: > * ensure that our (orb portablility layer) shutdown hooks are called when the TM service is stopped > * ensure that we do not shutdown an externally supplied orb -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2514) TransactionManagerService stop does not run orb and oa shutdown hooks

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2514?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2514: -------------------------------- Description: The transaction manager service that we use for integration with app servers in JTS mode (com.arjuna.ats.jbossatx.jts.TransactionManagerService()) does not run any of our orb shutdown hooks in its stop method. The reason for this is that we use an orb supplied by the app server which we do not wrap so none of the shutdown hooks in our wrappers get called. In particular the JavaIdlRCShutdown hook isn't called so it is not possible to restart the RecoveryService (see JavaIdlRCServiceInit) with the consequence that the wildfly reload management operation fails. In summary, the scope of the fix is: * ensure that our (orb portablility layer) shutdown hooks are called when the TM service is stopped * ensure that we do not shutdown an externally supplied orb was:The transaction manager service that we use for integration with app servers in JTS mode (com.arjuna.ats.jbossatx.jts.TransactionManagerService()) does not run any of our orb shutdown hooks in its stop method. The reason for this is that we use an orb supplied by the app server which we do not wrap so none of the shutdown hooks in our wrappers get called. In particular the JavaIdlRCShutdown hook isn't called so it is not possible to restart the RecoveryService (see JavaIdlRCServiceInit) with the consequence that the wildfly reload management operation fails. > TransactionManagerService stop does not run orb and oa shutdown hooks > --------------------------------------------------------------------- > > Key: JBTM-2514 > URL: https://issues.jboss.org/browse/JBTM-2514 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > The transaction manager service that we use for integration with app servers in JTS mode (com.arjuna.ats.jbossatx.jts.TransactionManagerService()) does not run any of our orb shutdown hooks in its stop method. The reason for this is that we use an orb supplied by the app server which we do not wrap so none of the shutdown hooks in our wrappers get called. In particular the JavaIdlRCShutdown hook isn't called so it is not possible to restart the RecoveryService (see JavaIdlRCServiceInit) with the consequence that the wildfly reload management operation fails. > In summary, the scope of the fix is: > * ensure that our (orb portablility layer) shutdown hooks are called when the TM service is stopped > * ensure that we do not shutdown an externally supplied orb -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2514) TransactionManagerService stop does not run orb and oa shutdown hooks

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2514?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2514: ---------------------------------------- I have added another PR to ensure that we do not shutdown the external orb (since other systems may still be using it). > TransactionManagerService stop does not run orb and oa shutdown hooks > --------------------------------------------------------------------- > > Key: JBTM-2514 > URL: https://issues.jboss.org/browse/JBTM-2514 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > The transaction manager service that we use for integration with app servers in JTS mode (com.arjuna.ats.jbossatx.jts.TransactionManagerService()) does not run any of our orb shutdown hooks in its stop method. The reason for this is that we use an orb supplied by the app server which we do not wrap so none of the shutdown hooks in our wrappers get called. In particular the JavaIdlRCShutdown hook isn't called so it is not possible to restart the RecoveryService (see JavaIdlRCServiceInit) with the consequence that the wildfly reload management operation fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2015