May 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-575) javax.transaction.RollbackException root cause

by Richard Kennard (JIRA)

javax.transaction.RollbackException root cause ---------------------------------------------- Key: JBTM-575 URL: https://jira.jboss.org/jira/browse/JBTM-575 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.7.0 Environment: JBoss 5.1.0.GA Reporter: Richard Kennard In JBoss 4.2.3.GA and previous releases, when a transaction rolled back the RollbackException included the root cause of the exception. This enhancement was implemented in response to JBAS-4238 and JBTM-66. However, in JBoss 5.1.0.GA this enhancement has been lost in some scenarios. This does not affect manual debugging (the root cause is still logged higher up in the logs), but makes it difficult for application code that relies on being able to unwrap the RollbackException to determine its root cause and therefore take appropriate action. -- 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, 6 months

8
36
0 / 0

[JBoss JIRA] Created: (JBTM-719) Create an RHQ plugin to replace the functionality provied by embedded tools

by Michael Musgrove (JIRA)

Create an RHQ plugin to replace the functionality provied by embedded tools --------------------------------------------------------------------------- Key: JBTM-719 URL: https://jira.jboss.org/jira/browse/JBTM-719 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.10.0 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.11.0 The embedded tools are currently delivered as a swing application. This does not fit with the requirement for managing JBoss via RHQ so there is a need to replace the current tool with an RHQ plugin. Such a plugin will work with both JOPR and JON. Similar functionality, with the exception of graphing tools, should also be available for standalone JBossTS via jconsole. -- 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, 7 months

1
8
0 / 0

[JBoss JIRA] Created: (JBTM-619) Cannot enlist two Oracle XAConnection resources in one transaction

by Wade Poziombka (JIRA)

Cannot enlist two Oracle XAConnection resources in one transaction ------------------------------------------------------------------ Key: JBTM-619 URL: https://jira.jboss.org/jira/browse/JBTM-619 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.7.0 Environment: Windows and Linux. Reporter: Wade Poziombka An attempt to enlist two Oracle connections causes the second enlistResource to fail with an exception similar to: oracle.jdbc.xa.OracleXAException at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:938) at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:244) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:902) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:513) Note the line number changes a bit depending on version of Oracle JDBC etc. However, the affect is always the same. There are others who noted this problem on the forum with no resolution or reply (except my own concurring with the observation). In particular two connections to same server using different user id's and passwords. I will test whether two completely separate oracle instances have this issue and update the bug. -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-443) check LastResource logging and recovery

by Jonathan Halliday (JIRA)

check LastResource logging and recovery --------------------------------------- Key: JBTM-443 URL: https://jira.jboss.org/jira/browse/JBTM-443 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation, Recovery Affects Versions: 4.4.0.GA Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.6 Where transactions contain LastResource, they may not be fully recoverable. Check if LastResource records are written to the log and if so, what happens to them during recovery. Optimise the case where a tx contains multiple last resources, as we need to write a log for such a tx only if it also contains real resources. The case where the tx only has a single resource enlisted is irrelevant as the onePhaseCommit optimization already skips logging. -- 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, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-284) Make sure distributed transaction example within JBossAS is clearly illustrated

by Mark Little (JIRA)

Make sure distributed transaction example within JBossAS is clearly illustrated ------------------------------------------------------------------------------- Key: JBTM-284 URL: http://jira.jboss.com/jira/browse/JBTM-284 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, Documentation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Fix For: 4.4 MR1 Will need to remember to use the JBossTS rmi-iiop tool (rmic) because OTS 1.1 should only propagate transactions to TransactionalObjects and no Java entites will ever qualify. -- 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, 10 months

3
11
0 / 0

[JBoss JIRA] Created: (JBTM-411) Other implementations for getpid

by Mark Little (JIRA)

Other implementations for getpid -------------------------------- Key: JBTM-411 URL: https://jira.jboss.org/jira/browse/JBTM-411 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: future VirtualMachine (JDK 6) JBoss Web ... If native is loaded then org.apache.tomcat.jni.Stdlib.getpid() or org.apache.tomcat.jni.Stdlib.getppid() for a parent process of jvm See the Stdlib.java for docs -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-573) Manually prune entries from logs

by Mark Little (JIRA)

Manually prune entries from logs -------------------------------- Key: JBTM-573 URL: https://jira.jboss.org/jira/browse/JBTM-573 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.0 Provide a command-line tool to allow entries in logs to be removed. Needs further thought. -- 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, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-518) Provide explicit ../lib/arjuna_wst1_0.jar, so WS-BusinessActivity Framework works "out of the box" with JBoss 5.00GA

by BEN COTTON (JIRA)

Provide explicit ../lib/arjuna_wst1_0.jar, so WS-BusinessActivity Framework works "out of the box" with JBoss 5.00GA --------------------------------------------------------------------------------------------------------------------- Key: JBTM-518 URL: https://jira.jboss.org/jira/browse/JBTM-518 Project: JBoss Transaction Manager Issue Type: Support Patch Security Level: Public (Everyone can see) Environment: software platform Reporter: BEN COTTON The current JBoss WS-BusinessActivity Framework 0.2.1 code (both demos and txbridge) currently imports the com.arjuna.wst.* and com.arjuna.mw.wst.* class libraries. These libraries are WST 1.0 compliant and will not work "out of the box" with JBoss 5.00GA (which requires WST 1.1 compliance). This patch provides and explicit https://svn.jboss.org/repos/labs/labs/jbosstm/workspace/bencotton/BAFRAME... so that the BA Framework (both demos and txbridge) will work "out of the box" with JBoss 5.00GA. Another JIRA will document patching the org.jboss.ba.demo.* and org.jboss.txbridge.* Java source code to explicitly import WST 1.1 classes. -- 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, 11 months

4
10
0 / 0

[JBoss JIRA] Created: (JBTM-716) Tooling code coverage

by Mark Little (JIRA)

Tooling code coverage --------------------- Key: JBTM-716 URL: https://jira.jboss.org/jira/browse/JBTM-716 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing, Tooling, Transaction Core Reporter: Mark Little Assignee: Michael Musgrove Fix For: 4.11.0 Write coverage for everything under the com.arjuna,.ats.arjuna.tools, as these are now the only classes in the arjuna module that have zero coverage. -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-599) Synchronization problem in CacheStore

by Andrew Dinn (JIRA)

Synchronization problem in CacheStore ------------------------------------- Key: JBTM-599 URL: https://jira.jboss.org/jira/browse/JBTM-599 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andrew Dinn This bug manifests occasionally when running the CachedTest. The AsyncStore thread suspends inside its run method on a (120 sec) timed wait because the cache is not full. When I managed to catch this case in the debugger I found that there were many writer threads (~30) suspended inside addWork in an untimed wait on the overflow lock. So, these writing threads make no progress for 120 seconds. The AsyncStore thread does notify the object on which the writers are waiting but there is clearly a window where the writers can go to sleep while the cache is full and not get notified when the AsyncStore thread has emptied it. -- 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, 11 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2010