December 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1007) Review annotation names offered by the TXFramework

by Paul Robinson (Created) (JIRA)

Review annotation names offered by the TXFramework -------------------------------------------------- Key: JBTM-1007 URL: https://issues.jboss.org/browse/JBTM-1007 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TXFramework Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.Final Essentially, we need to ensure that they provide a good description to the user of what they do. -- 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

11 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-223) Check WL-to-JBossTS interoperability (via JTS).

by Mark Little (JIRA)

Check WL-to-JBossTS interoperability (via JTS). ----------------------------------------------- Key: JBTM-223 URL: http://jira.jboss.com/jira/browse/JBTM-223 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: 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

11 years, 11 months

2
4
0 / 0

[JBoss JIRA] (JBTM-981) Annotation support for transaction bridging

by Paul Robinson (Created) (JIRA)

Annotation support for transaction bridging ------------------------------------------- Key: JBTM-981 URL: https://issues.jboss.org/browse/JBTM-981 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 Currently the developer specifies the type of transaction that the service and any lifecycle callbacks expect to participate in. For example, via @WSBA or @RESTJDI class level annotation. However, the participation requirements for these protocols is very similar. It would be better if the developer could simply specify that the service can participate in any forward compensation style transaction (such as REST-JDI or WS-BA) using a @BA annotation. The type of transaction is determined by the inflowed TX context. To take this a step further, by leaving off the transaction type annotation altogether, the service could participate in any transaction type. Of course, this would require a mix of ACID and forward compensation lifecycle callbacks to be present. Again, the inflow TX context would decide the actual TX type used. -- 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

11 years, 11 months

3
10
0 / 0

[JBoss JIRA] (JBTM-980) Move to generic participants

by Paul Robinson (Created) (JIRA)

Move to generic participants ---------------------------- Key: JBTM-980 URL: https://issues.jboss.org/browse/JBTM-980 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 -- 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

11 years, 12 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue

by Howard Gao (JIRA)

Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue ------------------------------------------------------------------------------ Key: JBTM-649 URL: https://jira.jboss.org/jira/browse/JBTM-649 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6.1 Reporter: Howard Gao Fix For: 4.6.1.CP04 After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test starts to fail. The scenario is: 1. We have two XAResources res1 and res2. Both are enlisted in a Transaction. 2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2). 3. delist res1 and res2 and commit the transaction. 4. During the commit process, we simulate a failure on res2.commit() so that the res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic state. 5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and recover the transaction. So we expect that the two sent messages will be received by the receiver. To allow the recovery to happen we give a 60 second timeout to receive the second message. But the result is the first message is received but the second message isn't. We know that it is not JTA compliant. But some users may still rely on the old behavior to work. Suggestion: a system property can be provided to enable the old behavior if specified by user. -- 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

12 years

5
11
0 / 0

[JBoss JIRA] Created: (JBTM-622) Support for crash recovery of tx-inflow with multiple resource managers

by Toshiya Kobayashi (JIRA)

Support for crash recovery of tx-inflow with multiple resource managers ----------------------------------------------------------------------- Key: JBTM-622 URL: https://jira.jboss.org/jira/browse/JBTM-622 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA, Recovery, Transaction Core Affects Versions: 4.7.0 Reporter: Toshiya Kobayashi JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs. In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid. -- 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

12 years

5
7
0 / 0

[JBoss JIRA] Created: (JBTM-831) performance tweaks

by Jonathan Halliday (JIRA)

performance tweaks ------------------ Key: JBTM-831 URL: https://issues.jboss.org/browse/JBTM-831 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Jonathan Halliday Assignee: Jonathan Halliday assorted performance tweaks -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
7
0 / 0

[JBoss JIRA] Created: (JBTM-849) registerSynchronization fails with from status message

by Carlo de Wolf (JIRA)

registerSynchronization fails with from status message ------------------------------------------------------ Key: JBTM-849 URL: https://issues.jboss.org/browse/JBTM-849 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.15.1 Environment: https://github.com/jbossejb3/jboss-as/tree/991e836c1bcb6b471010c5930fc3f5... Reporter: Carlo de Wolf Attachments: JBTM-849-stracktrace.txt registerSynchronization is called from within a beforeCompletion of another Synchronization. I would expect the status to be PREPARING (or anything but RUNNING). {noformat} java.lang.IllegalStateException: Synchronizations are not allowed! Transaction status isActionStatus.RUNNING at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronizationImple(TransactionImple.java:367) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronization(TransactionImple.java:344) at org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.getRegisteredSynchronizer(TransactionSynchronizer.java:198) at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:210) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:407) ... 104 more {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
14
0 / 0

[JBoss JIRA] Created: (JBTM-830) Wrong character encoding in HTML rendering of documentation

by Sanne Grinovero (JIRA)

Wrong character encoding in HTML rendering of documentation ----------------------------------------------------------- Key: JBTM-830 URL: https://issues.jboss.org/browse/JBTM-830 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Sanne Grinovero Priority: Optional Documents as http://docs.jboss.org/jbosstm/docs/4.2.1/manuals/html/jts/ProgrammersGuid... (but not limited to) are rendered with � symbols -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-259) Make sure the build system uses the version number

by Mark Little (JIRA)

Make sure the build system uses the version number -------------------------------------------------- Key: JBTM-259 URL: http://jira.jboss.com/jira/browse/JBTM-259 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Release Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Within the code we have some Info.java classes that are supposed to be able to give back important build-time information. Looks like that is being lost or incomplete these days: <module-info name="arjuna"><source-identifier>unknown</source-identifier><build-information>JBoss Inc. [kevin] (Linux 2.6.17-1.2157_FC5)</build-information><version>unknown</version><date>2006/Aug/04 15:26</date><notes></notes><configuration><properties-file dir=".">jbossjta-properties.xml</properties-file><object-store-root>/Users/bas/Documents/workspace/adhoc/ObjectStore</object-store-root></configuration></module-info> -- 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

12 years

3
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2011