October 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-917) Create a XAResourceOrphanFilter to recover subordinate transactions

by Tom Jenkinson (Created) (JIRA)

Create a XAResourceOrphanFilter to recover subordinate transactions ------------------------------------------------------------------- Key: JBTM-917 URL: https://issues.jboss.org/browse/JBTM-917 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
4
0 / 0

[JBoss JIRA] (JBTM-916) Convert XID to support encoding the node name in the branch qualifier for subordinate transactions and include the parent node name in the bqual also to assist with recovery

by Tom Jenkinson (Created) (JIRA)

Convert XID to support encoding the node name in the branch qualifier for subordinate transactions and include the parent node name in the bqual also to assist with recovery ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-916 URL: https://issues.jboss.org/browse/JBTM-916 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-909) Add an API hook for deferred afterCompletion

by David Lloyd (JIRA)

Add an API hook for deferred afterCompletion -------------------------------------------- Key: JBTM-909 URL: https://issues.jboss.org/browse/JBTM-909 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: Tom Jenkinson Fix For: 4.15.x Provide an API for deferring afterCompletion callback. This comes in two parts: # A flag to pass to the commit method indicating that afterCompletion should be deferred # A separate method indicating that afterCompletion callbacks should proceed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
5
0 / 0

[JBoss JIRA] (JBTM-933) Compress the EIS name in the bqual

by Tom Jenkinson (Created) (JIRA)

Compress the EIS name in the bqual ---------------------------------- Key: JBTM-933 URL: https://issues.jboss.org/browse/JBTM-933 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Fix For: 4.15.4 Current most of the bqual is consumed by the EIS name (stored uncompressed) leaving little space for future enhancements. This was OK before, but there is potentially a requirement to use some of the bqual to store a node identifier (which, in the gtrid is able to be 36 bytes long). Jonathan has pointed out that we can maintain a file somewhere where the user passes us an EIS name of say "foo" and we can add this to the file as integer 1, and so on. This file can be reloaded at startup into a hashmap so that we can still print out the real EIS name even though the XID bqual would only consume 4 bytes now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
6
0 / 0

[JBoss JIRA] Created: (JBTM-396) Provide one-phase commit optimization

by Mark Little (JIRA)

Provide one-phase commit optimization ------------------------------------- Key: JBTM-396 URL: https://jira.jboss.org/jira/browse/JBTM-396 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.4.CR1 Reporter: Mark Little Assignee: Andrew Dinn WS-AT does not support 1PC optimization. WS-ACID from WS-CAF does. It would be good to provide a configurable option for WS-AT users to enable 1PC optimization. This obviously breaks interoperability, which is why the default should be to have it disabled. -- 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, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBTM-713) Provide a general annotation-based Transaction Framework based on the BA Framework prototype

by Andrew Dinn (JIRA)

Provide a general annotation-based Transaction Framework based on the BA Framework prototype -------------------------------------------------------------------------------------------- Key: JBTM-713 URL: https://jira.jboss.org/jira/browse/JBTM-713 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration, Common, Demonstrator, Documentation, Recovery, Transaction Core, TxBridge, XTS Affects Versions: 4.9.0 Reporter: Andrew Dinn Assignee: Andrew Dinn The prototype BA Transaction Management Framework has been useful in clarifying how JBossTS can simplify some of the tasks developers must perform when designing and implementing of transactional services. However, the prototype suffers from various limitations, both in its definition and its implementation. An alternative framework, preferably one which can embrace multiple transaction protocols (and not just Web Service transactions), needs to be defined, developed and then incorporated into the TS release. -- 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, 4 months

6
11
0 / 0

[JBoss JIRA] Created: (JBTM-451) Check XTS default timeout

by Mark Little (JIRA)

Check XTS default timeout ------------------------- Key: JBTM-451 URL: https://jira.jboss.org/jira/browse/JBTM-451 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation 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

14 years, 4 months

6
13
0 / 0

[JBoss JIRA] Created: (JBTM-861) XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080

by Andrew Dinn (JIRA)

XTS AS7 configuration is incomplete and inadequate for binding/web port other than localhost:8080 ------------------------------------------------------------------------------------------------- Key: JBTM-861 URL: https://issues.jboss.org/browse/JBTM-861 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.15.2 Reporter: Andrew Dinn Fix For: 4.15.3, 5.0.0.M1 The current integration of XTS into AS7 as an AS7 extension allows optional configuration of the coordinator URL from the <xts/> element in the AS7 standalone configuration file. No other configuration options are currently supported. This is inadequate on two counts. Firstly, if no URL is provided the coordinator address is located via localhost:8080 (or localhost:8443 if an https scheme is employed). Similarly, the deployed web services are assumed to have localhost:8080 addresses. The XTS extension ought to depend on JBoss web and use the bind address and ports (non-secure and secure) JBoss web employs. Secondly, XTS ought to support more precise configuration. IN particular, it ought to be possible to enable or disable deployment of coordinator, participant or client services independently and also to choose whether to deploy WS-AT or WS-BA services or both. This requires selectively deploying only the required web service endpoints, selectively executing the required initialization routines and selectively loading the required high level service implementations and context factory implementations. The XTS implementation has already been factored so as to to support such discriminated bootstrapping. So this task only requires modifying the AS7 extension code to manage the relevant configuration information and install the relevant values into the XTS environment configuration beans before starting the XTS service. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
19
0 / 0

[JBoss JIRA] Created: (JBTM-912) jbossts-xts-testsuite-eap5.1.x-ci fails due to "cannot find symbol: AddressingProperties"

by Paul Robinson (JIRA)

jbossts-xts-testsuite-eap5.1.x-ci fails due to "cannot find symbol: AddressingProperties" ----------------------------------------------------------------------------------------- Key: JBTM-912 URL: https://issues.jboss.org/browse/JBTM-912 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.6.1.CP13 See https://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-xts-testsuite... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
4
0 / 0

[JBoss JIRA] (JBTM-938) java.lang.IllegalStateException occurs in afterCompletion during commit on inbound bridge at txbridge demo app

by Ivo Studensky (Created) (JIRA)

java.lang.IllegalStateException occurs in afterCompletion during commit on inbound bridge at txbridge demo app -------------------------------------------------------------------------------------------------------------- Key: JBTM-938 URL: https://issues.jboss.org/browse/JBTM-938 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Demonstrator, TxBridge Affects Versions: 4.15.3 Reporter: Ivo Studensky Assignee: Jonathan Halliday The txbridge demo app was tested with the latest AS7 build (7.1.0.Alpha2-SNAPSHOT). The application successfully ended and said 'Transaction finished OK' with WS-AT tx parent type option. However, a weird exception occured in the server log during the demo app run. The java.lang.IllegalStateException was thrown from afterCompletion method during the commit on the inbound bridge. Another issue is that the demo app was not able to identify this failure and said that everything was finished successfully. See the following stacktrace from the server log: {noformat} 15:23:22,651 WARN [com.arjuna.ats.jta] (TaskWorker-3) ARJUNA16029: SynchronizationImple.afterCompletion - failed for org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization@7ae73995 with exception: java.lang.IllegalStateException at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.getTransactionImple(TransactionSynchronizationRegistryImple.java:225) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.putResource(TransactionSynchronizationRegistryImple.java:103) [jbossjts-4.15.3.Final.jar:] at org.jboss.as.jpa.transaction.TransactionUtil.putEntityManagerInTransactionRegistry(TransactionUtil.java:195) at org.jboss.as.jpa.transaction.TransactionUtil.access$100(TransactionUtil.java:48) at org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization.afterCompletion(TransactionUtil.java:220) at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:117) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:403) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:335) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.SubordinateAtomicAction.doCommit(SubordinateAtomicAction.java:176) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple.doCommit(TransactionImple.java:158) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.commit(XATerminatorImple.java:87) [jbossjts-4.15.3.Final.jar:] at org.jboss.jbossts.txbridge.inbound.BridgeDurableParticipant.commit(BridgeDurableParticipant.java:204) [jbosstxbridge-4.15.3.Final.jar:] at com.arjuna.wst11.messaging.engines.ParticipantEngine.executeCommit(ParticipantEngine.java:577) [jbossxts-4.15.3.Final.jar:] at com.arjuna.wst11.messaging.engines.ParticipantEngine.commit(ParticipantEngine.java:149) [jbossxts-4.15.3.Final.jar:] at com.arjuna.wst11.messaging.ParticipantProcessorImpl.commit(ParticipantProcessorImpl.java:99) [jbossxts-4.15.3.Final.jar:] at com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl$2.executeTask(ParticipantPortTypeImpl.java:84) [jbossxts-4.15.3.Final.jar:] at com.arjuna.services.framework.task.TaskWorker.run(TaskWorker.java:63) [jbossxts-4.15.3.Final.jar:] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
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 October 2011