September 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-399) Set up continuous integration build system

by Mark Little (JIRA)

Set up continuous integration build system ------------------------------------------ Key: JBTM-399 URL: https://jira.jboss.org/jira/browse/JBTM-399 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Mark Little Maybe running mini-QA setup from old Arjuna days? -- 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, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-595) Add support for JBoss LogManager backend

by David Lloyd (JIRA)

Add support for JBoss LogManager backend ---------------------------------------- Key: JBTM-595 URL: https://jira.jboss.org/jira/browse/JBTM-595 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Common Reporter: David Lloyd Priority: Minor The new log manager in AS 6.0 supports internationalization and localization natively. Provide an implementation which does not rely on log4j or JCL anymore since those technologies are bug-ridden and obsolete. Patch attached. -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-555) make memory leak tests more robust

by Jonathan Halliday (JIRA)

make memory leak tests more robust ---------------------------------- Key: JBTM-555 URL: https://jira.jboss.org/jira/browse/JBTM-555 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing, Transaction Core Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: future Some tests in the txcore group attempt to detect memory leaks by setup System.gc() take memory reading doTransactionStuff System.gc() take another memory reading This is unreliable, as System.gc() is only advisory to the runtime. There is no way to FORCE gc from within the jvm. This causes the tests to be somewhat unreliable. Dirty tricks to work around this include running the tests with a small heap (-Xmx5m). With less free space to work with, the gc tries harder. On a default size heap it mostly ignores System.gc(). Unfortunately the test framework does not make it easy to set -Xmx on a per test / test group basis. Similar effect could perhaps be achieved by allocating all except a small portion of the available heap from within the vm using eg. new byte[]. There is also the jvmti ForceGarbageCollection method, but that would require us to have a chunk of C code on each test platform, which is a pain. -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-612) check use of isDebugEnabled/debugAllowed

by Jonathan Halliday (JIRA)

check use of isDebugEnabled/debugAllowed ---------------------------------------- Key: JBTM-612 URL: https://jira.jboss.org/jira/browse/JBTM-612 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common Affects Versions: 4.7.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9 The CLF exposes an rather complex API, in which isDebugEnabled and debugAllowed have different semantics. As pretty much everything is logged, the cost of these methods, and especially the cost of incorrect usage that leads to creating debug messages that just get throw away, is a non-trivial overhead. Both the implementation of these methods and their usage is suspect and needs a review. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-414) atsintegration classes not internationalized

by Mark Little (JIRA)

atsintegration classes not internationalized -------------------------------------------- Key: JBTM-414 URL: https://jira.jboss.org/jira/browse/JBTM-414 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: 4.6 -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-418) ExpiredEntryScanner does not delete old state after move

by Mark Little (JIRA)

ExpiredEntryScanner does not delete old state after move -------------------------------------------------------- Key: JBTM-418 URL: https://jira.jboss.org/jira/browse/JBTM-418 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: 4.5 -- 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-300) Move stale transaction logs

by Mark Little (JIRA)

Move stale transaction logs --------------------------- Key: JBTM-300 URL: http://jira.jboss.com/jira/browse/JBTM-300 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assigned To: Mark Little Priority: Optional We should generalise the ExpiryScanner implementation of TopLevelTransaction in JTS so that logs that cannot be recovered after a set period of time are moved elsewhere for manual intervention. -- 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-234) setRollbackOnly consistency

by Mark Little (JIRA)

setRollbackOnly consistency --------------------------- Key: JBTM-234 URL: http://jira.jboss.com/jira/browse/JBTM-234 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP4 Reporter: Mark Little Assigned To: Mark Little Priority: Optional OTS does not let you call rollback-only if the state of the transaction is not active. JTA doesn't make it clear whether or not that is an error. That makes it implementation dependent. At the moment both of our JTA implementations mask this issue. AS appears to not expect an exception from setRollbackOnly either, but that's may cause an issue if someone uses a different JTA. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-592) Add fallback for Utility::hostInetAddr()

by Jesper Pedersen (JIRA)

Add fallback for Utility::hostInetAddr() ---------------------------------------- Key: JBTM-592 URL: https://jira.jboss.org/jira/browse/JBTM-592 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Common Affects Versions: 4.6.1 Reporter: Jesper Pedersen Priority: Minor If a host has a misconfigured hostname Utility::hostInetAddr() fails with an UnknownHostException. An extra try could be made after logging a warning about the failed InetAddress.getLocalHost() using InetAddress.getByName(null) - e.g. try { addr = InetAddress.getLocalHost(); } catch (UnknownHostException uhe) { log.warn("Unable to use InetAddress.getLocalHost() to resolve address"); addr = InetAddress.getByName(null); } -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-593) read-only optimization in configuration should point general second phase instead of second phase abort.

by Vicky Kak (JIRA)

read-only optimization in configuration should point general second phase instead of second phase abort. -------------------------------------------------------------------------------------------------------- Key: JBTM-593 URL: https://jira.jboss.org/jira/browse/JBTM-593 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Vicky Kak Assignee: Mark Little I can see the read-only optimization details provided in the docs as "Enable or disable read-only optimization for the second phase abort." http://www.jboss.org/jbosstm/docs/4.2.3/manuals/html/core/ProgrammersGuid... The read-only optimization should work for second phase in general, irrespective of it being rollback/commit. The abort in "second phase abort." seems to be pointing to the rollback process in second phase. There should be a change of "second phase abort" to "second phase" -- 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, 1 month

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2009