January 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2612?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2612: ----------------------------------- Assignee: Tom Jenkinson > Deploy jdbc module to the Maven repository > ------------------------------------------ > > Key: JBTM-2612 > URL: https://issues.jboss.org/browse/JBTM-2612 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2612: ------------------------------------- Summary: Deploy jdbc module to the Maven repository Key: JBTM-2612 URL: https://issues.jboss.org/browse/JBTM-2612 Project: JBoss Transaction Manager Issue Type: Task Components: JTA Reporter: Gytis Trikleris Fix For: 5.next Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2609) Make JDBCStore able to handle JEE errors interfacing with a datasource in an app server

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2609?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #969 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Make JDBCStore able to handle JEE errors interfacing with a datasource in an app server > --------------------------------------------------------------------------------------- > > Key: JBTM-2609 > URL: https://issues.jboss.org/browse/JBTM-2609 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently the handling is all expected to be JSE typed exceptions like an SQLexception. It seems that in an app server a variety of other exception types can be thrown not just limited to JNDI exceptions. It has been reported that IllegalStateException can be thrown when an app server is rebooting and the datasource is not available for lookup. > Changing to handle all exceptions in JDBCImple_Driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2517?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2517. ------------------------------------ Resolution: Done The benchmark results and bar chart are now uploaded to the artefact repo (https://github.com/jbosstm/artifacts) with a suitable git comment, for example: bq. Generated on host haverstraw (Tue 19 Jan 11:09:06 GMT 2016) using tag 5.2.12.Final > 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: Performance Testing, 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2611) Make consistent usage of surefire version in quickstart poms

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2611?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2611: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Make consistent usage of surefire version in quickstart poms > ------------------------------------------------------------- > > Key: JBTM-2611 > URL: https://issues.jboss.org/browse/JBTM-2611 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Some of the quickstarts use 2.4.3 of surefire plugin (amongst others used by other quickstarts). Lets standardise these on the current version. The reason this change is required is because some times the quickstart runs fail on lancel (probably something about this nodes .m2) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2553: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2553: -------------------------------- Priority: Minor (was: Major) > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-741: ------------------------------- Fix Version/s: 5.later > 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: Sub-task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > > 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, 5 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1804: -------------------------------- Priority: Minor (was: Major) > 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: Sub-task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Priority: Minor > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2305) Incomplete tooling documentation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2305?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2305: -------------------------------- Priority: Minor (was: Major) > Incomplete tooling documentation > -------------------------------- > > Key: JBTM-2305 > URL: https://issues.jboss.org/browse/JBTM-2305 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. > In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 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 January 2016