Partager via

java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package

  • Article

We have heard from customers using WebSphere 6.0 and trying to use the v1.2 JDBC driver that they are encountering the above exception.  This problem is primarily due to a name mismatch between our JDBC driver and another vendor's jdbc driver.  While the v1.2 JDBC driver is supported by IBM WebSphere 6.1, it is not officially supported on WebSphere 6.0.  We recommend customers to upgrade to WebSphere 6.1 or later when possible.  If you are unable to upgrade to WebSphere 6.1 or later, one potential workaround is to install the v1.2 JDBC driver in a separate directory and configuring WebSphere to look for the driver in the new directory.  We have seen this resolves the issue in a number of cases.

Jimmy Wu
SQL Server JDBC Team

Comments

  • Anonymous
    July 11, 2008
    I am not able to get connect to the sqlserver 2000 database.... i even set the path and also installed the sql driver ver:2.0 plz help me out.....

  • Anonymous
    August 05, 2008
    The comment has been removed

  • Anonymous
    August 18, 2008
    Hi, Is there any official document of IBM or MS to state that WebShpere 6.0 does not support JDBC 1.2? We met the same problem and need some related document. Thanks a lot. Neil

  • Anonymous
    December 22, 2008
    SQL server 2005 JDBC 1.2 java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.TDSCommand"'s signer information does not match signer information of other classes in the same package        at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code))        at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code))        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code))        at java.net.URLClassLoader.defineClass(URLClassLoader.java:475)        at java.net.URLClassLoader.access$500(URLClassLoader.java(Inlined Compiled Code))        at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java(Compiled Code))        at java.security.AccessController.doPrivileged1(Native Method)        at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))        at java.net.URLClassLoader.findClass(URLClassLoader.java(Compiled Code))        at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:90)        at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))        at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))        at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(Unknown Source)        at com.microsoft.sqlserver.jdbc.SQLServerPooledConnection.createNewConnection(Unknown Source) Any resolution for this?