September 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2504) Investigate why throughput of JTS performance comparison test is 0

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2504?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2504: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Investigate why throughput of JTS performance comparison test is 0 > ------------------------------------------------------------------ > > Key: JBTM-2504 > URL: https://issues.jboss.org/browse/JBTM-2504 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > We need to investigate why throughput of JTS performance comparison test is coming out at 0 ([~mmusgrov] thinks it is because it`s very slow); -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 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.2.3.Final (was: 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.2.3.Final > > > 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)

8 years, 7 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 closed JBTM-2514. ---------------------------------- > 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.2.3.Final > > > 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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2504) Investigate why throughput of JTS performance comparison test is 0

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2504?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2504: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/performance/pull/23 > Investigate why throughput of JTS performance comparison test is 0 > ------------------------------------------------------------------ > > Key: JBTM-2504 > URL: https://issues.jboss.org/browse/JBTM-2504 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > We need to investigate why throughput of JTS performance comparison test is coming out at 0 ([~mmusgrov] thinks it is because it`s very slow); -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.s... ] Michael Musgrove updated JBTM-741: ---------------------------------- Fix Version/s: 5.next (was: 5.2.3.Final) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1340: ----------------------------------- Fix Version/s: 5.next (was: 5.2.3.Final) > BeanPopulator overhead needs looking into > ----------------------------------------- > > Key: JBTM-1340 > URL: https://issues.jboss.org/browse/JBTM-1340 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 4.17.2 > Environment: Mac OS 10.7 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.next > > > During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit. > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance > 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder.<init> > 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString > 0.0% - 320 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey > 0.0% - 61 µs - 10,000 inv. java.lang.Class.getName > 0.0% - 25 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.get -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-855) Create an example showing integration with Spring

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.s... ] Michael Musgrove updated JBTM-855: ---------------------------------- Fix Version/s: 5.next (was: 5.2.3.Final) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2110?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2110: ----------------------------------- Fix Version/s: 5.next (was: 5.2.3.Final) > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.jboss.org/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1854) Journal failures in CI test suite on JDKORB

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1854: ----------------------------------- Fix Version/s: 5.next (was: 5.2.3.Final) > Journal failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1804: ----------------------------------- Fix Version/s: 5.next (was: 5.2.3.Final) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 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 September 2015