Re: [Proxool-developer] JDBC API TestSuite 1.3.1 failure

[Bill H. <bi...@lo...>]

Bas,

On Fri, 2002-11-29 at 10:57, Bas Cancrinus wrote:

> In principle Proxool may be compliant, because all test 
> sets are passed the first time.

:-D

> The TestSuite repeats all test sets in 4 batches or so, to make sure 
> that the driver is consistent. When the TestSuite enters the second 
> batch it starts repeating the following stack trace:
> 
> java.lang.NoClassDefFoundError
>      at
> org.logicalcobwebs.proxool.ConnectionPool.<init>(ConnectionPool.java:101)

I don't understand that at all. Line 101 in ConnectionPool is:

    reloadMonitor = new ReloadMonitor(definition.getName());

Obviously, that class does exist since it is found the first time. I am
a little suspicious because the responisibility of that class is to spot
Proxool being reloaded (which can sometimes cause duplicate static
instances depending on what container is doing the reload). But I can't
see any code that would result in a class not being found! (Nor do I
know what code would cause that).

How many times does that error appear? 

Why does the test suite report "ERROR: An error occurred while closing
the database connection" whilst the stack trace seems to be related to
creating a new connection pool?

What is the reload mechanism between batches. Does the test suite
attempt to reload the classes? (I'm a little hazy about reloading
classes, JVMs and such). Or does it remove the connection pool and start
again (without any JVM or class reload stuff)?


I'm glad your looking into this. Proxool can only benefit from intensive
testing like this. I'm confident that this problem is not appearing in
production situations at the moment, but I still think it is very worth
while getting to the bottom of this.

Regards,
Bill


>      at
> org.logicalcobwebs.proxool.ConnectionPoolManager.createConnectionPool(ConnectionPoolManager.java:62)
>      at
> org.logicalcobwebs.proxool.ProxoolFacade.registerConnectionPool(ProxoolFacade.java:58)
>      at
> org.logicalcobwebs.proxool.ProxoolDriver.connect(ProxoolDriver.java:66)
>      at java.sql.DriverManager.getConnection(DriverManager.java:512)
>      at java.sql.DriverManager.getConnection(DriverManager.java:172)
>      at ...
> 
> And the test suite says:
> ERROR: An error occurred while closing the database connection
> Test case throws exception: java.lang.NoClassDefFoundError
> 
> Do you have any idea what could cause this problem? Further details:
> - All Proxool properties remain their default value during the tests, 
> i.e. we haven't set any proxool.* properties.
> - Tested source is current CVS repository state.
> 
> Many thanks,
> Bas