May 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-277) add jax-ws context processors

by Jonathan Halliday (JIRA)

add jax-ws context processors ----------------------------- Key: JBTM-277 URL: http://jira.jboss.com/jira/browse/JBTM-277 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.2.3.SP5 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.4 We currently have handlers (header context processors) only for jax-rpc. Add ones for jax-ws, including refactoring common code out of the existing handlers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-240) Add Spring configuration to documentation

by Mark Little (JIRA)

Add Spring configuration to documentation ----------------------------------------- Key: JBTM-240 URL: http://jira.jboss.com/jira/browse/JBTM-240 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Jonathan Halliday Fix For: 4.4 We should add this http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossTransactionsWithSpring to the shipped docs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-360) test framework for transactions in JBossAS

by Jonathan Halliday (JIRA)

test framework for transactions in JBossAS ------------------------------------------ Key: JBTM-360 URL: http://jira.jboss.com/jira/browse/JBTM-360 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration, Testing Affects Versions: 4.3.0.BETA2 Reporter: Jonathan Halliday Assigned To: Michael Musgrove Fix For: 4.4 The JBossAS testsuite has some coverage of basic transactions behaviour. However, there is no support for e.g. crash recovery testing. Investigate how we can test JBossTS in JBossAS more fully. DTF? JBossAS server management project? Develop additional tooling as required. Actual test development may be handed off to QE? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-346) XTS coordinator recovery

by Jonathan Halliday (JIRA)

XTS coordinator recovery ------------------------ Key: JBTM-346 URL: http://jira.jboss.com/jira/browse/JBTM-346 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Assigned To: Andrew Dinn Fix For: 4.4.CR1 Take the prototype recovery module for XTS coordinator and wire it up to the XTS .sar deployment, so that it gets registered and unregistered when XTS is deployed/undeployed into JBossAS. Check that it works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBTM-335) AS 5.0 integration needs new crash recovery handling

by Jonathan Halliday (JIRA)

AS 5.0 integration needs new crash recovery handling ---------------------------------------------------- Key: JBTM-335 URL: http://jira.jboss.com/jira/browse/JBTM-335 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.3.0.BETA2 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.4 We need to work with the AS team to design and implement integration of transaction crash recovery for AS 5.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-357) add open source DTF tests

by Jonathan Halliday (JIRA)

add open source DTF tests ------------------------- Key: JBTM-357 URL: http://jira.jboss.com/jira/browse/JBTM-357 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.4.CR1 As the DTF is now open source, we should open source the DTF tests for JBossTS (i.e. jbossts-qa) and add it to the JBossTS code repository -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-331) Reduce the log level of the periodic recovery stuff

by David Lloyd (JIRA)

Reduce the log level of the periodic recovery stuff --------------------------------------------------- Key: JBTM-331 URL: http://jira.jboss.com/jira/browse/JBTM-331 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery Reporter: David Lloyd The JBossAS log (as of 5.0.0.Beta4) is filled with this kind of thing: 2008-02-28 17:57:51,703 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <Thu, 28 Feb 2008 17:57:51> 2008-02-28 17:57:51,703 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] AtomicActionRecoveryModule: Second pass 2008-02-28 17:57:51,703 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - second pass 2008-02-28 17:57:51,703 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass 2008-02-28 17:59:51,703 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - first pass <Thu, 28 Feb 2008 17:59:51> 2008-02-28 17:59:51,704 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] StatusModule: first pass 2008-02-28 17:59:51,704 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass 2008-02-28 17:59:51,704 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass These messages ought to be at TRACE level. The first hint is that this is the only thing spamming the log after successful startup. Also on more than one occasion, folks pop into the public #jboss IRC channel asking about why their logs get spammed with these messages. An otherwise idle JBossAS instance quietly gobbles 750kb of disk space a day with these messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-304) Update the management MBean with all of the collected statistics

by Mark Little (JIRA)

Update the management MBean with all of the collected statistics ---------------------------------------------------------------- Key: JBTM-304 URL: http://jira.jboss.com/jira/browse/JBTM-304 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Reporter: Mark Little Assigned To: Andrew Dinn Priority: Minor JBossTS collects more information than the MBean now exposes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-354) race condition in XAResource start/end handling due to async rollback

by Jonathan Halliday (JIRA)

race condition in XAResource start/end handling due to async rollback --------------------------------------------------------------------- Key: JBTM-354 URL: http://jira.jboss.com/jira/browse/JBTM-354 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Affects Versions: 4.3.0.GA, 4.2.3.SP5 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.2.3.SP8, 4.4.CR1 There exists a race condition such that we may call start on an XAResource but never call end (or anything else) on it if the transaction times out whilst the resource enlistment is still in progress. This is a Bad Thing and may make resource managers unhappy. To reproduce: TransactionManager tm = new TransactionManagerImple(); tm.setTransactionTimeout(5); tm.begin(); Transaction t = tm.getTransaction(); // XAResourceImpl has a start method with Thread.sleep longer than 5s XAResource xaResource = new XAResourceImpl(); t.enlistResource(xaResource); Thread.sleep(10); // reaper times out the tx, resource manager for XAResource // *may* have received start but never receives end. Fix notes: TransactionImple.enlistResource needs to lock out the reaper thread. At first glance an alternative fix is to put the resource into the transaction's internal data structure before calling start on it, but that would allow an 'end, begin' sequence of calls to be seen by the resource manager. caution: ref support case i-t #171373 there *may* exist additional race conditions in the app server JCA so this change alone won't necessarily fix the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-370) xts participant comenstate() exception handling improvements

by Jonathan Halliday (JIRA)

xts participant comenstate() exception handling improvements ------------------------------------------------------------ Key: JBTM-370 URL: http://jira.jboss.com/jira/browse/JBTM-370 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.3.0.GA, 4.2.3.SP7 Reporter: Jonathan Halliday Assigned To: Andrew Dinn Fix For: 4.2.3.SP8, 4.4.CR1 In the XTS demo app, TaxiParticipantBA.compensate throws a SystemException. This is regarded by XTS as a potentially transitory problem and thus the compensate is retried at 30 second intervals. We should instead throw FaultedException, which indicated a permanent error. Further, the javadoc for BusinessAgreementWithParticipantCompletionParticipant should be updated to clarify the behaviour of these exceptions and the circumstances in which each should be used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2008