I don't know for sure if this will help, but, if you have application
specific .jar files that are stored somewhere other than under your
WEB-INF/lib directory, you might want to try to move them there and see if
that makes a difference. What I always try to do when resolving a problem
like this is revert back to the basic installation, test out the sample
programs, make sure that works, then, start adding things back one at a time
until it breaks.
Jon
----- Original Message -----
From: "Taavi Tiirik" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 07, 2001 2:48 AM
Subject: tomcat4: sealing violation when reloading servlets
> I am encountering sealing violation problems with tomcat 4.0
> (nightly build 20010825). Whenever I recompile a servlet or
> change any .properties files that I use for i18n text
> messages press reload, it gives ServletException like this:
>
> Exception Report:
> javax.servlet.ServletException: Servlet.init() for servlet jsp
> threw exception at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:875)
> ...
>
> Root Cause:
> java.lang.SecurityException: sealing violation
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:234)
> ...
>
> As I have understood it can be avoided by not having conflicts
> between certain class libraries. I have plenty of them in
> jre/lib/ext directory...
>
> Is there any changes to the class loading mechanism in more
> current nightly builds?
>
> with best wishes,
> Taavi
>
>
