Bug 724363 (BRMS-309) - Limited jurisdiction policy files in IBM's JDK version 5 prevent mssql jdbc driver from connecting to the database
Summary: Limited jurisdiction policy files in IBM's JDK version 5 prevent mssql jdbc d...
Keywords:
Status: CLOSED WONTFIX
Alias: BRMS-309
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: 3rd Party, Configuration
Version: 5.0.2
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: future
Assignee: Tihomir Surdilovic
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-22 15:36 UTC by Jiri Locker
Modified: 2011-05-26 20:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
RHEL 5, IBM JDK 5, MSSQL database accesed via msjdbc-2.0.1008.2 jdbc driver
Last Closed: 2011-05-26 20:16:38 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-309 0 None Closed Limited jurisdiction policy files in IBM's JDK version 5 prevent mssql jdbc driver from connecting to the database 2011-08-23 09:24:30 UTC

Description Jiri Locker 2010-04-22 15:36:34 UTC
Date of First Response: 2010-04-22 11:46:19
securitylevel_name: Public

The attempt to connect to the database results in
   [groovy] java.lang.NoClassDefFoundError: javax.crypto.b (initialization failure)
   [groovy] 	at java.lang.J9VMInternals.initialize(J9VMInternals.java:134)
   [groovy] 	at javax.crypto.Cipher.getInstance(Unknown Source)
   [groovy] 	at com.ibm.jsse2.gb.a(gb.java:55)
   [groovy] 	at com.ibm.jsse2.cb.<init>(cb.java:66)
   [groovy] 	at com.ibm.jsse2.eb.a(eb.java:300)
   [groovy] 	at com.ibm.jsse2.eb.a(eb.java:27)
   [groovy] 	at com.ibm.jsse2.db.m(db.java:283)
   [groovy] 	at com.ibm.jsse2.db.a(db.java:108)
   [groovy] 	at com.ibm.jsse2.jc.a(jc.java:380)
   [groovy] 	at com.ibm.jsse2.jc.g(jc.java:444)
   [groovy] 	at com.ibm.jsse2.jc.a(jc.java:1)
   [groovy] 	at com.ibm.jsse2.jc.startHandshake(jc.java:35)
   [groovy] 	at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1394)
   [groovy] 	at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1204)
   [groovy] 	at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(SQLServerConnection.java:1054)
   [groovy] 	at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:758)
   [groovy] 	at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:842)

The issue might be worked around by following IBM's Security Information article at http://www.ibm.com/developerworks/java/jdk/security/50/
This is currently under investigation.

Comment 2 John Graham 2011-05-26 20:16:38 UTC
No longer supporting 1.5 level VM


Note You need to log in before you can comment on or make changes to this bug.