March 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2117) codeCoverage job config appears to be still set up to create an emma report

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2117: ----------------------------------- Summary: codeCoverage job config appears to be still set up to create an emma report Key: JBTM-2117 URL: https://issues.jboss.org/browse/JBTM-2117 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.0.2 http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/ Mike, please can you change the emma config to whatever jacoco config we need to create the report? Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2117) codeCoverage job can't create report

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2117?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2117: -------------------------------- Summary: codeCoverage job can't create report (was: codeCoverage job config appears to be still set up to create an emma report) > codeCoverage job can't create report > ------------------------------------ > > Key: JBTM-2117 > URL: https://issues.jboss.org/browse/JBTM-2117 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/ > Mike, please can you change the emma config to whatever jacoco config we need to create the report? > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2117) codeCoverage job can't create report

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2117?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2117: ------------------------------------- http://172.17.131.2/job/narayana-codeCoverage/107/ > codeCoverage job can't create report > ------------------------------------ > > Key: JBTM-2117 > URL: https://issues.jboss.org/browse/JBTM-2117 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/ > Mike, please can you change the emma config to whatever jacoco config we need to create the report? > Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2116) SPI: Unique identifier for a transaction

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBTM-2116: ------------------------------------- Summary: SPI: Unique identifier for a transaction Key: JBTM-2116 URL: https://issues.jboss.org/browse/JBTM-2116 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jesper Pedersen Assignee: Michael Musgrove The Narayana SPI should provide a method that returns a unique identifier for a transaction that is stable for its entire lifecycle. {noformat} public Object getIdentifier(Transaction tx) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2066) Replace Emma with JaCoCo

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2066?page=com.atlassian.jira.plugin.... ] Gytis Trikleris reopened JBTM-2066: ----------------------------------- Jacoco failed to create a report http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/106/ > Replace Emma with JaCoCo > ------------------------ > > Key: JBTM-2066 > URL: https://issues.jboss.org/browse/JBTM-2066 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SPI > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.2 > > > http://172.17.131.2/job/narayana-codeCoverage/92/consoleText > {code} > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /home/hudson/workspace/narayana-codeCoverage/ArjunaJTA/spi/src/test/java/io/narayana/spi/util/DummyXAResource.java:[39,75] diamond operator is not supported in -source 1.6 > (use -source 7 or higher to enable diamond operator) > [INFO] 1 error > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2105) TxStats.enable generates excessive GC overhead

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2105?page=com.atlassian.jira.plugin.... ] Work on JBTM-2105 started by Tom Jenkinson. > TxStats.enable generates excessive GC overhead > ---------------------------------------------- > > Key: JBTM-2105 > URL: https://issues.jboss.org/browse/JBTM-2105 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.15, 5.0.1 > Reporter: Will Reichert > Assignee: Tom Jenkinson > Labels: performance > Fix For: 5.0.2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > TxStats.enable() calls arjPropertyManager.getCoordinatorEnvironmentBean() with each invocation which results in String concatenation to generate a HashMap key. The String concatenation generated 1.61GB of GC overhead during a 20 minute performance test. Changing TxStats to use a private static reference to the Bean decreases the GC overhead to 20KB for the same 20 minute test -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2105) TxStats.enable generates excessive GC overhead

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2105?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2105. --------------------------------- Resolution: Done > TxStats.enable generates excessive GC overhead > ---------------------------------------------- > > Key: JBTM-2105 > URL: https://issues.jboss.org/browse/JBTM-2105 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.15, 5.0.1 > Reporter: Will Reichert > Assignee: Tom Jenkinson > Labels: performance > Fix For: 5.0.2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > TxStats.enable() calls arjPropertyManager.getCoordinatorEnvironmentBean() with each invocation which results in String concatenation to generate a HashMap key. The String concatenation generated 1.61GB of GC overhead during a 20 minute performance test. Changing TxStats to use a private static reference to the Bean decreases the GC overhead to 20KB for the same 20 minute test -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2105) TxStats.enable generates excessive GC overhead

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2105?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2105: -------------------------------- Assignee: Will Reichert (was: Tom Jenkinson) > TxStats.enable generates excessive GC overhead > ---------------------------------------------- > > Key: JBTM-2105 > URL: https://issues.jboss.org/browse/JBTM-2105 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.15, 5.0.1 > Reporter: Will Reichert > Assignee: Will Reichert > Labels: performance > Fix For: 5.0.2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > TxStats.enable() calls arjPropertyManager.getCoordinatorEnvironmentBean() with each invocation which results in String concatenation to generate a HashMap key. The String concatenation generated 1.61GB of GC overhead during a 20 minute performance test. Changing TxStats to use a private static reference to the Bean decreases the GC overhead to 20KB for the same 20 minute test -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2105) TxStats.enable generates excessive GC overhead

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2105?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2105: -------------------------------- Fix Version/s: 5.0.2 (was: 4.17.15) (was: 4.17.18) > TxStats.enable generates excessive GC overhead > ---------------------------------------------- > > Key: JBTM-2105 > URL: https://issues.jboss.org/browse/JBTM-2105 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.17.15, 5.0.1 > Reporter: Will Reichert > Assignee: Tom Jenkinson > Labels: performance > Fix For: 5.0.2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > TxStats.enable() calls arjPropertyManager.getCoordinatorEnvironmentBean() with each invocation which results in String concatenation to generate a HashMap key. The String concatenation generated 1.61GB of GC overhead during a 20 minute performance test. Changing TxStats to use a private static reference to the Bean decreases the GC overhead to 20KB for the same 20 minute test -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2054) JNDI names from JTAEnvironmentBean should be used in ArjunaJTA/cdi classes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2054?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2054: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JNDI names from JTAEnvironmentBean should be used in ArjunaJTA/cdi classes > -------------------------------------------------------------------------- > > Key: JBTM-2054 > URL: https://issues.jboss.org/browse/JBTM-2054 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.0.2 > > > Currently ArjunaJTA/cdi uses java:/jboss namespace for JNDI lookup. However, in standalone mode such names do not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2014