July 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-336) crash recovery testing with AS integration

by Jonathan Halliday (JIRA)

crash recovery testing with AS integration ------------------------------------------ Key: JBTM-336 URL: http://jira.jboss.com/jira/browse/JBTM-336 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3.0.BETA2 Reporter: Jonathan Halliday Fix For: 4.4 Current testing of JBossTS is standalone. The JBossAS integration code does not get exercised. This a particularly a problem for specialized crash recovery modules that are used only when running integrated with AS. Work with the AS team to figure out how best to do crash recovery testing for JBossAS. -- 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

13 years, 9 months

2
13
0 / 0

[JBoss JIRA] Updated: (JBTM-44) Transaction bridging

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/browse/JBTM-44?page=com.atlassian.jira.plugin.syst... ] Jonathan Halliday updated JBTM-44: ---------------------------------- Fix Version/s: 4.13.0 (was: 4.12.0) > Transaction bridging > -------------------- > > Key: JBTM-44 > URL: https://jira.jboss.org/browse/JBTM-44 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA, JTS, XTS > Reporter: Mark Little > Assignee: Jonathan Halliday > Priority: Critical > Fix For: 4.13.0 > > Attachments: jbossxts-bridge.zip > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-760) ThreadAction.currentAction uses Exception for branch logic

by Carlo de Wolf (JIRA)

ThreadAction.currentAction uses Exception for branch logic ---------------------------------------------------------- Key: JBTM-760 URL: https://jira.jboss.org/browse/JBTM-760 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.6.1.CP05 Reporter: Carlo de Wolf Priority: Critical Fix For: 4.6.1.CP06 Using exceptions for logic is a performance bottleneck. if (txs != null) { try { return (BasicAction) txs.peek(); } catch (EmptyStackException e) { } } -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-730) JBossTS embedded tools startup fails on EAP5.0.1 CR1

by Ivo Studensky (JIRA)

JBossTS embedded tools startup fails on EAP5.0.1 CR1 ---------------------------------------------------- Key: JBTM-730 URL: https://jira.jboss.org/jira/browse/JBTM-730 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.6.1.CP04 Environment: EAP5.0.1.CR1 Reporter: Ivo Studensky In EAP5.0.1.CR1 the embedded tools fails with the error below. snippet of server.log: 2010-03-12 11:13:00,841 ERROR [STDERR] (Thread-27) java.io.FileNotFoundException: /home/studensky/job/EAP5/5.0.1.cr1/jboss-eap-5.0/jboss-as/server/all/tmp/jboss_tools_tmp/META-INF/MANIFEST.MF (No such file or directory) 2010-03-12 11:13:00,841 ERROR [STDERR] (Thread-27) at java.io.FileOutputStream.open(Native Method) 2010-03-12 11:13:00,841 ERROR [STDERR] (Thread-27) at java.io.FileOutputStream.<init>(FileOutputStream.java:179) 2010-03-12 11:13:00,841 ERROR [STDERR] (Thread-27) at java.io.FileOutputStream.<init>(FileOutputStream.java:131) 2010-03-12 11:13:00,841 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.plugin.ToolPluginInformation.externalizeFile(ToolPluginInformation.java:172) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ToolsClassLoader.processSar(ToolsClassLoader.java:121) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ToolsClassLoader.init(ToolsClassLoader.java:87) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ToolsClassLoader.<init>(ToolsClassLoader.java:68) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ToolsClassLoader.<init>(ToolsClassLoader.java:73) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ArjunaToolsFramework.<init>(ArjunaToolsFramework.java:106) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at org.jboss.jbosstm.tools.embedded.EmbeddedToolsFramework.<init>(EmbeddedToolsFramework.java:37) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at org.jboss.jbosstm.tools.mbean.EmbeddedTools$1.run(EmbeddedTools.java:37) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) Exception in thread "Thread-27" 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) java.lang.RuntimeException: Unable to unpack tools sar: /home/studensky/job/EAP5/5.0.1.cr1/jboss-eap-5.0/jboss-as/server/all/tmp/jboss_tools_tmp/META-INF/MANIFEST.MF (No such file or directory) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ToolsClassLoader.processSar(ToolsClassLoader.java:140) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ToolsClassLoader.init(ToolsClassLoader.java:87) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ToolsClassLoader.<init>(ToolsClassLoader.java:68) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ToolsClassLoader.<init>(ToolsClassLoader.java:73) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at com.arjuna.ats.tools.toolsframework.ArjunaToolsFramework.<init>(ArjunaToolsFramework.java:106) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at org.jboss.jbosstm.tools.embedded.EmbeddedToolsFramework.<init>(EmbeddedToolsFramework.java:37) 2010-03-12 11:13:00,842 ERROR [STDERR] (Thread-27) at org.jboss.jbosstm.tools.mbean.EmbeddedTools$1.run(EmbeddedTools.java:37) -- 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

13 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBTM-757) improve TransactionImple.isAlive performance

by Jonathan Halliday (JIRA)

improve TransactionImple.isAlive performance -------------------------------------------- Key: JBTM-757 URL: https://jira.jboss.org/browse/JBTM-757 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.6.1.CP05, 4.11.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.12.0, 4.6.1.CP06 TransactionImple.isAlive is a performance bottleneck for some app server use cases. See JBPAPP-4598 -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-756) deprecate AppServerJDBCXARecovery

by Jonathan Halliday (JIRA)

deprecate AppServerJDBCXARecovery --------------------------------- Key: JBTM-756 URL: https://jira.jboss.org/browse/JBTM-756 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.11.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.12.0 With the addition of recovery auto registration in the JCA for EAP 5.1 and AS 6.M4, AppServerJDBCXARecovery is no longer required. Indeed its continued use in those server versions may cause premature transaction branch rollback in certain circumstances. In order not to break existing user config files the class should continue to be shipped in the next TS release and then removed in the one after. During the transition period it will be disabled by default, with the option to re-enable by appending ",force=true" to the config string. see also: http://community.jboss.org/thread/92291?start=32&tstart=0 http://community.jboss.org/wiki/XARecoveryinJCA JBAS-8073 JBPAPP-3638 -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Closed: (JBTM-81) Delay start of recovery manager

by Howard Gao (JIRA)

[ https://jira.jboss.org/browse/JBTM-81?page=com.atlassian.jira.plugin.syst... ] Howard Gao closed JBTM-81. -------------------------- Resolution: Done we have reach a solution, close this issue. > Delay start of recovery manager > ------------------------------- > > Key: JBTM-81 > URL: https://jira.jboss.org/browse/JBTM-81 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA, JTS > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Jonathan Halliday > Priority: Minor > Fix For: 4.2.2 > > Attachments: jbossts-properties.xml, jms-ds.xml, server.log > > Time Spent: 1 day > Remaining Estimate: 0 minutes > > Currently the Recovery Manager begins working as soon as JBossAS starts. When the local JTA implementation is used and there is a transaction to recover, we get the following stack trace: > 10:52:35,529 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.restorestate] [com.arjuna.ats.interna\ > l.jta.resources.arjunacore.restorestate] Exception on attempting to restore XAResource > java.io.StreamCorruptedException: unexpected end of block data > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1321) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.restore_state(XAResourceRecord.java:879) > at com.arjuna.ats.arjuna.coordinator.BasicAction.restore_state(BasicAction.java:1410) > at com.arjuna.ats.arjuna.coordinator.BasicAction.activate(BasicAction.java:711) > at com.arjuna.ats.arjuna.coordinator.BasicAction.activate(BasicAction.java:673) > at com.arjuna.ats.arjuna.recovery.RecoverAtomicAction.<init>(RecoverAtomicAction.java:60) > at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.doRecoverTransaction(AtomicActionRecovery\ > Module.java:178) > This is because the rest of the system isn't yet fully initialised. The next periodic run of recovery does not suffer this problem and recovery completes successfully. We should look at delaying the start of the Recovery Manager until JBossAS is fully initialised. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-744) Provide documentation to explain how apps which rely on XTS service should declare their service dependency

by Andrew Dinn (JIRA)

Provide documentation to explain how apps which rely on XTS service should declare their service dependency ----------------------------------------------------------------------------------------------------------- Key: JBTM-744 URL: https://jira.jboss.org/browse/JBTM-744 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.6.1.CP05, 4.11.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.12.0, 4.6.1.CP06 Update the XTS programmer's guide to explain how programmers should make their transactional clients and transactional web services depend on the XTS service. This is necessary to ensure that they do not run before the requisite XTS services are available. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-753) FaultTo ednpoints provided to allow asynchronous soap fault Delivery specify wrong service/endpoint

by Andrew Dinn (JIRA)

FaultTo ednpoints provided to allow asynchronous soap fault Delivery specify wrong service/endpoint --------------------------------------------------------------------------------------------------- Key: JBTM-753 URL: https://jira.jboss.org/browse/JBTM-753 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.11.0 Reporter: Andrew Dinn Assignee: Andrew Dinn The move to CXF 2.2.9 has identified a problem with the mechanism used by the WS-T services to deliver asynchronous soap faults. Each (OneWay) service request includes a FaultTo endpoint which addresses to the pair service/port and this endpoint is used to deliver soap faults reporting any problems which may arise after the one way message has been delivered. So, for example when the Participant service running in a transactional web service's container is sent a Prepare request the FaultTo endpoint addresses the Coordinator service running in the JBossTS/XTS coordinator's container. Soap faults are sent using JaxWS by invoking a proxy cloned from a SoapFaultService instance. All the WS-T endpoints implement the web method declared by this service so they can handle the incoming request. Unfortunately, with CXF 2.2.9 the endpoint now includes metadata identifying the originating service/port used when the endpoint is created. The client validates any proxy create (getPort) request against this metadata. Since the endpoint and create refer to different services getPort fails. The endpoint should either be created with no metadata or should contain metadata for the SoapFaultService and associated port. It may still be appropriate to address the fault back to the WS-T service or it may be necessary to install a distinct endpoint for a SoapFaultService and have it route faults to the relevant WS-T service. Which of these is necessary depends upon the outcome of a related JBossWS issue addressing this problem from the CXF side (JBWS-3069) -- 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, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-762) Errors in XTS documentation

by Mauro Molinari (JIRA)

Errors in XTS documentation --------------------------- Key: JBTM-762 URL: https://jira.jboss.org/browse/JBTM-762 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.11.0 Reporter: Mauro Molinari Priority: Minor While reading the XTS (Web Service Transactions Programmers Guide) documentation I found the following errors: - page 26: the end of the note misses the reference - page 27: the last sentence of the last paragraph in the page (before the note) has a "to" repeated ("repond to to a rollback") - page 34: the last paragraph of "User Transactions" misses the reference - page 36: the last paragraph of "Participants" misses the reference - page 54: the first sentence has a "the" repeated ("system crash on the the participant host(s)") - page 57: under "Recovering Participants at Reboot", after the first code snippet, "register" is mispelled ("as argument to [the?] regsiter and unregister calls") - page 59 and 60: I think the headers should be "WS-BA Participant Crash Recovery" and "WS-BA Participant Crash Recovery APIs" respectively -- 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, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2010