Alan Burlison wrote:
Also, I've put code in that manually unregisters the EmbeddedDriver, but
I'm a bit puzzled because it doesn't seem to be loaded in the first
place - I've added code to list the loaded drivers befor and after the
unload, and here is what I see:
Unloading [EMAIL PROTECTED]
Before
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
After
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
It does seem to point to the AutoloadedDriver as being the problem
though...
I've added code to deregister all the Derby drivers on shutdown, I
iterate over the loaded drivers and call DriverManager.deregisterDriver
on any drivers that are in the org.apache.derby.jdbc package:
Before
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
After
[EMAIL PROTECTED]
However, jstack *still* shows an instance of derby.antiGC is running, so
although DERBY-2905 may be a factor, I think there is another problem
as well.
--
Alan Burlison
--
