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

Ivo Studensky (JIRA) jira-events at lists.jboss.org
Wed May 13 08:47:46 EDT 2009


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

        



More information about the jbossts-issues mailing list