There is nothing an application (or an application framework) can
really do to affect how servlet containers do application reloads. 
I've had lots of success on pure Tomcat 5 installations, but I have
heard hearsay about problems with the JBoss class loader scheme (which
completely replaces the standard Tomcat mechanisms).  That would tend
to suggest the JBoss user list as a place to ask about similar
experiences and possible solutions.

In any container, obvious things to double check, of course, include
having all the JAR files involved inside your /WEB-INF/lib directory
(as opposed to a shared directory in the server), and otherwise making
sure that you don't have more than one copy of the classes visible. 
That tends to be the root cause of most class loader related issues.

Craig


On Mon, 02 Aug 2004 01:02:41 -0400, Erik Weber <[EMAIL PROTECTED]> wrote:
> During hot deployment in JBoss 3.2.4 and 3.2.5 / Tomcat 5 (both on Red
> Hat and Windows 2000), ActionServlet is failing to initialize and
> logging this message to standard out not every time, but quite often:
> 
> Error: [ActionServlet] javax.servlet.UnavailableException: Cannot
> initialize RequestProcessor of class MyRequestProcessor:
> java.lang.ClassNotFoundException: No ClassLoaders found for:
> MyRequestProcessor
> 
> There seems to be a pattern to this occurrence but I won't go into the
> details of it here unless someone asks, except to say, if you just keep
> redeploying the same app without any changes to struts-config.xml and
> without redeploying other apps in between, it doesn't seem to happen.
> 
> Every time this happens, I have to clean out the server tmp directories
> and restart the server.
> 
> Is this a bug in Struts or in Tomcat? I would appreciate any tips. This
> doesn't seem to happen when I don't plug in my own RequestProcessor.
> 
> Thanks,
> Erik
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to