September 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-536) JTS compilation with IBM jdk1.5 fails due to "Fatal Error: Unable to find package java.lang"

by Ivo Studensky (JIRA)

JTS compilation with IBM jdk1.5 fails due to "Fatal Error: Unable to find package java.lang" -------------------------------------------------------------------------------------------- Key: JBTM-536 URL: https://jira.jboss.org/jira/browse/JBTM-536 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Environment: IBM JDK 1.5, Apache Ant 1.6.5, Linux Reporter: Ivo Studensky Fix For: 4.6.1 Compiler cannot find java.lang package in case of compiling with IBM JDK 1.5. See the snippet of compilation output: ... [java] com.hp.mwlabs.orbportability.orbspecific.jacorb.compile: [java] [echo] Performing JacORB IDL compile [java] [classpath-builder] Property 'build.jacorb.classpath' set to classpath ... [java] [echo] Performing JacORB orb specific compile [java] [javac] Compiling 11 source files to /mnt/hudson_workspace/workspace/jbossts-testsuite-matrix/jdk/ibm15/label/RHEL4_x86/trunk/ArjunaJTS/orbportability/orbspecific-build [java] [javac] Fatal Error: Unable to find package java.lang in classpath or bootclasspath -- 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, 5 months

2
8
0 / 0

[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, 7 months

8
36
0 / 0

[JBoss JIRA] Created: (JBTM-795) add i18n tooling to build

by Jonathan Halliday (JIRA)

add i18n tooling to build ------------------------- Key: JBTM-795 URL: https://jira.jboss.org/browse/JBTM-795 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common, Tooling Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.14.0 Following the move from CLF to jboss-logging (JBTM-750) the i18n system uses an approach consisting of an interface with annotations containing the log message text, plus an implementation class that should generated automatically from those annotations. However the tooling is not ready yet, so the impls have to be done manually for now, which is a pain. Migrate to autogeneration when possible. http://community.jboss.org/wiki/LoggingI18NToolingTechnicalRequirements -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-782) add HornetQ journal based ObjectStore

by Jonathan Halliday (JIRA)

add HornetQ journal based ObjectStore ------------------------------------- Key: JBTM-782 URL: https://jira.jboss.org/browse/JBTM-782 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.12.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.13.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

13 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-775) Property files within jars not being detected

by Galder Zamarreno (JIRA)

Property files within jars not being detected --------------------------------------------- Key: JBTM-775 URL: https://jira.jboss.org/browse/JBTM-775 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.9.0 Reporter: Galder Zamarreno We, Infinispan, has added a jbossts-properties.xml to src/test/resources to make it easier for developers to enable debug logging for JBoss TS code. Now, when the test jar is filled, this file is included, but any client code using this jar can't startup and instead throws errors like this: Caused by: java.lang.ExceptionInInitializerError at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:97) at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:76) ... 65 more Caused by: java.lang.RuntimeException: java.lang.RuntimeException: invalid property file file:/home/sanne/.m2/repository/org/infinispan/infinispan-core/4.1.0-SNAPSHOT/infinispan-core-4.1.0-SNAPSHOT-tests.jar!/jbossts-properties.xml at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getSingletonInstance(BeanPopulator.java:52) at com.arjuna.common.internal.util.logging.commonPropertyManager.getLoggingEnvironmentBean(commonPropertyManager.java:39) at com.arjuna.common.util.logging.LogFactory.setupLogSystem(LogFactory.java:146) at com.arjuna.common.util.logging.LogFactory.getLogNoi18n(LogFactory.java:107) at com.arjuna.ats.jta.logging.jtaLogger.<clinit>(jtaLogger.java:54) ... 67 more Caused by: java.lang.RuntimeException: invalid property file file:/home/sanne/.m2/repository/org/infinispan/infinispan-core/4.1.0-SNAPSHOT/infinispan-core-4.1.0-SNAPSHOT-tests.jar!/jbossts-properties.xml at com.arjuna.common.util.propertyservice.PropertiesFactory.getPropertiesFromFile(PropertiesFactory.java:79) at com.arjuna.common.util.propertyservice.PropertiesFactory.initDefaultProperties(PropertiesFactory.java:187) at com.arjuna.common.util.propertyservice.PropertiesFactory.getDefaultProperties(PropertiesFactory.java:57) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getSingletonInstance(BeanPopulator.java:49) ... 71 more 2010-08-17 11:48:49,656 INFO [TransactionManagerFactory] (main) failed looking up TransactionManager, will not use transactions java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.infinispan.transaction.lookup.JBossStandaloneJTAManagerLookup.getTransactionManager(JBossStandaloneJTAManagerLookup.java:54) at org.infinispan.factories.TransactionManagerFactory.construct(TransactionManagerFactory.java:55) at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:306) at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:244) at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:803) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:219) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:118) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:186) at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:314) at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:244) at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:803) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:219) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:118) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:186) at org.infinispan.factories.InterceptorChainFactory.createInterceptor(InterceptorChainFactory.java:50) at org.infinispan.factories.InterceptorChainFactory.buildInterceptorChain(InterceptorChainFactory.java:67) at org.infinispan.factories.InterceptorChainFactory.construct(InterceptorChainFactory.java:192) at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:306) at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:244) at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:803) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:219) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:118) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:186) at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:314) at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:244) at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:803) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:219) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:118) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:186) at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:314) at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:244) at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:803) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:219) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:118) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:186) at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:314) at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:244) at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:803) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:219) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:118) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:186) at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:314) at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:244) at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:803) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:219) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:118) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:186) at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:314) at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:244) at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:803) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:219) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:118) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:186) at org.infinispan.factories.InternalCacheFactory.bootstrap(InternalCacheFactory.java:90) at org.infinispan.factories.InternalCacheFactory.createAndWire(InternalCacheFactory.java:77) at org.infinispan.factories.InternalCacheFactory.createCache(InternalCacheFactory.java:58) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:445) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:411) Even though the properties file is within the JAR and the contents of the jar and xml have been verified, the following code does not like it: filepath = FileLocator.locateFile(propertyFileName); File propertyFile = new File(filepath); if(!propertyFile.exists() || !propertyFile.isFile()) { throw new RuntimeException("invalid property file "+filepath); } Maybe the JBoss TS code should be improved to locate property files within jars? -- 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, 8 months

3
5
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, 8 months

1
8
0 / 0

[JBoss JIRA] Created: (JBTM-748) Calling rollback_only via OTS is throwing the wrong exception

by Michael Musgrove (JIRA)

Calling rollback_only via OTS is throwing the wrong exception ------------------------------------------------------------- Key: JBTM-748 URL: https://jira.jboss.org/browse/JBTM-748 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.11.0 Reporter: Michael Musgrove Assignee: Andrew Dinn Fix For: 4.12.0 Occasionally our BlackTie CI test run is failing when marking a transaction rollback only because it is getting the wrong exception back from the transaction manager 16:11:10,296 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for TX -53ee7cfb:10e2:4c0fa834:22ec in state RUN [exec] 2010-06-09 16:11:10,296 [0x0000123c] WARN (TxLogControl :153 ) - rollback_only: INVALID_TRANSACTION minor: 20001 16:11:10,328 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_7] - TransactionReaper::doCancellations worker Thread[Thread-18,5,jboss] successfully canceled TX -53ee7cfb:10e2:4c0fa834:22ec The second log message comes from the C client (the other two from the reaper). The CORBA System exception major/minor code represents INVALID_TRANSACTION/INACTIVE_TRANSACTION which according to the OTS spec is incorrect. A look at the code shows a race condition between a BlackTie C client marking a transaction abort only and the Transaction Reaper cancelling it (due to a timeout being reached). The reaper eventually winds up in ControlImple.destroy() where the CORBA object representing the transaction is destroyed. There is a window where the C client request reaches JacORB just before the reaper has had a chance to destroy the CORBA object resulting in the wrong exception being returned. -- 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, 8 months

3
7
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, 9 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, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-774) TM is not fully OTS spec compliant with respect to XA

by Michael Musgrove (JIRA)

TM is not fully OTS spec compliant with respect to XA ------------------------------------------------------ Key: JBTM-774 URL: https://jira.jboss.org/browse/JBTM-774 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.6.1.CP07, 4.12.0 Reporter: Michael Musgrove Assignee: Mark Little Fix For: 4.13.0, 4.6.1.CP08 According to the OTS specification the Propagation Context should always be available. Annex B2.2 says: "The Transaction Service does not restrict the availability of the PropagationContext: the operation get_txcontext on the Coordinator never raises Unavailable." However the TM is raising this exception if the transaction has been aborted (for example if the reaper has detected that the transaction has timed out). [The method ArjunaTransactionImple.get_txcontext will always raise CosTransactions.Unavailable if the transaction is not active.] This problem was observed whilst running the BlackTie test suite. -- 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, 10 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2010