October 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-404) Add Recovery for Business Activities

by Andrew Dinn (JIRA)

Add Recovery for Business Activities ------------------------------------ Key: JBTM-404 URL: https://jira.jboss.org/jira/browse/JBTM-404 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.4.CR1 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.6 The XTS WS-BA implementation needs to implement coordinator and participant recovery -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-422) UserTransaction rollback trips over null pointer and generates inappropriate error

by Andrew Dinn (JIRA)

UserTransaction rollback trips over null pointer and generates inappropriate error ---------------------------------------------------------------------------------- Key: JBTM-422 URL: https://jira.jboss.org/jira/browse/JBTM-422 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.4.0.GA Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.5 The WS-AT remote UserTransactionImple rollback method fails to detect the case where there is no TX associated with the calling thread and trips over the resulting null pointer generating an invalid error code. This problem appears in both 1.0 and 1.1 implementations and also affects methods in the WS-BA UserBusinessActivityImple class. This should be fixed by checking for null and explicitly throwing a WrongStateException which needs to be added to the parent API class. This is as near as possible to the JTA behaviour where an IllegalStateException is thrown. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBTM-31) Support August 2005 WS-Addressing Candidate Recommendation

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-31?page=com.atlassian.jira.plugin... ] Mark Little closed JBTM-31. --------------------------- Resolution: Out of Date > Support August 2005 WS-Addressing Candidate Recommendation > ---------------------------------------------------------- > > Key: JBTM-31 > URL: https://jira.jboss.org/jira/browse/JBTM-31 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assignee: Kevin Conner > Fix For: 4.6 > > > When the WS-TX specifications are upgraded to support the latest version of WS-Addressing, the product will have to do likewise. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-252) Documentation: left align paragraphs to remove extra spacing

by Daniel Bevenius (JIRA)

Documentation: left align paragraphs to remove extra spacing ------------------------------------------------------------ Key: JBTM-252 URL: http://jira.jboss.com/jira/browse/JBTM-252 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Trivial Some of the docs (maybe all) have paragraphs which are not left aligned which is causing extra spacing between words. Simply making the paragraphs left aligned will rectify this. Thanks, Daniel -- 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, 6 months

3
7
0 / 0

[JBoss JIRA] Closed: (JBTM-55) Public WS-A endpoint for testing purposes

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-55?page=com.atlassian.jira.plugin... ] Mark Little closed JBTM-55. --------------------------- Resolution: Out of Date > Public WS-A endpoint for testing purposes > ----------------------------------------- > > Key: JBTM-55 > URL: https://jira.jboss.org/jira/browse/JBTM-55 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assignee: Kevin Conner > Priority: Minor > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Put the W3C-tested WS-A endpoint up for public access. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-228) Check that endSuspendedRMs called if transaction times out

by Mark Little (JIRA)

Check that endSuspendedRMs called if transaction times out ---------------------------------------------------------- Key: JBTM-228 URL: http://jira.jboss.com/jira/browse/JBTM-228 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Reporter: Mark Little Assigned To: Mark Little -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-366) integrate heuristics resolution tool with AS 5.0

by Jonathan Halliday (JIRA)

integrate heuristics resolution tool with AS 5.0 ------------------------------------------------ Key: JBTM-366 URL: http://jira.jboss.com/jira/browse/JBTM-366 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Application Server Integration, Recovery, Tooling Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Fix For: 4.6 The existing object store browser runs as a standalone process and is present only in the full TS distribution. We should have a subset of this functionality integrated with AS 5.0, so that app server users can view and cleanup tx. Ideally this should integrate seamlessly with the rest of the AS tooling e.g. console integration. The prototyping Maciej did to make the existing objectstore browser runnable from the browser in AS 4.x is a step in the right direction. However, we can't really decide how this should work until the final state of the tooling for AS 5.0 becomes clear. This may therefore follow in a point release after 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-389) TransactionStatusManager and Recovery integration without Sockets

by Dmitri Voronov (JIRA)

TransactionStatusManager and Recovery integration without Sockets ----------------------------------------------------------------- Key: JBTM-389 URL: https://jira.jboss.org/jira/browse/JBTM-389 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.2.3 Environment: JBoss 4.2.3 Reporter: Dmitri Voronov Attachments: jboss-jta-without-sockets.zip In the current JBoss integration the communication within arjuna occurs over Sockets whereby the communication is within the same JVM and doesn't need to use any socket or listen on any ports. This requires a configuration overhead, if the ports should be determined. If no ports have been configured, the next free port is opened. In our environment we manage the port ranges per JBoss instance, e.g. https, rmi etc. My suggestion is to use piped streams (see attachment) ; it would prevent the changes on Arjuna's API and the internal algorithms. -- 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, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-407) Add new Process implementations

by Mark Little (JIRA)

Add new Process implementations ------------------------------- Key: JBTM-407 URL: https://jira.jboss.org/jira/browse/JBTM-407 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.4.CR1 Reporter: Mark Little Assignee: Mark Little Fix For: 4.5 JDK 5 and JDK 6 give us some more interesting options. However, even with 4 there are some alternatives. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-334) deprecate NORMAL mode reaper

by Jonathan Halliday (JIRA)

deprecate NORMAL mode reaper ---------------------------- Key: JBTM-334 URL: http://jira.jboss.com/jira/browse/JBTM-334 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3.0.BETA2 Reporter: Jonathan Halliday Fix For: 4.4 It is misleading to have DYNAMIC be the default whilst NORMAL still exists. Deprecate NORMAL, replacing it with equivalent PERIODIC. Make DYNAMIC the default in properties file and code. -- 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, 7 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 October 2008