[Proxool-developer] J2EE compliance testing

[Alastair C. <ala...@ci...>]

Dear All,

I have been attempting to run the J2EE 1.2 compliance tests with 
Proxool.  Unfortunately there have been two problems.  At first, it 
emerged that the user and password for the database needed to be the 
same (unlike the J2EE 1.3 test-suite).  I solved this rather tedious 
problem by altering the password in Oracle, and a connection to Oracle 
is now obtained via Proxool (I logged the toString() of the connection - 
i.e. the address - to make sure it is a real connection).  There are 
therefore no problems with Proxool itself.  The problem now is that 
there is an exception thrown by the test suite itself, which is proving 
harder to rectify.  The test suite output is as follows:

********************************************************************************
Beginning Test:  testAllProceduresAreCallable
********************************************************************************
SVR: Using DataSource
SVR: intTabSize: 5
SVR: intTabTypeSize: 5
SVR: createString1: create table ctstable1 (TYPE_ID int, TYPE_DESC 
varchar(32), primary key(TYPE_ID))
SVR-ERROR: SQLException creating ctstable2 or ctstable1 table
SVR-ERROR: An exception occurred on a remote host. Details: Unable to 
forward the command, java.rmi.ServerException: RemoteException occurred 
in server thread; nested exception is:
    java.rmi.RemoteException: java.rmi.ServerException: RemoteException 
occurred in server thread; nested exception is:
    java.rmi.RemoteException: java.rmi.ServerException: RemoteException 
occurred in server thread; nested exception is:
    java.rmi.RemoteException: java.rmi.RemoteException: 
java.lang.NullPointerException
SVR: Closed the database connection
SVR-ERROR: Setup Failed!

SVR-ERROR: java.rmi.RemoteException: An exception occurred on a remote 
host. Details: Unable to forward the command, java.rmi.ServerException: 
RemoteException occurred in server thread; nested exception is:
    java.rmi.RemoteException: java.rmi.ServerException: RemoteException 
occurred in server thread; nested exception is:
    java.rmi.RemoteException: java.rmi.ServerException: RemoteException 
occurred in server thread; nested exception is:
    java.rmi.RemoteException: java.rmi.RemoteException: 
java.lang.NullPointerException
    at 
com.sun.cts.tests.jdbc.ee.common.dbSchema.createData(dbSchema.java:54)
    at 
com.sun.cts.tests.jdbc.ee.dbMeta.dbMeta1.dbMetaClient1.setup(dbMetaClient1.java:123)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.sun.cts.harness.EETest.run(EETest.java:589)
    at com.sun.cts.harness.ServiceEETest.run(ServiceEETest.java:249)
    at 
com.sun.cts.harness.vehicle.ejb.EJBVehicle.runTest(EJBVehicle.java:68)
    at 
com.sun.cts.harness.vehicle.ejb.EJBVehicle_EJBObjectImpl.runTest(EJBVehicle_EJBObjectImpl.java:17)
    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:423)
    at 
com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:137)
    at 
com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:98)
    at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:227)
    at 
com.sun.corba.ee.internal.iiop.CachedWorkerThread.doWork(IIOPConnection.java:262)
    at 
com.sun.corba.ee.internal.iiop.CachedWorkerThread.run(IIOPConnection.java:230)

The NullPointerException is thrown by the following code in the method 
com.sun.cts.tests.jdbc.ee.common.dbSchema.createData:

44  try
45          {
46              // Create the database tables
47              props=p;
48              createTable(p,conn);
49              TestUtil.logMsg("Created the tables " + pTableName + " 
and " + fTableName);
50          }
51          catch (Exception e)
52          {
53             dbUnConnect(conn);
54              throw new RemoteException( e.getMessage() );
55        }

which means that either 'props' or 'conn' is null for some reason.  I am 
investigating this, but as it's not really possible to recompile the 
test-suite itself, and you have to wait about 30 minutes before the 
output for the first test (i.e. the output above) appears, it is taking 
a more time than I expected.  Please bear with me and I'll keep you 
informed of any further developments.

Regards,
Alastair Calderwood
Cipherware Ltd.
http://www.cipherware.com