February 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-726) Change some CosTransactions exceptions to be CORBA exceptions

by Mark Little (JIRA)

Change some CosTransactions exceptions to be CORBA exceptions ------------------------------------------------------------- Key: JBTM-726 URL: https://jira.jboss.org/jira/browse/JBTM-726 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.0 -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-668) Consider .NET interop

by Mark Little (JIRA)

Consider .NET interop --------------------- Key: JBTM-668 URL: https://jira.jboss.org/jira/browse/JBTM-668 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TxBridge Reporter: Mark Little Assignee: Mark Little http://www.jnbridge.com/jnbpro-transactions.htm -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-715) Improve test coverage for jts

by Mark Little (JIRA)

Improve test coverage for jts ----------------------------- Key: JBTM-715 URL: https://jira.jboss.org/jira/browse/JBTM-715 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS, Testing Reporter: Mark Little Assignee: Mark Little Fix For: 4.11.0 -- 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, 3 months

2
11
0 / 0

[JBoss JIRA] Created: (JBTM-268) Change SynchronizationRecord so it is an AbstractRecord

by Mark Little (JIRA)

Change SynchronizationRecord so it is an AbstractRecord ------------------------------------------------------- Key: JBTM-268 URL: http://jira.jboss.com/jira/browse/JBTM-268 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little -- 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, 3 months

2
2
0 / 0

[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-825) qa tests should support in-process recovery

by Jonathan Halliday (JIRA)

qa tests should support in-process recovery ------------------------------------------- Key: JBTM-825 URL: https://issues.jboss.org/browse/JBTM-825 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Recovery, Testing Affects Versions: 4.14.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.15.0 The qa (formerly dtf) testsuite spawns multiple client/server processes for each test. As currently configured, these share an objectstore dir and the recovery manager runs as a separate process. This makes them unsuitable for testing objectstore implementations that have in-process state and expect process exclusive access to their on-disk state i.e. only support in-process recovery manager. Now that we actually plan to create such implementations that's become a problem. The testsuite is unwieldy enough as it is, so we don't want to clone and modify tests, but rather have existing tests run with a dedicated objectstore and recovery manager per process rather than per test. This should be configurable, such that the tests may be run in either external or in-process recovery configuration. --- Modify the test harness to provide a uniq objectstore dir location to each spawned process. Allow crash recovery tests to selectively override this, as pre and post crash processes must use the same store or there won't be any state to recover. This requires tweaking the crashrec tests themselves to supply a correspondence identifier to the test harness so it can match pre and post crash processes. Spawned processes likewise need uniq/matching port values to avoid listener port conflicts between concurrent processes and ensure the recovery IORs are valid. Provide an optionally activated wrapper that will suppress the standalone recovery process and start/stop an in-process recovery system for each spawned task in the test. Use the directory and port values supplied to configure this. When the wrapper is not present, default behaviour of shared dir with external rec mgr will apply. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2011