[Proxool-developer] J2EE 1.2.1 compliance testing

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

1  .class file is not found in .jar

Thanks for your tip, Christian.  I'll try with a different lock to see 
if that solves the problem. Out of interest has anyone else had this 
problem with the jar, or are you all using unjarred classes?  I'll use 
them unjarred until this problem is solved.

2.  Oracle maximum cursors exceeded error

On Friday I reported that Oracle was producing an error for certain 
tests when tested with Proxool.  The error was:

SVR-ERROR: java.rmi.RemoteException: ORA-01000: maximum open cursors
exceeded

I have researched the cause of the problem in Oracle FAQ and it appears 
that Oracle's default maximum number of cursors (300) should be quite 
sufficient.  Cursors are staying open only because the test suite does 
not close every PreparedStatement but instead relies on the close method 
of Connection, which with a plain driver (i.e. without a connection pool 
in front) would call finalize on the whole hierarchy.  In a connection 
pool where connections are not really closed, and there is no reference 
to the hierarchy, this never occurs.  Personally I'd say it was the 
application programmer's responsiblity to close PreparedStatements - not 
sure why they haven't done so in the tests - and in my opinion the 
failure of these tests is not too important, but others might have 
different points of view.  My next test is to run via a remote-access 
application (Ci-Access) that does close PreparedStatements when a 
Connection is closed, so perhaps that will yield a better result

Alastair Calderwood