February 2012 - jbossts-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (JBTM-855) Create an example showing integration with Tomcat and Spring

by Tom Jenkinson (JIRA)

Create an example showing integration with Tomcat and Spring ------------------------------------------------------------ Key: JBTM-855 URL: https://issues.jboss.org/browse/JBTM-855 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Simple example showing TS in use by tomcat and spring -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
4
0 / 0

[JBoss JIRA] (JBTM-978) Support REST-AT protocol in the TXFramework

by Paul Robinson (Created) (JIRA)

Support REST-AT protocol in the TXFramework ------------------------------------------- Key: JBTM-978 URL: https://issues.jboss.org/browse/JBTM-978 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 class level annotation allows the class which is the target of lifecycle handler callbacks to be specified. {code} @Retention(RetentionPolicy.RUNTIME) @Target(ElementType.TYPE) public @interface ParticipantService { public Class lifecycleClass() default Default.class; } {code} This field may be overridden in the ServiceRequest annotation itself. If the value of this field is Default.class then the ParticipantService class is used as the default class to resolve POJO lifecycle methods. {code} @Retention(RetentionPolicy.RUNTIME) @Target({ElementType.METHOD, ElementType.TYPE}) public @interface ServiceRequest { public Class lifecycleClass() default Default.class; } {code} If the lifecycleClass attribute is not specified in either place, the class containing the @ServiceInvocation is assumed to also contain the associated Lifecycle Handler methods. -- 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

12 years

3
13
0 / 0

[JBoss JIRA] Created: (JBTM-865) Make sure REST-AT is covered in docbook

by Michael Musgrove (JIRA)

Make sure REST-AT is covered in docbook --------------------------------------- Key: JBTM-865 URL: https://issues.jboss.org/browse/JBTM-865 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.0.M2 Include a section on REST-AT in docbook -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
1
0 / 0

[JBoss JIRA] (JBTM-1016) Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1016: ----------------------------------- Summary: Run bmcheck.sh regularly to spot inconsistencies between byteman scripts and the code Key: JBTM-1016 URL: https://issues.jboss.org/browse/JBTM-1016 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 I've found many bugs in the XTS crash recovery tests that where due to changes being made to the XTS code without updating the byteman scripts. The problem is that these inconsistencies often go unnoticed when the tests run, until you notice a failure in the test. A simple solution would be to run bmcheck.sh over all our byteman scripts as part of CI. -- 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

12 years, 1 month

3
19
0 / 0

[JBoss JIRA] (JBTM-970) Allow a ServiceRequest to be annotated as read only

by Paul Robinson (Created) (JIRA)

Allow a ServiceRequest to be annotated as read only --------------------------------------------------- Key: JBTM-970 URL: https://issues.jboss.org/browse/JBTM-970 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 This class level annotation allows the class which is the target of lifecycle handler callbacks to be specified. {code} @Retention(RetentionPolicy.RUNTIME) @Target(ElementType.TYPE) public @interface ParticipantService { public Class lifecycleClass() default Default.class; } {code} This field may be overridden in the ServiceRequest annotation itself. If the value of this field is Default.class then the ParticipantService class is used as the default class to resolve POJO lifecycle methods. {code} @Retention(RetentionPolicy.RUNTIME) @Target({ElementType.METHOD, ElementType.TYPE}) public @interface ServiceRequest { public Class lifecycleClass() default Default.class; } {code} If the lifecycleClass attribute is not specified in either place, the class containing the @ServiceInvocation is assumed to also contain the associated Lifecycle Handler methods. -- 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

12 years, 1 month

3
6
0 / 0

[JBoss JIRA] (JBTM-985) Add WS-TX WS-Policy assertions to generated WSDL

by Paul Robinson (Created) (JIRA)

Add WS-TX WS-Policy assertions to generated WSDL ------------------------------------------------- Key: JBTM-985 URL: https://issues.jboss.org/browse/JBTM-985 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 See the "Policy Assertions" section of the WS-BA and WS-AT specification for what this should implement. Ideally this feature would be turned on/off via an annotation, however we should take a look to see if WS-Policy mandates a particular method. -- 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

12 years, 1 month

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2012