August 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-699) Command line interface to modifying transaction log during recovery

by Mark Little (JIRA)

Command line interface to modifying transaction log during recovery ------------------------------------------------------------------- Key: JBTM-699 URL: https://jira.jboss.org/jira/browse/JBTM-699 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery, Tooling, Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 4.10.0 Similar to the OS browser. -- 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, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBTM-784) incorrect ORB initialization

by Jonathan Halliday (JIRA)

incorrect ORB initialization ---------------------------- Key: JBTM-784 URL: https://jira.jboss.org/browse/JBTM-784 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS, Recovery Affects Versions: 4.12.0 Reporter: Jonathan Halliday Assignee: Mark Little Fix For: 4.13.0 When running the TransactionManager and RecoveryManager in the same JVM, the ORB initialization incorrectly attempts to setup the ORB twice: WARN: ARJUNA-22251 The ORBManager is already associated with an ORB/OA. The correct model is one ORB and two POAs, whereas we currently have two ORBs. See ORBManager; RecoveryORBManager (both have ORB field); ORB/InternalORB (why the subclass?) method initORB->InitLoader->ORBSetup; JacOrbRCServiceInit -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-779) Add refactored XTS Development Guide to XTS upstream documentation repo

by Misty Stanley-Jones (JIRA)

Add refactored XTS Development Guide to XTS upstream documentation repo ----------------------------------------------------------------------- Key: JBTM-779 URL: https://jira.jboss.org/browse/JBTM-779 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-700) Look at restructuring docs

by Mark Little (JIRA)

Look at restructuring docs -------------------------- Key: JBTM-700 URL: https://jira.jboss.org/jira/browse/JBTM-700 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assignee: Mark Little Fix For: 4.11.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

15 years, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-776) Enable XTS client deployments without the need for a JaxWS endpoint

by Andrew Dinn (JIRA)

Enable XTS client deployments without the need for a JaxWS endpoint ------------------------------------------------------------------- Key: JBTM-776 URL: https://jira.jboss.org/browse/JBTM-776 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.12.0 Reporter: Andrew Dinn Assignee: Andrew Dinn It would be very useful if the XTS client code could be deployed embedded with JBossTS without the need to deploy any JaxWS endpoints i.e. so that it only required httpclient capability. This would allow development of, say, CXF-based clients running on a simple desktop system which use embedded TS/XTS to provide transactional access to web services. Removal of the JaxWS endpoints avoids the need to expose the desktop machine with a public IP address, open up fire walls etc which are serious barriers to such deployments. At present implementing this change is stopped by two factors: - the XTS code cannot be built and configured as a client only deployment - the Completion protocols used by WS-AT and WS-BA to terminate transactions employ one way messages the latter requirement forces the client to expose an endpoint for delivery of the message confirming and identifying the outcome of a termination request. The first problem will be addressed by a related issue. Solving the second problem requires implementing an alternative version of the Completion services employing protocol messages with an RPC message exchange pattern. For WS-BA this raises no serious issues since the BA standard does not specify the details of the Completion protocol -- we can do what we like in this regard. In the case of WS-AT the spec does define the protocol. So, any alternative we provide will be non-standard i.e. it willl only work if the client is talking to a JBoss coordinator (this is already the situation for our or anyone else's BA client implementation, mind you). While this does not invalidate adding this feature it does qualify its utility since clients developed using this extension will not be portable. If this feature works and is useful it woudl be worth lobbying to get it adopted as part of the standard. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-777) Reorganise impleemntation to allow independent deploy/initialise of client, participant and coordinator services

by Andrew Dinn (JIRA)

Reorganise impleemntation to allow independent deploy/initialise of client, participant and coordinator services ---------------------------------------------------------------------------------------------------------------- Key: JBTM-777 URL: https://jira.jboss.org/browse/JBTM-777 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.12.0 Reporter: Andrew Dinn Assignee: Andrew Dinn It would be helpful if it were easier to configure which XTS services get started when XTS is deployed. It should be possible to deploy some proper subset of the client, participant and coordinator services if that is all that will be required by the deployment. This is particularly important for enabling a client only version of XTS to be shipped (addressed in a related issue). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBTM-778) WSDL bindings in XTS code employ the wrong attribute in the binding:operation:input/output declarations

by Andrew Dinn (JIRA)

WSDL bindings in XTS code employ the wrong attribute in the binding:operation:input/output declarations ------------------------------------------------------------------------------------------------------- Key: JBTM-778 URL: https://jira.jboss.org/browse/JBTM-778 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.12.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.13.0 The WSDL for the WSTX service bindings employs the invalid attribute "message" for the binding:operation:input and binding:operation:output elements. The correct attribute name is "name". e.g. in wscoor-activation-binding.wsdl the declaration is <wsdl:binding name="Activation_SOAPBinding" type="wscoor:ActivationPortType"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="CreateCoordinationContextOperation"> <wsdl:input message="wscoor:CreateCoordinationContext"> <soap:body use="literal"/> </wsdl:input> <wsdl:output message="wscoor:CreateCoordinationContextResponse"> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> The correct version should be <wsdl:binding name="Activation_SOAPBinding" type="wscoor:ActivationPortType"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="CreateCoordinationContextOperation"> <wsdl:input name="wscoor:CreateCoordinationContext"> <soap:body use="literal"/> </wsdl:input> <wsdl:output name="wscoor:CreateCoordinationContextResponse"> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> According to a comment in the flle this was a workaround for an error in the com.ibm.wsdl parsing which now appears to have been fixed. The WSDL should be updated accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-678) Enable configuration of XTS using injection of properties into service bean

by Andrew Dinn (JIRA)

Enable configuration of XTS using injection of properties into service bean --------------------------------------------------------------------------- Key: JBTM-678 URL: https://jira.jboss.org/jira/browse/JBTM-678 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.9.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.10.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

15 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-773) Fail to handle Transaction Rollback

by sunny lau (JIRA)

Fail to handle Transaction Rollback ----------------------------------- Key: JBTM-773 URL: https://jira.jboss.org/browse/JBTM-773 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Affects Versions: 5.0.0 Environment: Spring 2.5.5, Oracle Database 10g Reporter: sunny lau Priority: Critical While we want to rollback the transaction due to violate some business rules, Jboss cannot handle the task because of java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.syncrollbackmexception. I did find similar post https://jira.jboss.org/browse/JBTM-663 which already claimed that is a Jboss 4 defect, however, it still appear in Jboss 5.1.0 GA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-772) improve BaseTransactionManagerDelegate.findLock concurrency

by Jonathan Halliday (JIRA)

improve BaseTransactionManagerDelegate.findLock concurrency ----------------------------------------------------------- Key: JBTM-772 URL: https://jira.jboss.org/browse/JBTM-772 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.6.1.CP06, 4.12.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.13.0, 4.6.1.CP07 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2010