On 6 Apr 2004, at 20:08, Werner Guttmann wrote:
- are you familiar with Tomcat's classloader hierarchy as per http://jakarta.apache.org/tomcat/tomcat-5.0-doc/class-loader- howto.html ?
Yup.
- after having read that document, where does castor-0.9.5.x.jar reside ? If in common/lib, this might be a problem.
In common/lib; if you feel it would behave differently in shared/lib, I'd be surprised - either way, the problem isn't whether or not they're in the set of jars referenced internally to Tomcat, IMO, the problem is that they're *not* in the webapp classloader.
As I said - there are no other problems; changing this one thing, from array to arraylist, has caused it to immediately start working as it should. That's true even when I access something which was in the JDO cache, before unload is called and the clear operation takes place, and then access again in the new webapp - which is a smaller test case than the one we had previously, which was that any access to a JDO class which referenced an array type of other JDO classes, regardless of whether the instance would have ever been in cache, causing a failure.
The fact that it *almost* works perfectly is the point here - it's nigh-on perfect. What I don't understand is what's being left around residually between the unload of one WAR and the load of the next, when the JDO instance itself has been discarded.
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
