October 2009 - jbossts-issues - Jboss List Archives

[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

14 years, 5 months

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

14 years, 5 months

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

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-299) Xid pack should ignore trailing zeros

by Mark Little (JIRA)

Xid pack should ignore trailing zeros ------------------------------------- Key: JBTM-299 URL: http://jira.jboss.com/jira/browse/JBTM-299 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP6 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.6 It packs the whole array even if most of it is zeros. -- 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

14 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-636) Need a way of determining the age of a transaction post prepare

by Michael Musgrove (JIRA)

Need a way of determining the age of a transaction post prepare --------------------------------------------------------------- Key: JBTM-636 URL: https://jira.jboss.org/jira/browse/JBTM-636 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.8.0 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 5.0.0 The management tools for JBossTM need to be able to display the age of a transaction post prepare stage to enable monitoring of 'wedged' transactions. This information is currently not available. -- 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

14 years, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-615) Remove Gandiva code

by Mark Little (JIRA)

Remove Gandiva code ------------------- Key: JBTM-615 URL: https://jira.jboss.org/jira/browse/JBTM-615 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: future Not needed these 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

14 years, 5 months

1
12
0 / 0

[JBoss JIRA] Created: (JBTM-597) Implement subordinate coordinator for WS-BA

by Andrew Dinn (JIRA)

Implement subordinate coordinator for WS-BA ------------------------------------------- Key: JBTM-597 URL: https://jira.jboss.org/jira/browse/JBTM-597 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.7.0 Reporter: Andrew Dinn Assignee: Andrew Dinn The WS-BA protocol implementation should allow propagated transactions to be coordinated by a subordinate coordinator as currently happens with WS-AT. BA-enabled web services should be allowed to access this functionality by installing a server side JaxWS handler as per the WS-AT subordinate implementation. -- 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

14 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-610) Restore mutex handling on LockManager

by Mark Little (JIRA)

Restore mutex handling on LockManager ------------------------------------- Key: JBTM-610 URL: https://jira.jboss.org/jira/browse/JBTM-610 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 4.8.0 It looks like someone tried to optimize the synchronizations around LockManager, probably for HP-MS performance tuning. Unfortunately they didn't fully understand the implications. Backing out to original approach until/unless performance becomes an issue again. -- 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

14 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBTM-630) Update docs on Node Name due to Uid changes

by Mark Little (JIRA)

Update docs on Node Name due to Uid changes ------------------------------------------- Key: JBTM-630 URL: https://jira.jboss.org/jira/browse/JBTM-630 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assignee: Mark Little Fix For: 4.9.0 -- 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

14 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-629) Change XTS to work with immutable Uid

by Mark Little (JIRA)

Change XTS to work with immutable Uid ------------------------------------- Key: JBTM-629 URL: https://jira.jboss.org/jira/browse/JBTM-629 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Reporter: Mark Little Assignee: Andrew Dinn Fix For: 4.9.0 -- 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

14 years, 5 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 October 2009