July 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-554) Testsuite - fluctuant org.omg.CORBA.OBJECT_NOT_EXIST: Server-side Exception errors on RHEL4 and Sun/IBM jdk1.5

by Ivo Studensky (JIRA)

Testsuite - fluctuant org.omg.CORBA.OBJECT_NOT_EXIST: Server-side Exception errors on RHEL4 and Sun/IBM jdk1.5 -------------------------------------------------------------------------------------------------------------- Key: JBTM-554 URL: https://jira.jboss.org/jira/browse/JBTM-554 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.6.1 Environment: RHEL4 x86_64 + java15_x86_64 and RHEL4_x86 + ibm15 Reporter: Ivo Studensky An error occurs on the combination of RHEL4 and Sun/IBM jdk1.5 in the otsserver test group. Sometimes there are 2 errors, sometimes only 1 error occurs. Error messages from the log are here: Client14.Worker.run: org.omg.CORBA.OBJECT_NOT_EXIST: Server-side Exception: vmcid: 0x0 minor code: 0 completed: No org.omg.CORBA.OBJECT_NOT_EXIST: Server-side Exception: vmcid: 0x0 minor code: 0 completed: No at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.jacorb.orb.SystemExceptionHelper.read(Unknown Source) at org.jacorb.orb.ReplyReceiver.getReply(Unknown Source) at org.jacorb.orb.Delegate.invoke_internal(Unknown Source) at org.jacorb.orb.Delegate.invoke(Unknown Source) at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457) at org.omg.CosTransactions._ControlStub.get_terminator(_ControlStub.java:32) at org.jboss.jbossts.qa.OTSServerClients.Client14$Worker.run(Client14.java:164) [jacorb.poa] INFO : POA RootPOA destroyed java.io.FileNotFoundException: ServerIORs (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at java.io.FileInputStream.<init>(FileInputStream.java:66) at org.jboss.jbossts.qa.Utils.FileServerIORStore.removeIOR(FileServerIORStore.java:69) at org.jboss.jbossts.qa.Utils.ServerIORStore.removeIOR(ServerIORStore.java:47) at org.jboss.jbossts.qa.Utils.RemoveServerIORStore.main(RemoveServerIORStore.java:42) Error logs on Hudson: http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... Affected Hudson jobs: http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... http://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-testsuite-matr... -- 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

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-543) qa tests should support driver selection

by Jonathan Halliday (JIRA)

qa tests should support driver selection ---------------------------------------- Key: JBTM-543 URL: https://jira.jboss.org/jira/browse/JBTM-543 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 For some database servers we want to runs tests with multiple different versions of the drivers. This is non-trivial, as the driver versions each use the same classnames, so only one version can be on the classpath at a time. We'll need some kind of config mechanism to alter the classpath on the fly. -- 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

15 years, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (JBTM-553) Testsuite running on openjdk is missing class javax.crypto.JceSecurity

by Ivo Studensky (JIRA)

Testsuite running on openjdk is missing class javax.crypto.JceSecurity ---------------------------------------------------------------------- Key: JBTM-553 URL: https://jira.jboss.org/jira/browse/JBTM-553 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.6.1 Environment: RHEL5 x86_64, openjdk Reporter: Ivo Studensky Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class javax.crypto.JceSecurity at javax.crypto.KeyGenerator.nextSpi(KeyGenerator.java:310) at javax.crypto.KeyGenerator.<init>(KeyGenerator.java:140) at javax.crypto.KeyGenerator.getInstance(KeyGenerator.java:191) at sun.security.ssl.JsseJce.getKeyGenerator(JsseJce.java:240) at sun.security.ssl.RSAClientKeyExchange.<init>(RSAClientKeyExchange.java:108) at sun.security.ssl.ClientHandshaker.serverHelloDone(ClientHandshaker.java:593) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:533) at sun.security.ssl.Handshaker.process_record(Handshaker.java:471) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:904) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1116) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1143) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1127) at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1394) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1204) at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(SQLServerConnection.java:1054) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:758) at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:578) at com.microsoft.sqlserver.jdbc.SQLServerPooledConnection.createNewConnection(SQLServerPooledConnection.java:67) at com.microsoft.sqlserver.jdbc.SQLServerPooledConnection.<init>(SQLServerPooledConnection.java:43) at com.microsoft.sqlserver.jdbc.SQLServerXAConnection.<init>(SQLServerXAConnection.java:27) at com.microsoft.sqlserver.jdbc.SQLServerXADataSource.getXAConnection(SQLServerXADataSource.java:51) at com.arjuna.ats.internal.jdbc.IndirectRecoverableConnection.createConnection(IndirectRecoverableConnection.java:431) at com.arjuna.ats.internal.jdbc.IndirectRecoverableConnection.getConnection(IndirectRecoverableConnection.java:298) at com.arjuna.ats.internal.jdbc.ConnectionImple.getConnection(ConnectionImple.java:704) at com.arjuna.ats.internal.jdbc.ConnectionImple.registerDatabase(ConnectionImple.java:806) at com.arjuna.ats.internal.jdbc.ConnectionImple.createStatement(ConnectionImple.java:162) at org.jboss.jbossts.qa.JDBCResources01Setups.Setup02.main(Setup02.java:94) -- 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

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-596) provide bean based configuration

by Jonathan Halliday (JIRA)

provide bean based configuration -------------------------------- Key: JBTM-596 URL: https://jira.jboss.org/jira/browse/JBTM-596 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration, Common, Configuration, JTA, JTS Affects Versions: 4.7.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.8.0 bean-centric DI frameworks are the flavour of the day. Add a set of beans representing the config options so that the system can be configured through them rather than via a -properties.xml -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-532) Connection leak if the DBMS is not mapped into the ModifierFactory or if the DBMS does not support multiple connections

by Mauro Molinari (JIRA)

Connection leak if the DBMS is not mapped into the ModifierFactory or if the DBMS does not support multiple connections ----------------------------------------------------------------------------------------------------------------------- Key: JBTM-532 URL: https://jira.jboss.org/jira/browse/JBTM-532 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.6.0, 4.5.0 Environment: Spring + JBossJTA Reporter: Mauro Molinari Priority: Blocker When a close() is issued on a ConnectionImple() before transaction termination (and this can happen because of Spring JTA infrastructure calling org.springframework.jdbc.datasource.DataSourceUtils.ConnectionSynchronization.beforeCompletion()) and either: - the ModifierFactory has no information about the DBMS in use (PostgreSQL, for instance...) or - the modifier for the DBMS says that it does not support multiple connections in a single transaction then, the synchronization that should close the connection after transaction completion is not registered and the connection is lost! This is at lines 349-359 of com.arjuna.ats.internal.jdbc.ConnectionImple in JBossTS 4.5.0 GA codebase. IMHO, the synchronization should always be registered unless we are sure that multiple connections in a single transaction are not supported. I have no idea of what should happen in the latter case... -- 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

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-432) Authentication support on AppServerJDBCXARecovery plugin

by Tyronne Wickramarathne (JIRA)

Authentication support on AppServerJDBCXARecovery plugin -------------------------------------------------------- Key: JBTM-432 URL: https://jira.jboss.org/jira/browse/JBTM-432 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2.3.SP5 Environment: JBoss-EAP-4.3_CP3, jdk 1.5.0_15-b04 Reporter: Tyronne Wickramarathne The present implementation of AppServerJDBCXARecovery plugin has a limitation on its usage when the invokers are secured. Hence, to overcome this limitation AppServerJDBCXARecovery plugin has to support authentication so this could be used even when the invokers are secured. -- 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

15 years, 5 months

4
12
0 / 0

[JBoss JIRA] Closed: (JBTM-156) add support for getting the Xid from JTA transactions.

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-156?page=com.atlassian.jira.plugi... ] Mark Little closed JBTM-156. ---------------------------- Fix Version/s: 4.8.0 (was: future) Resolution: Done get_uid was already available through our own Transaction interface, but getTxId has been added (and documented) to return an Xid equivalent. > add support for getting the Xid from JTA transactions. > ------------------------------------------------------ > > Key: JBTM-156 > URL: https://jira.jboss.org/jira/browse/JBTM-156 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Documentation, JTA, JTS > Affects Versions: 4.2.1 > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 4.8.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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-590) Add back support for isEnabled in BasicAction

by Mark Little (JIRA)

Add back support for isEnabled in BasicAction --------------------------------------------- Key: JBTM-590 URL: https://jira.jboss.org/jira/browse/JBTM-590 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Mark Little Fix For: future -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-580) CacheStore race condition on remove_state

by Mark Little (JIRA)

CacheStore race condition on remove_state ----------------------------------------- Key: JBTM-580 URL: https://jira.jboss.org/jira/browse/JBTM-580 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Mark Little Fix For: 4.8.0 Failed to check state was being processed. -- 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

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-572) WARN message about completed transaction (Could not find new XAResource..)

by Tomohisa igarashi (JIRA)

WARN message about completed transaction (Could not find new XAResource..) -------------------------------------------------------------------------- Key: JBTM-572 URL: https://jira.jboss.org/jira/browse/JBTM-572 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.2.3.SP5 Environment: JBoss SOA-P 4.3.0 Reporter: Tomohisa igarashi If JBoss node is down when TransactionManager is at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore#remove_state():652( before deleting Tx log after RM's commit is completed ), the following WARN message is output for a long time. ---- 15:03:44,952 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa]Could not find new XAResource to use for recovering non-serializable XAResource< 131075, 31, 29, 1--53e1e740:1064:4a40cd21:2460b-53e1e740:1064:4a40cd21:2460c ---- Removing this log automatically might not be the best way when thinking the case where RM lost the ｔransaction. Manual recovering is needed. So, JBossTM must have the way of deleting Tx log manually. -- 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

15 years, 5 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2009