April 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-326) TxImporter is not thread-safe and it is used concurrent environment

by Pavel Kadlec (JIRA)

TxImporter is not thread-safe and it is used concurrent environment ------------------------------------------------------------------- Key: JBTM-326 URL: http://jira.jboss.com/jira/browse/JBTM-326 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP7 Environment: JBoss-4.2.1.GA Reporter: Pavel Kadlec TxImporter is used by com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple. The field TxImporter._transactions is static and there can be more XATerminatorImple objects in JVM or there can more threads in one XATerminatorImple object. The access to that field is not synchronized. Type of the field is non-synchronized HashMap. -- 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-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

16 years, 3 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

16 years, 3 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

16 years, 3 months

3
8
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

16 years, 3 months

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

16 years, 3 months

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

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2008