Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

JSP 1.0 Compilation Error

0 views
Skip to first unread message

John Adkins

unread,
Mar 10, 2000, 3:00:00 AM3/10/00
to
I have upgraded WAS 3.0 to WAS 3.02 and now I cannot compile any jsp
files. Instead I get the following message:

java.lang.NoClassDefFoundError: com/ibm/cs/util/ObjInfo
at
com.sun.jsp.compiler.Jsp1_0ParseEventListener.beginPageProcessing(Jsp1_0ParseEventListener.java:525)
at com.sun.jsp.compiler.Main.compile(Main.java:307)
at com.sun.jsp.runtime.JspLoader.compile(JspLoader.java:86)
at com.sun.jsp.runtime.JspLoader.loadJSP(JspLoader.java:200)
at
com.sun.jsp.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:99)
at
com.sun.jsp.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:110)
at com.sun.jsp.runtime.JspServlet.serviceJspFile(JspServlet.java:400)
at com.sun.jsp.runtime.JspServlet.service(JspServlet.java:510)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:639)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:557)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:349)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:705)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:631)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebApp.java:1129)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebApp.java:1001)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebApp.java:960)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebGroup.java:681)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:139)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQEventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventListenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQEventSource.java:202)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.notifyService(SQWrapperEventSource.java:347)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRunnable.run(SQWrapperEventSource.java:216)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run(Compiled
Code)
at java.lang.Thread.run(Thread.java:472)

This looks like my WAS configuration is missing a jar file from the
classpath, but I did not make any modifications manually. The .java
source file generated by the compilation process is zero bytes in
length. Any suggestions?

- John Adkins
jadkins @ revenue.state.il.us

Ken Hygh

unread,
Mar 10, 2000, 3:00:00 AM3/10/00
to
John,
I understand there's a problem when upgrading from 3.0 to 3.02, where
a line in your admin.config is not updated. Make sure that
<wasroot>/AppServer/lib/jsp10.jar is in the classpath in your
admin.config.

Ken

0 new messages