Bug #22726 the jdbc test tool can not normally run against to mysql connector/J 5.0.3
Submitted: 27 Sep 2006 7:09 Modified: 28 Sep 2006 2:09
Reporter: ming lu Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Connector / J Severity:S2 (Serious)
Version:5.0.3 OS:Linux (linux)
Assigned to: CPU Architecture:Any

[27 Sep 2006 7:09] ming lu
Description:
  I do a compliance test against to MySQL JDBC driver (mysql-connector-java-5.0.3) with the test tool jdbccts-1_3_1(the SUN's jdbc compliance test tool). But all the tests against to JDBC's interface are failed. 
  Then I change the MySQL JDBC driver to mysql-connector-java-3.1.13, the jdbccts can run normally, most of the tests can passed. 
  Why the mysql-connector-java-3.1.13 can be tested by jdbccts-1_3_1 but mysql-connector-java-5.0.3 can not ? 

  part of error message (test mysql-connector-java-5.0.3): 

Test: testSupportsStoredProcedures returned from running in ejb vehicle 
SVR: Using DataSource 
SVR-ERROR: SQL Exception : Cannot load connection class because of underlying exception: 'java.security.AccessControlException: access denied (java.lang.RuntimePermission modifyThreadGroup)'. 
SVR: Calling supportsStoredProcedures on DatabaseMetaData 
SVR-ERROR: Unexpected exception null 
SVR-ERROR: Call to supportsStoredProcedures is Failed! 
SVR-ERROR: java.lang.NullPointerException 
at com.sun.cts.tests.jdbc.ee.dbMeta.dbMeta1.dbMetaClient1.testSupportsStoredProcedures(dbMetaClient1.java:166) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
at java.lang.reflect.Method.invoke(Method.java:324) 
at com.sun.cts.harness.EETest.run(EETest.java:626) 
at com.sun.cts.harness.ServiceEETest.run(ServiceEETest.java:257) 
at com.sun.cts.harness.vehicle.ejb.EJBVehicle.runTest(EJBVehicle.java:65) 
at com.sun.cts.harness.vehicle.ejb.EJBVehicle_EJBObjectImpl.runTest(EJBVehicle_EJBObjectImpl.java:22) 
at org.omg.stub.com.sun.cts.harness.vehicle.ejb._EJBVehicle_EJBObjectImpl_Tie._invoke(Unknown Source) 
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:520) 
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:210) 
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:112) 
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255) 
at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:84) 
at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:99)

How to repeat:
  Install the jdbccts1.3.1 on linux(redhat9) according to the SUN's reference documents.
  Replace the mysql-connector-java-5.0.3.jar to the appointted place.
  Run the test tool and then look the jdbc-tests.log.
[28 Sep 2006 2:09] ming lu
Sorry, it maybe not a mysal jdbc's bug. I find that the java security policy is a important factor to the jdbccts. Now, I can run the test normally by modify the java security policy of the jdbccts1.3.1