November 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-803) The WSDLs of the WS-C services are present both in ws-c11.jar e wstx.jar

by Mauro Molinari (JIRA)

The WSDLs of the WS-C services are present both in ws-c11.jar e wstx.jar ------------------------------------------------------------------------ Key: JBTM-803 URL: https://jira.jboss.org/browse/JBTM-803 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.13.0 Reporter: Mauro Molinari Priority: Minor The WSDLs of the WS-C services (wsat-coordinator-binding and wscoor-activation-binding) are located in two places, in ws-c11.jar but also in wstx.jar. They have been put in the ws-c11 jar so the coordinator service classes (also in this jar) can find them. But also in wstx11.jar so the client classes (also in wstx11.jar) can find them. However, since all the XTS JARs at the moment are needed on each part of the system (Client, Coordinator, Participant), it's useless (and confusing) to have these WSDLs in both places. I personally suggest to keep the ones in ws-c11.jar, so that they are easily recognizable as the counterparts of the WS-T services WSDLs in ws-t11.jar. -- 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

13 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-799) Provide a way to configure the WS-C and WS-T service endpoint URLs/paths

by Mauro Molinari (JIRA)

Provide a way to configure the WS-C and WS-T service endpoint URLs/paths ------------------------------------------------------------------------ Key: JBTM-799 URL: https://jira.jboss.org/browse/JBTM-799 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.13.0 Reporter: Mauro Molinari As of now, the paths to get to the exposed service endpoints of the different WS-C and WS-T services is hard coded, based on the JBossAS/JBossWS convention of using the path <war-name>/<service-name> (where <war-name> is the name of the war containing the service). For instance, the ActivationService URL is expected to be http://bindAddress:bindPort/ws-c11/ActivationService. However, if you want to deploy to another environment (for instance: your own web application, running on Tomcat with CXF), you may want (or you may even be forced) to change the endpoint URLs as you like. Since with CXF (and, in general, with JAX-WS) you are free to expose a webservice with the URL you prefer, the best would be to make XTS configurable in this sense. Every component (Client, Participant, Coordinator) should be improved to let the user specify the URL at which he wants to expose the corresponding webservices (i.e.: for WS-AT, it's the CompletionInitiator on the Client, the Participant on the Participant, the Coordinator, CompletionCoordinator, Activation and Registration on the Coordinator). More precisely, since the bindAddress and bindPort are already settable, just the path part should be made configurable. -- 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

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-800) Recovery manager not initialised when deploying just the Coordinator

by Mauro Molinari (JIRA)

Recovery manager not initialised when deploying just the Coordinator -------------------------------------------------------------------- Key: JBTM-800 URL: https://jira.jboss.org/browse/JBTM-800 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.13.0 Reporter: Mauro Molinari If you deploy just the Coordinator component of XTS and you follow the configuration guidelines, you may be providing just the following recovery manager configuration entries in xts-properties.xml: <entry key="org.jboss.jbossts.xts.recovery.coordinatorRecoveryModule1">org.jboss.jbossts.xts.recovery.coordinator.at.ATCoordinatorRecoveryModule</entry> <entry key="org.jboss.jbossts.xts.recovery.coordinatorRecoveryModule2">org.jboss.jbossts.xts.recovery.coordinator.at.SubordinateATCoordinatorRecoveryModule</entry> However, in this way, after the Coordinator has started, you get the following NullPointerException: Exception in thread "Periodic Recovery" java.lang.NullPointerException at org.jboss.jbossts.xts.recovery.coordinator.at.ATCoordinatorRecoveryModule.processTransactionsStatus(ATCoordinatorRecoveryModule.java:280) at org.jboss.jbossts.xts.recovery.coordinator.at.ATCoordinatorRecoveryModule.periodicWorkSecondPass(ATCoordinatorRecoveryModule.java:121) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) This is because the recovery manager is currently initialized by the ATParticipantRecoveryModule, which is expected to be made available just on the Participant component. -- 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

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-798) Package the XTS service and initialisation classes in a JAR, rather than in the SAR

by Mauro Molinari (JIRA)

Package the XTS service and initialisation classes in a JAR, rather than in the SAR ----------------------------------------------------------------------------------- Key: JBTM-798 URL: https://jira.jboss.org/browse/JBTM-798 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.13.0 Reporter: Mauro Molinari As of now, the binary distribution of XTS provides the following classes in jbossxts.sar: org.jboss.jbossts.XTSService org.jboss.jbossts.XTSServiceMBean org.jboss.jbossts.initialisation.* org.jboss.jbossts.logging.* As discussed in the forum, in order to make XTS easily deployable outside JBossAS it would be convenient to move these classes into one of the already existing JARs (jbossxts-api.jar?) or in a new one (jbossxts-service.jar?). Then, this JAR should be included in the SAR, if it's not already. In this way, the SAR would become just a facility to deploy XTS in JBossAS, but the user could deploy it also on another application server (Tomcat for instance) just by deploying the XTS JARs and providing the necessary configuration wiring. -- 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

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-797) orb setup drops exceptions

by Jonathan Halliday (JIRA)

orb setup drops exceptions -------------------------- Key: JBTM-797 URL: https://jira.jboss.org/browse/JBTM-797 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.13.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.14.0 When the specified orb (actually OA) port is in use the orb setup will fail, leave the orb/oa in an unusable state, print a warning but not be detectable or recoverable programatically. This sucks for the test suite, since it's not uncommon for rec mgr startup to fail due to the O/S not having recycled ports from a previous test process. This situation should be detectable and retryable. -- 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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-813) Convert and merge Installation and Administration Guides for ArjunaCore, JBossJTA, JBossJTS, JBossXTS

by Misty Stanley-Jones (JIRA)

Convert and merge Installation and Administration Guides for ArjunaCore, JBossJTA, JBossJTS, JBossXTS ----------------------------------------------------------------------------------------------------- Key: JBTM-813 URL: https://jira.jboss.org/browse/JBTM-813 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.13.0 Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 4.14.0 For each of ArjunaCore, ArjunaJTA, ArjunaJTS, ArjunaXTS, merge the Installation and Administration guides, and convert to Docbook. -- 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

14 years

1
7
0 / 0

[JBoss JIRA] Created: (JBTM-805) Convert JTA Development Guide to docbook

by Misty Stanley-Jones (JIRA)

Convert JTA Development Guide to docbook ---------------------------------------- Key: JBTM-805 URL: https://jira.jboss.org/browse/JBTM-805 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 4.14.0 -- 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

14 years

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-815) JBoss TransactionManager throws a XAException exception with error code XAER_PROTO error while trying to commit a transaction.

by Tom Ross (JIRA)

JBoss TransactionManager throws a XAException exception with error code XAER_PROTO error while trying to commit a transaction. ------------------------------------------------------------------------------------------------------------------------------ Key: JBTM-815 URL: https://jira.jboss.org/browse/JBTM-815 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss EAP 4.3.GA.CP08 Reporter: Tom Ross It looks like the problem is in org.jboss.tm.TransactionImpl.commit(). This method checks the transaction's status, if it is STATUS_ACTIVE then it, in the case of an XA transaction, prepares the resources (sets status to STATUS_PREPARED) and then commits the resources. During the commit for each of the resources the status is STATUS_COMMITTING. It appears a time-out happens exactly at this point. As the log shows: WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl[FormatId=257, GlobalId=doron/220, BranchQual=, localId=220] timed out. status=STATUS_COMMITING On a transaction timeout when the transaction status is STATUS_COMMITING, org.jboss.tm.TransactionImpl.timedOut(Timeout timeout) sets the status to STATUS_MARKED_ROLLBACK. However, see the comment in the code: 271 case Status.STATUS_COMMITTING: 272 // This is _very_ bad: 273 // We are in the second commit phase, and have decided 274 // to commit, but now we get a timeout and should rollback. 275 // So we end up with a mixed decision. 276 gotHeuristic(null, XAException.XA_HEURMIX); 277 status = Status.STATUS_MARKED_ROLLBACK; 278 return; // commit will fail This is "_very_ bad" because some of the resources may have already actually committed. It appears that is exactly what happened in this customer's case. Therefore, when org.jboss.tm.TransactionImpl.commit() checks the status again after the commit attempt and sees STATUS_MARKED_ROLLBACK it tries to rollback the resources. However, this resource has already committed and therefore doesn't recognize the Xid that it's given: WARN [org.jboss.tm.TransactionImpl] XAException: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=doron/220, BranchQual=, localId=220] errorCode=XAER_PROTO org.jboss.resource.connectionmanager.JBossLocalXAException: wrong xid in rollback: expected: null, got: XidImpl[FormatId=257, GlobalId=doron/220, BranchQual=1, localId=220] at org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.rollback(TxConnectionManager.java:1023) -- 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

14 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-77) Make UserTransaction Serializable/Referenceable

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/browse/JBTM-77?page=com.atlassian.jira.plugin.syst... ] Jonathan Halliday closed JBTM-77. --------------------------------- Resolution: Done > Make UserTransaction Serializable/Referenceable > ----------------------------------------------- > > Key: JBTM-77 > URL: https://jira.jboss.org/browse/JBTM-77 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Jonathan Halliday > Priority: Minor > Fix For: 4.14.0 > > > JTA says we should be. Doesn't affect embedding in AS, but for strict compliane we should update the implementation. -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-437) Make sure JBossTS configuration in EAP has recovery set up by default

by Mark Little (JIRA)

Make sure JBossTS configuration in EAP has recovery set up by default --------------------------------------------------------------------- Key: JBTM-437 URL: https://jira.jboss.org/jira/browse/JBTM-437 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration, Recovery Reporter: Mark Little Assignee: Mark Little Fix For: 4.5 -- 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, 1 month

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2010