June 2009 - 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, 4 months

2
8
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-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

[JBoss JIRA] Created: (JBTM-539) the Recovery ORB is bound to 0.0.0.0

by Frank Schwarz (JIRA)

the Recovery ORB is bound to 0.0.0.0 ------------------------------------ Key: JBTM-539 URL: https://jira.jboss.org/jira/browse/JBTM-539 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration, Configuration, JTS, Recovery Environment: JBoss AS 5.0.0.GA Reporter: Frank Schwarz from jbossjts-properties.xml:  <property name="com.arjuna.ats.jts.recoveryManagerAddress" value=""/> This is not quite right. I can see a binding to 0.0.0.0 instead of the ip-address the server was started with (run.cmd -b <...>) When I change this line to <property name="com.arjuna.ats.jts.recoveryManagerAddress" value="${jboss.bind.address}"/> the Recovery ORB is bound instead to 127.0.0.1 I have to be explicit on the ip-address to get the right binding. Please use the default ip-address as stated with the "-b option" to bind the Recovery ORB if nothing else is specified. -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBTM-521) Fatal error when obtaining POA

by Jason T. Greene (JIRA)

Fatal error when obtaining POA ------------------------------ Key: JBTM-521 URL: https://jira.jboss.org/jira/browse/JBTM-521 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6.0 Reporter: Jason T. Greene When updating to 4.6.0.GA, org.jboss.test.jca.test.TxInflowUnitTestCase in the AS testsuite triggers a fatal error obtaining a POA. com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:537) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.<init>(ServerControl.java:230) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.<init>(SubordinateAtomicTransaction.java:51) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.<init>(TransactionImple.java:57) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.importTransaction(TransactionImporterImple.java:90) at com.arjuna.ats.internal.jbossatx.jta.jca.XATerminator.registerWork(XATerminator.java:106) at org.jboss.resource.work.JBossWorkManager.importWork(JBossWorkManager.java:167) at org.jboss.resource.work.JBossWorkManager.doWork(JBossWorkManager.java:103) at org.jboss.test.jca.inflow.TestResourceAdapterTxInflow.basicTest(TestResourceAdapterTxInflow.java:81) at org.jboss.test.jca.inflow.TestResourceAdapterTxInflow.run(TestResourceAdapterTxInflow.java:55) at org.jboss.test.jca.inflow.TestResourceAdapter.testTxInflow(TestResourceAdapter.java:77) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:263) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) -- 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

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-439) TMENDRSCAN could be earlier

by Mark Little (JIRA)

TMENDRSCAN could be earlier --------------------------- Key: JBTM-439 URL: https://jira.jboss.org/jira/browse/JBTM-439 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little -- 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

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2009