June 2009 - jbossts-issues - Jboss List Archives

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

1
2
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] 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-570) Failed to recover with empty Tx log

by Tomohisa igarashi (JIRA)

Failed to recover with empty Tx log ----------------------------------- Key: JBTM-570 URL: https://jira.jboss.org/jira/browse/JBTM-570 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.2.3.SP5 Environment: JBoss SOA Platform 4.3.0 Sun JDK 1.5.0_18 RHEL5.3, WindowsXP_64 Reporter: Tomohisa igarashi If JBoss node is down when TransactionManager is at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore#write_state():751( after creating FOS:ofile before ofile.write() ), the following WARN message is output for a long time, and the transaction is no longer recovered because of an empty Tx log file. ---- 21:41:11,731 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.RecoverAtomicAction_4] - RecoverAtomicAction: transaction not activated, unable to replay phase 2 commit ---- IMO in this case, the transaction should be rollbacked. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-329) When BridgeParticipantAT receives prepare, participant should associate current thread with corresponding JTA transaction

by Pavel Kadlec (JIRA)

When BridgeParticipantAT receives prepare, participant should associate current thread with corresponding JTA transaction ------------------------------------------------------------------------------------------------------------------------- Key: JBTM-329 URL: http://jira.jboss.com/jira/browse/JBTM-329 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss-4.2.1.GA, JBossTS-4.2.3.SP7 Reporter: Pavel Kadlec When participant receives prepare from coordinator, it calls prepare on jta transaction. SubordinateAtomicAction.doPrepare then calls beforeCompletion() method. Hibernate registers Synchronization object which is called in beforeCompletion() method. In that synchronization object, when hibernate cannot find transaction on current thread, it flushes all entites into database, which is bad. When Hibernate cannot find transaction on thread, it logs WARN [AbstractEntityManagerImpl] Transaction not available on beforeCompletionPhase: assuming valid Fix is easy, BridgeParticipantAT should associate current thread with the corresponding JTA transaction. And finally it should suspend that JTA transaction. -- 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

15 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-566) Put the XTS interop tests to the 4.6.1.CP branch

by Ivo Studensky (JIRA)

Put the XTS interop tests to the 4.6.1.CP branch ------------------------------------------------ Key: JBTM-566 URL: https://jira.jboss.org/jira/browse/JBTM-566 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing, XTS Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 4.6.1.CP01 The XTS interop tests should be put to the 4.6.1CP branch as this is the branch supposed for EAP5 and we want to integrate the interop tests with EAP5's testsuite. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-484) Transaction timeout notifier

by Mark Little (JIRA)

Transaction timeout notifier ---------------------------- Key: JBTM-484 URL: https://jira.jboss.org/jira/browse/JBTM-484 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little Fix For: 4.7 Provide a means whereby listeners can be informed of timeouts. Should try to work with rollback-only too. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-230) Put xaRecoveryNode in configuration

by Mark Little (JIRA)

Put xaRecoveryNode in configuration ----------------------------------- Key: JBTM-230 URL: http://jira.jboss.com/jira/browse/JBTM-230 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP4 Reporter: Mark Little Assigned To: Mark Little Priority: Minor -- 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

15 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-438) Consider flattening the property file (again)

by Mark Little (JIRA)

Consider flattening the property file (again) --------------------------------------------- Key: JBTM-438 URL: https://jira.jboss.org/jira/browse/JBTM-438 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little At one time the configuration file was relatively straightforward. Then we added support for nested scopes and dependencies between scopes. This is overkill these days, so we should consider going back to a nice straightforward property 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

15 years, 6 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2009