Hi, all.  I am making great progress on implementing a classloader that will 
protect shared code from strange "shadowing" behavior when the classpath has 
multiple versions of Derby.  

However, in the checkDataSource.java test, I am getting a StackOverflowError at 
the point when it calls 
DriverManager.getConnection("jdbc:derby:shutdown=true").  

I can't seem to catch this error or print a stack trace, so I'm looking for a 
little help:

- Anybody know how to track down a StackOverflowError that won't give you a 
stack trace?

- The change I made to EmbeddedDriver is that EmbeddedDriver now delegates to 
EmbeddedDriverImpl (which has been loaded through my specialized classloader).  
Does anyone know why this might make shutdown go into an endless loop?  I have 
tried walking through the code but its quite twisty and it will take me some 
time to work through it.  Any tips would be much appreciated.

Thanks,

David

Reply via email to