October 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1963) Automatically added TXBridge handler should be optional

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1963?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1963. ------------------------------- > Automatically added TXBridge handler should be optional > ------------------------------------------------------- > > Key: JBTM-1963 > URL: https://issues.jboss.org/browse/JBTM-1963 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M6 > > > XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException. > The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory. > We could write a wrapper for the current handler, which will delegate the call only if the transaction is available. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-589) Document static initializers

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-589?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-589: ------------------------------- Fix Version/s: 5.0.0.M2 (was: 5.0.0.Final) > Document static initializers > ---------------------------- > > Key: JBTM-589 > URL: https://issues.jboss.org/browse/JBTM-589 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, Transaction Core, XTS > Affects Versions: 4.7.0 > Reporter: Mark Little > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M2 > > > Or remove them. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-589) Document static initializers

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-589?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson closed JBTM-589. ------------------------------ > Document static initializers > ---------------------------- > > Key: JBTM-589 > URL: https://issues.jboss.org/browse/JBTM-589 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, Transaction Core, XTS > Affects Versions: 4.7.0 > Reporter: Mark Little > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M2 > > > Or remove them. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1963) Automatically added TXBridge handler should be optional

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1963?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1963: -------------------------------- Fix Version/s: 5.0.0.M6 (was: 5.0.0.Final) > Automatically added TXBridge handler should be optional > ------------------------------------------------------- > > Key: JBTM-1963 > URL: https://issues.jboss.org/browse/JBTM-1963 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M6 > > > XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException. > The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory. > We could write a wrapper for the current handler, which will delegate the call only if the transaction is available. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1444) Review the logging in XTS when participants throw Exceptions in phase 2 methods

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1444?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1444: -------------------------------- Fix Version/s: 5.0.0.M6 (was: 5.0.0.Final) > Review the logging in XTS when participants throw Exceptions in phase 2 methods > ------------------------------------------------------------------------------- > > Key: JBTM-1444 > URL: https://issues.jboss.org/browse/JBTM-1444 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M6 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 0 minutes > > To experiment: > 1. Take the JDF WS-AT and WS-BA quickstarts. > 2. Update the server logging to TRACE for the 'arjuna' catagory. > 3. Observe what happens when the declared exceptions (and RuntimeException) are thrown from each of the phase two methods on the participants (close, compensate, commit, rollback). > 3.1 We are interested in what logging is produced (and at what log level) and what behaviour it has on the application (does it hang, is an exception returned to the client, or something else). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1444) Review the logging in XTS when participants throw Exceptions in phase 2 methods

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1444?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1444. ------------------------------- > Review the logging in XTS when participants throw Exceptions in phase 2 methods > ------------------------------------------------------------------------------- > > Key: JBTM-1444 > URL: https://issues.jboss.org/browse/JBTM-1444 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M6 > > Original Estimate: 1 day > Time Spent: 1 day > Remaining Estimate: 0 minutes > > To experiment: > 1. Take the JDF WS-AT and WS-BA quickstarts. > 2. Update the server logging to TRACE for the 'arjuna' catagory. > 3. Observe what happens when the declared exceptions (and RuntimeException) are thrown from each of the phase two methods on the participants (close, compensate, commit, rollback). > 3.1 We are interested in what logging is produced (and at what log level) and what behaviour it has on the application (does it hang, is an exception returned to the client, or something else). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1459) Create a parallel version of beforeCompletion invocations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1459?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1459. ------------------------------- > Create a parallel version of beforeCompletion invocations > --------------------------------------------------------- > > Key: JBTM-1459 > URL: https://issues.jboss.org/browse/JBTM-1459 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > Some RM's do the bulk of there work in the beforeCompletion synchronisations so it would be beneficial to have an option for calling it asynchronously. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1459) Create a parallel version of beforeCompletion invocations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1459?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1459: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > Create a parallel version of beforeCompletion invocations > --------------------------------------------------------- > > Key: JBTM-1459 > URL: https://issues.jboss.org/browse/JBTM-1459 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > Some RM's do the bulk of there work in the beforeCompletion synchronisations so it would be beneficial to have an option for calling it asynchronously. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1327) QA Test Suite Failures

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1327?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1327. ------------------------------- > QA Test Suite Failures > ---------------------- > > Key: JBTM-1327 > URL: https://issues.jboss.org/browse/JBTM-1327 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > Parent JIRA for QA test failures -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1464) Some performance tests are missing the timing code.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1464?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1464: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > Some performance tests are missing the timing code. > --------------------------------------------------- > > Key: JBTM-1464 > URL: https://issues.jboss.org/browse/JBTM-1464 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Performance Testing, Testing, Transaction Core > Affects Versions: 4.17.3 > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 5.0.0.M5 > > > The TXOJ performance tests are supposed to get the start time before running and then the end time after completion, printing out the difference. It seems that in several of them, the end time is no longer obtained and nothing is printed out either, i.e., no elapsed time is given. This makes these tests pretty useless as performance tests. Rather than remove the tests, the elapsed time check should be put back. -- 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, 8 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 October 2013