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

Dismiss

WAS 3.5 OLT 4 -> Pages fail on debug mode & OLT runs but no debug occurs!

0 views

Skip to first unread message

Hertzel Karbasi

unread,

Jan 16, 2001, 1:53:36 PM1/16/01

to ch...@geocities.com, gp...@gpuri.com

Hello

As I see you have encountered a lot of problems concerning OLT.
Would you please try to help me with the following:

1.OLT 4 & OLD 8.5
2. The WAS AE 3.5.2 (NT) & HTTPserver 1.3.12 are local.
3. JDK 1.2.2
Java runs ok in command line and Java -version is:
JRE 1.2.2 IBM build wn122-20000720 (JIT enabled: jitc)
4. Admin.config has updated by:
com.ibm.ejs.sm.util.process.Nanny.path=
C\:\\WebSphere\\AppServer\\bin;C\:\\SQLLIB\\bin;C\:\\SQLLIB\\function;C\:\\WebSphere\\AppServer\\jdk\\bin;c:\\IBMDebug\\bin;

5. Default server is in debug enabled & OLT enabled, OLT server:
localhost,
port 2102, source path: the servlets & web path for default_app
6. OLT runs in command line and it's window pops up with:
Trace and debug, localhost, port 8001 & options: step by step
7. When i run a web page/servlet/jsp (in default server) in this mode i
get the follwong error.
when the same servlets/pages/jsps are ok in normal mode(no debug)
and no
error occurs.
In OLT nothing happens ! It does not debugs/traces the page !!!

Please your assitance
I think there is a problem with JDK in debug mode.

Thanks in advance
Hertzel

A recursive error was detected.
The server cannot use specified error page. Please check the application
error-path.
Original Error:
Error Message: Unable to compile class for JSP: null
Error Code: 500
Target Servlet: jsp10
Error Stack:

Root Error-1: Unable to compile class for JSP: null

com.ibm.servlet.engine.webapp.WebAppErrorReport: Unable to compile class
for JSP: null
at
com.ibm.servlet.engine.webapp.WebAppDispatcherResponse.sendError(WebAppDispatcherResponse.java:97)

at
com.sun.jsp.runtime.JspServlet.unknownException(JspServlet.java:656)
at com.sun.jsp.runtime.JspServlet.service(JspServlet.java:768)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:580)

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:353)

at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:729)

at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:655)

at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:338)

at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:175)

at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:93)

at SimpleJSPServlet.doGet(SimpleJSPServlet.java:40)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:580)