August 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-401) Resource Leakage in Transactional Driver

by Michael Musgrove (JIRA)

Resource Leakage in Transactional Driver ---------------------------------------- Key: JBTM-401 URL: https://jira.jboss.org/jira/browse/JBTM-401 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.4.CR1 Environment: Standalone JTA build Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.4.0.GA Use the Transactional Driver to get a JDBC connection (this returns a ConnectionImple which wraps the connection to the real resource and enlists/delists it with transactions). After running about 500 transactions the underlying resource throws an error reporting "Too many connections" (I tried this on Derby and MySql XA drivers). The real connection is implemented by RecoverableXAConnection - when a transaction completes the reference to the real connection is nulled (and therefore not closed) so on the next transaction a new connection is obtained so the resource manager eventually runs out of connections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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-386) Overriding property manager plugin doesn't work

by Rune Molin (JIRA)

Overriding property manager plugin doesn't work ----------------------------------------------- Key: JBTM-386 URL: https://jira.jboss.org/jira/browse/JBTM-386 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.3.SP5 Environment: all Reporter: Rune Molin Setting the property "com.arjuna.common.util.propertyservice.pluginclassname" has no effect . In PropertyManagerImpl, line 357: PropertyManagerIOPlugin plugin = (PropertyManagerIOPlugin)Thread.currentThread().getContextClassLoader().loadClass(pluginClassname).newInstance(); Should propably read: PropertyManagerIOPlugin plugin = (PropertyManagerIOPlugin)Thread.currentThread().getContextClassLoader().loadClass(classname).newInstance(); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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] Assigned: (JBTM-48) Move tools to Eclipse?

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-48?page=com.atlassian.jira.plugin... ] Mark Little reassigned JBTM-48: ------------------------------- Assignee: Michael Musgrove (was: Mark Little) > Move tools to Eclipse? > ---------------------- > > Key: JBTM-48 > URL: https://jira.jboss.org/jira/browse/JBTM-48 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.4.0.GA > > > Currently we have a set of management tools that use their own graphical interfaces (jgraph I think). Do we maintain these, or move them all to run within Eclipse? It seems that Eclipse is the way to go for any development tools, but I'm not convinced about run-time management tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBTM-48) Move tools to Eclipse?

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-48?page=com.atlassian.jira.plugin... ] Mark Little updated JBTM-48: ---------------------------- Fix Version/s: 4.4.0.GA Affects Version/s: 4.2 > Move tools to Eclipse? > ---------------------- > > Key: JBTM-48 > URL: https://jira.jboss.org/jira/browse/JBTM-48 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.4.0.GA > > > Currently we have a set of management tools that use their own graphical interfaces (jgraph I think). Do we maintain these, or move them all to run within Eclipse? It seems that Eclipse is the way to go for any development tools, but I'm not convinced about run-time management tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[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

15 years, 8 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Assigned: (JBTM-220) Run performance suite

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-220?page=com.atlassian.jira.plugi... ] Mark Little reassigned JBTM-220: -------------------------------- Assignee: Michael Musgrove (was: Mark Little) > Run performance suite > --------------------- > > Key: JBTM-220 > URL: https://jira.jboss.org/jira/browse/JBTM-220 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Mark Little > Assignee: Michael Musgrove > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
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] Closed: (JBTM-199) overriding bootclasspath in orbspecific.xml

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-199?page=com.atlassian.jira.plugi... ] Mark Little closed JBTM-199. ---------------------------- Resolution: Out of Date The latest version of Mac OS 10 and the Apple JDK fixes this. > overriding bootclasspath in orbspecific.xml > ------------------------------------------- > > Key: JBTM-199 > URL: https://jira.jboss.org/jira/browse/JBTM-199 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Process > Affects Versions: 4.2.2 > Reporter: Mark Little > Assignee: Mark Little > Priority: Trivial > Fix For: 4.4.2 > > > orbspecific.xml overrides the bootclasspath with rt.jar when running the various CORBA IDL compilers. Does it need to? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2008