[Proxool-developer] J2EE 1.2.1 compliance testing

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

Dear All,

Yesterday I sent a report highlighting an error that occured when using 
Proxool with Ci-Access, a product we have developed.  It appears that 
Proxool obtained the connection and yet threw a SQLException when a 
statement was executed using that connection.  In order to investigate 
which product actually caused the problem, I today tested the Oracle 
driver by itself, which passed most (but not all!) tests in the test 
suite.  I then tested with the Proxool and Oracle drivers, and found 
that the test suite does have a strange problem with Proxool.  I think 
that it cannot find ConnectionPoolManager.class in this method:

   public static ConnectionPoolManager getInstance() {
        if (connectionPoolManager == null) {
            synchronized (ConnectionPoolManager.class) {
                if (connectionPoolManager == null) {
                    connectionPoolManager = new ConnectionPoolManager();
                }
            }
        }
        return connectionPoolManager;
    }

Here's the test-suite log:

********************************************************************************
Beginning Test:  testAllProceduresAreCallable
********************************************************************************
SVR: Using DataSource
SVR-ERROR:
SVR-ERROR: java.lang.NoClassDefFoundError
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:115)
    at org.logicalcobwebs.proxool.ConnectionPoolManager.class$(Unknown 
Source)
    at org.logicalcobwebs.proxool.ConnectionPoolManager.<clinit>(Unknown 
Source)
    at org.logicalcobwebs.proxool.ProxoolDriver.connect(Unknown Source)
    at java.sql.DriverManager.getConnection(DriverManager.java:512)
    at java.sql.DriverManager.getConnection(DriverManager.java:172)
    at 
com.sun.enterprise.resource.JdbcConnectionAllocator.createResource(JdbcConnectionAllocator.java:72)

... and so on for a few pages...

Any ideas?  I thought J2EE might need the full name, so will try that 
and see what happens.

Regards,

Alastair Calderwood

"Save paper...  don't print out stack traces!"