Probably while Tomcat was running your app you've changed & recompiled some of
classes already loaded by your servlet or JSP (but not servlet class or JSP
themselves).
Alec
"Lacerda, Wellington (AFIS)" wrote:
> I got this error message (TOMCAT 3.2b6 NT4 ):
>
> java.lang.IllegalStateException: Can't happen - classname is null, who added
> this ?
> at
> org.apache.tomcat.core.ServletWrapper.loadServlet(ServletWrapper.java:261)
> at
> org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:289)
> at org.apache.tomcat.core.Handler.service(Handler.java:243)
> at
> org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:371)
> at
> org.apache.tomcat.core.ContextManager.handleStatus(ContextManager.java:1032)
> at
> org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:76
> 4)
> at
> org.apache.tomcat.core.ContextManager.service(ContextManager.java:732)
> at
> org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
> onnectionHandler.java:210)
> at
> org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:407)
> at
> org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
> at java.lang.Thread.run(Thread.java:484)
>
> Appart from the funny message, I got a LOT of problems with a web app that
> uses a lot of pre-generated classes (are working fine in TOMCAT 3.1). For
> instance, null pointers everywhere and some isOutdated() routine breaking in
> Jasper ?
>
> Any clues ?
>
> Wellington Silva
> UN/FAO
