July 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-330) PropagationContextManager.getTransactionPropagationContext() to log returned tpc

by Galder Zamarreno (JIRA)

PropagationContextManager.getTransactionPropagationContext() to log returned tpc -------------------------------------------------------------------------------- Key: JBTM-330 URL: http://jira.jboss.com/jira/browse/JBTM-330 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3.0.BETA2, 4.2.3.SP6 Reporter: Galder Zamarreno >From a support point of view, it'd be really helpful if the JTA and JTS PropagationContextManager logged which tcp is returned when getTransactionPropagationContext() is called. I have done a local patch for the JTA version as a result of trying to figure out how it worked internally: public Object getTransactionPropagationContext() { if (log.isDebugEnabled()) { log.debug("PropagationContextManager.getTransactionPropagationContext - called"); } String txid = ((BasicAction.Current() == null) ? null : BasicAction.Current().get_uid().stringForm()); if (log.isDebugEnabled()) { log.debug("PropagationContextManager.getTransactionPropagationContext - returned tpc = " + txid); } return txid; } If everyone's happy with this, I can commit it myself. Thoughts? -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-287) 1PC mentioned in XTS docs

by Mark Little (JIRA)

1PC mentioned in XTS docs ------------------------- Key: JBTM-287 URL: http://jira.jboss.com/jira/browse/JBTM-287 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Priority: Trivial -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-280) Convert documents over to OpenOffice format

by Mark Little (JIRA)

Convert documents over to OpenOffice format ------------------------------------------- Key: JBTM-280 URL: http://jira.jboss.com/jira/browse/JBTM-280 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: Mark Little Looks like this is the best option now. -- 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

15 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-382) allow objectstore browser to run as applet from JBossAS console

by Jonathan Halliday (JIRA)

allow objectstore browser to run as applet from JBossAS console --------------------------------------------------------------- Key: JBTM-382 URL: http://jira.jboss.com/jira/browse/JBTM-382 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Assigned To: Michael Musgrove Fix For: 4.4.CR2 The objectstore browser, or more generally the tooling framework it's based on, is a swing app. It would be nice if it also functioned as an applet, so we can integrate it with the management console for JBossAS 5. Maciej has already prototyped this, see https://svn.jboss.org/repos/labs/labs/jbosstm/workspace/jhalliday/mm_tool... Dust off this work, merge it back to trunk and figure out how best to package it. Additional considerations include the heuristics resolution work and remote operation (the applet running in a browser that's not on the same host as the AS instance it downloaded from). These may not make it into the AS 5.0 iteration. -- 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

15 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-317) Add optional support for HTTPS

by Mark Little (JIRA)

Add optional support for HTTPS ------------------------------ Key: JBTM-317 URL: http://jira.jboss.com/jira/browse/JBTM-317 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-T Implementation Reporter: Mark Little Assigned To: Andrew Dinn Fix For: 4.4 -- 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

15 years, 8 months

1
1
0 / 0

[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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-272) default reaper interval too long for CTS tests

by Jonathan Halliday (JIRA)

default reaper interval too long for CTS tests ---------------------------------------------- Key: JBTM-272 URL: http://jira.jboss.com/jira/browse/JBTM-272 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.4 Following changes for http://jira.jboss.com/jira/browse/JBTM-237, the default 120s interval for NORMAL mode tx reaper is too long for some JEE TCK tests. Consider shortening the default to e.g. 20s or switching to DYNAMIC, at least for use inside JBossAS. -- 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

15 years, 8 months

2
2
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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-371) improve getTimeLeftBeforeTransactionTimeout implementation

by Jonathan Halliday (JIRA)

improve getTimeLeftBeforeTransactionTimeout implementation ---------------------------------------------------------- Key: JBTM-371 URL: http://jira.jboss.com/jira/browse/JBTM-371 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.3.0.GA, 4.2.3.SP7 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.2.3.SP8, 4.4.CR1 The JBossAS integration code (specifically TransactionManagerDelegate) includes an implementation of the TransactionTimeoutConfiguration.getTimeLeftBeforeTransactionTimeout method. The behaviour of this method does not currently match the expectations of the AS code. The integration SPI is not particularly well documented but it's clear we can make some modifications to improve matters. For the maintenance branch (TS 4.2.3.SP, AS 4.x) these will be limited to improving exception handling. For trunk (TS 4.4, AS 5.0) we can make more extensive changes, perhaps encompassing modification of the integration SPI and taking advantage of the transaction reaper changes to support actually returning a sensible value from this method. -- 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

15 years, 8 months

1
2
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

15 years, 9 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2008