December 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-670) jts/iiop as embedded in jbossAS 5.1.0 - transaction examples are not working

by jzendle (JIRA)

jts/iiop as embedded in jbossAS 5.1.0 - transaction examples are not working ---------------------------------------------------------------------------- Key: JBTM-670 URL: https://jira.jboss.org/jira/browse/JBTM-670 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.6.1 Environment: JBoss 5.1.0GA, java 1.5.22, windows xp, Reporter: jzendle The examples described in this article on the wiki at https://www.jboss.org/community/wiki/TransactionPropagationwithJBoss Are not working. The 1st OTS test case dies on the client side with the following stack trace: [java] 1.3 [java] 1.4 [java] 1.5 [java] > Starting OTS tx with ejb2 [java] 15:13:01,837 { main} () [WARN ,arjLoggerI18N] [com.arjuna.ats.arj una.coordinator.TxControl_1] - Name of XA node not defined. Using a0d257d:be9:4b 22c3ed:0 [java] looking up OTSEjb2StatelessBean on host venus and orb name JBoss [java] jndi url: corbaloc::venus:3528/JBoss/Naming/root [java] javax.transaction.TransactionRequiredException: CORBA TRANSACTION_RE QUIRED 0 No; nested exception is: [java] org.omg.CORBA.TRANSACTION_REQUIRED: Server-side Exception: javax .transaction.TransactionRequiredException: Transaction Required vmcid: 0x0 min or code: 0 completed: No [java] at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException (Util.java:203) [java] at javax.rmi.CORBA.Util.mapSystemException(Util.java:67) [java] at org.jboss.proxy.ejb.DynamicIIOPStub.invoke(DynamicIIOPStub.ja va:149) [java] at org.jboss.jbossts.qa.astests.ejb2._MyRemote_Stub.foo(Unknown Source) [java] at com.arjuna.ats.tools.TxTest.ejbTest(TxTest.java:264) [java] at com.arjuna.ats.tools.TxTest.doTest(TxTest.java:119) [java] at com.arjuna.ats.tools.TxTest.main(TxTest.java:82) [java] Caused by: org.omg.CORBA.TRANSACTION_REQUIRED: Server-side Exception : javax.transaction.TransactionRequiredException: Transaction Required vmcid: 0 x0 minor code: 0 completed: No [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [java] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeC onstructorAccessorImpl.java:39) [java] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Del egatingConstructorAccessorImpl.java:27) [java] at java.lang.reflect.Constructor.newInstance(Constructor.java:50 1) [java] at org.jacorb.orb.SystemExceptionHelper.read(Unknown Source) [java] at org.jacorb.orb.ReplyReceiver.getReply(Unknown Source) [java] at org.jacorb.orb.Delegate.invoke_internal(Unknown Source) [java] at org.jacorb.orb.Delegate.invoke(Unknown Source) [java] at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457 ) [java] at org.jboss.proxy.ejb.DynamicIIOPStub.invoke(DynamicIIOPStub.ja va:124) [java] ... 4 more [java] 4 [java] ots: true -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-667) Hibernate exception stack is overridden by SetRollbackOnly

by Terry Xie (JIRA)

Hibernate exception stack is overridden by SetRollbackOnly ---------------------------------------------------------- Key: JBTM-667 URL: https://jira.jboss.org/jira/browse/JBTM-667 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.6.0 Environment: OS: windows XP. Intel CPU Reporter: Terry Xie The fix in https://jira.jboss.org/jira/browse/JBTM-66 makes the hibernate persistence exception lost in exception stack. For example, say there is a duplicate data constraint violation, hibernate entity manager calls calls transaction manager setRollbackOnly . However setRollbackOnly in TransactionImple.java sets the _rollbackOnlyCallerStacktrace which will be thrown as the exception cause later instead of the hibernate exception source. This makes the hibernate persistence exception unable to propagate to jboss clients. In this case, it is much more useful for hibernate exception information to be displayed to clients instead of the setRollbackOnly stack. The method in TransactionImple.java which throws the rollbackOnlyCallerStacktrace instead of _theTransaction.getDeferredThrowable() protected void commitAndDisassociate() throws javax.transaction.RollbackException, javax.transaction.HeuristicMixedException, javax.transaction.HeuristicRollbackException, java.lang.SecurityException, javax.transaction.SystemException, java.lang.IllegalStateException { . . . if(_rollbackOnlyCallerStacktrace != null) { // we rolled back beacuse the user explicitly told us not to commit. Attach the trace of who did that for debug: rollbackException.initCause(_rollbackOnlyCallerStacktrace); } else if(_theTransaction.getDeferredThrowable() != null) { // we tried to commit but it went wrong - attach the reason for debug: rollbackException.initCause(_theTransaction.getDeferredThrowable()); } Here should be the change related to issue JBTM-66 : http://viewvc.jboss.org/cgi-bin/viewvc.cgi/labs/labs/jbosstm/trunk/Arjuna... -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-377) XAResourceRecord save/restore state insufficiently paranoid

by Jonathan Halliday (JIRA)

XAResourceRecord save/restore state insufficiently paranoid ----------------------------------------------------------- Key: JBTM-377 URL: http://jira.jboss.com/jira/browse/JBTM-377 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Fix For: 4.4.CR2 The XAResourceRecord save state method writes meta-data into the objectstore before attempting to Serialize and write the actual bytes for an XAResource that it believes, on the basis of it implementing the market interface, is Serializable. If the serialization fails at runtime, the objectstore record is left in an invalid state and can cause the recovery pass to blow up in horrible ways. We should obtain the byte[] representing the serialized resource before writing anything to the record so that this does not occur. If serialization fails, the record will therefore be useless but at least not otherwise broken. -- 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

14 years, 7 months

2
10
0 / 0

[JBoss JIRA] Created: (JBTM-643) Create 3 interfaces for different aspects of ObjectStore

by Mark Little (JIRA)

Create 3 interfaces for different aspects of ObjectStore -------------------------------------------------------- Key: JBTM-643 URL: https://jira.jboss.org/jira/browse/JBTM-643 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core 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, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-663) MissingResourceException when synchronizing a JTA transaction

by Olivier BILLIARD (JIRA)

MissingResourceException when synchronizing a JTA transaction ------------------------------------------------------------- Key: JBTM-663 URL: https://jira.jboss.org/jira/browse/JBTM-663 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.8.0, 4.5.0 Environment: AS 5.0.1 GA Reporter: Olivier BILLIARD In the class "com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple" When we try to synchronize to an aborted JTA transaction a RollbackException is thrown. This exception is catched and we throw a RuntimeException using the key "com.arjuna.ats.internal.jta.transaction.arjunacore.syncrollbackmexception". This key doesn't exist in the jta_msg_en_US.properties file. It seems to me that the end of the key should be syncrollbackexception because this key exist in the file. I attach the corrected file. -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-608) Allow synchronization registration as long as beforeCompletion phase not finished

by Mark Little (JIRA)

Allow synchronization registration as long as beforeCompletion phase not finished --------------------------------------------------------------------------------- Key: JBTM-608 URL: https://jira.jboss.org/jira/browse/JBTM-608 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA, JTS, Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: future There are some edge cases where this may be useful. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-640) startEnbeddedTools may try to create a file without making parent directory

by Tomohisa igarashi (JIRA)

startEnbeddedTools may try to create a file without making parent directory --------------------------------------------------------------------------- Key: JBTM-640 URL: https://jira.jboss.org/jira/browse/JBTM-640 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.6.1 Reporter: Tomohisa igarashi Fix For: 4.2 startEnbeddedTools() from EmbeddedTools mbean may try to create a file without making parent directory, and end with FileNotFoundException. -- 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, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBTM-664) The JTA transaction synchronization don't respect the JTA 1.1 specification

by Olivier BILLIARD (JIRA)

The JTA transaction synchronization don't respect the JTA 1.1 specification --------------------------------------------------------------------------- Key: JBTM-664 URL: https://jira.jboss.org/jira/browse/JBTM-664 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.5.0, 4.6.1.CP04 Environment: jboss AS 5.0.1 GA Reporter: Olivier BILLIARD Priority: Critical According to the JTA 1.1 specification, the registerInterposedSynchronization must throw an IllegalStateException if the no transaction is active ( http://java.sun.com/javaee/5/docs/api/javax/transaction/TransactionSynchr... ). The current code throw a RuntimeException. It's a problem because some third party framework, like Spring, only catch RollbackException, SystemException and IllegalStateException. It'll be great to modify the registerInterposedSynchronization method for throwing the expected exception. I attach the corrected source file. -- 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, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (JBTM-666) Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule

by Justin Bertram (JIRA)

Add support to AppServerJDBCXARecovery for passwords encrypted for use with org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-666 URL: https://jira.jboss.org/jira/browse/JBTM-666 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Justin Bertram Attempting to recovery failed XA transactions from a datasource using: <security-domain>DefaultDSRealm</security-domain> Where the security realm's login module implementation is org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule. For example: <application-policy name = "DefaultDSRealm"> <authentication> <login-module code = "org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule" flag = "required"> <module-option name = "username">user</module-option> <module-option name = "password">oLxZUT0uKnAfS.zbvaEZd</module-option> <module-option name = "managedConnectionFactoryName">jboss.jca:service=XATxCM,name=XAOracleDS</module-option> <module-option name = "jaasSecurityDomain">jboss.security:service=JaasSecurityDomain,domain=ServerMasterPassword</module-option> </login-module> </authentication> </application-policy> (See more discussion of this configuration at http://www.jboss.org/community/wiki/encryptingdatasourcepasswords) This exception is thrown: 2009-12-03 09:53:20,388 ERROR [com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery] (Thread-6:) AppServerJDBCXARecovery.createConnection got exception java.sql.SQLException: Invalid argument(s) in call java.sql.SQLException: Invalid argument(s) in call at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208) at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:99) at com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery.createConnection(AppServerJDBCXARecovery.java:258) at com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery.getXAResource(AppServerJDBCXARecovery.java:115) at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecovery(XARecoveryModule.java:683) at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:179) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWork(PeriodicRecovery.java:237) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:163) This exception is thrown because com.arjuna.ats.internal.jbossatx.jta.AppServerJDBCXARecovery is attempting to create a connection without a username and password since it can't decrypt the password from the security domain. -- 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, 8 months

2
9
0 / 0

[JBoss JIRA] Closed: (JBTM-209) Debugging section is out of date

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-209?page=com.atlassian.jira.plugi... ] Mark Little closed JBTM-209. ---------------------------- Fix Version/s: 4.10.0 Resolution: Done > Debugging section is out of date > -------------------------------- > > Key: JBTM-209 > URL: https://jira.jboss.org/jira/browse/JBTM-209 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 4.2.2 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 4.10.0 > > > The section of debugging is out-of-date, e.g., no CommonLogging.xml exists since ATL days. -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues December 2009