Google Gruppi non supporta più i nuovi post o le nuove iscrizioni Usenet. I contenuti storici continuano a essere visibili.

Dismiss

JSP compilation fails in WAS3.5.0 AE

0 visualizzazioni

Passa al primo messaggio da leggere

Алексей Стыров

da leggere,

14 set 2001, 13:24:3714/09/01

Greetings, group!

I need any advice on the following situation. Call of JSP page create.jsp
fails in WAS 3.5.0 AE (OS is Win2k Professional
Russian). My JSP1.0 processor is default: com.sun.jsp.runtime.JspServlet.
I've traced this call and got the
trace log given below along with error stack trace and the source of that
JSP page. I've also put
the trace log of some well-compiled JSP, which I use in my webapp too. BTW,
this wab application works QUITE FINE
on Jakarta Tomcat

Does somebody have any suggestion on this point? Any advice appreciated.
Thanks in advance!

----------------------------------------------------------------------------
-------------------------------

The source of create.jsp

<%@ page session="true" contentType="text/html; charset=windows-1251" import
= "com.styrov.forum.*" %>
<HTML>
<HEAD>
<TITLE>
Title
</TITLE>
</HEAD>
<BODY BGCOLOR="#ffffc0">
<H1>
What's wrong with this page??
</H1>
<HR>

<% String id = (String)session.getAttribute("ID"); %>
<% if( id == null){ %>
<% id=""; %>
<% }
%>
<input type="hidden" name="id" value='<%= id %>'>
<BR><BR>
<INPUT TYPE="SUBMIT" NAME="Submit" VALUE="Send">
</form>
</BODY>
</HTML>

---------------------------------------------------------------

Trace of unsuccessful call of create.jsp
[01.09.14 09:07:49:730 GMT] 7e1a02d9 WebAppRequest >
WebAppRequestDispatcherInfo.calculateInfo()
[01.09.14 09:07:49:730 GMT] 7e1a02d9 WebAppRequest <
WebAppRequestDispatcherInfo.calculateInfo()
[01.09.14 09:07:49:730 GMT] 7e1a02d9 WebAppRequest >
WebAppRequestDispatcher.dispatch()
[01.09.14 09:07:49:730 GMT] 7e1a02d9 WebAppRequest D
WebAppRequestDispatcher.dispatch(): webapp request =
/webapp/SIForum/create.jsp
[01.09.14 09:07:49:730 GMT] 7e1a02d9 WebAppRequest D
WebAppRequestDispatcherInfo.getTargetServlet().getServletName(): JSP 1.0
Processor
[01.09.14 09:07:49:730 GMT] 7e1a02d9 WebAppRequest D
WebAppRequestDispatcher.dispatch(): forward attrib null, setting to current
servlet name
[01.09.14 09:07:49:730 GMT] 7e1a02d9 WebAppRequest >
WebAppRequestDispatcher.handleWebAppDispatch()
[01.09.14 09:07:49:730 GMT] 7e1a02d9 WebAppRequest D
WebAppRequestDispatcher.handleWebAppDispatch(): ref.servletname = JSP 1.0
Processor; ref.servletClassName com.sun.jsp.runtime.JspServlet
[01.09.14 09:07:51:352 GMT] 7e1a02d9 WebAppRequest <
WebAppRequestDispatcher.handleWebAppDispatch()
[01.09.14 09:07:51:362 GMT] 7e1a02d9 WebAppRequest <
WebAppRequestDispatcher.dispatch()
As you can see, no special info about jsp call fault...

------------------------------------------------------------------

The stack trace appearing in the browser window after an attempt to call the
create.jsp
com.sun.jsp.JspException: Compilation failed
at javax.servlet.ServletException.(ServletException.java:49)
at com.sun.jsp.JspException.(JspException.java:29)
at com.sun.jsp.compiler.Main.compile(Main.java:347)
at com.sun.jsp.runtime.JspLoader.compile(JspLoader.java:86)
at com.sun.jsp.runtime.JspLoader.loadJSP(JspLoader.java:210)
at
com.sun.jsp.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.
java:126)
at
com.sun.jsp.runtime.JspServlet$JspServletWrapper.service(JspServlet.java:137
)
at com.sun.jsp.runtime.JspServlet.serviceJspFile(JspServlet.java:505)
at com.sun.jsp.runtime.JspServlet.service(JspServlet.java:615)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:639)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:580)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:35
3)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:729)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:655)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebApp.java:1269)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebApp.java:1
106)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebApp.java:10
39)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebGroup.java:
646)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(Cacheabl
eInvocationContext.java:106)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:160)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQ
EventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventL
istenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQE
ventSource.java:202)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.notifyService(SQWrapperEventSource.java:347)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.run(SQWrapperEventSource.java:216)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run
(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)

----------------------------------------------------------------------------
--------------------------

On the other hand, "good" jsp files produce the following trace:
Trace of successful call of anotherJSP (view.jsp)
[01.09.14 09:10:34:807 GMT] 7e6202d9 WebAppRequest >
WebAppRequestDispatcherInfo.calculateInfo()
[01.09.14 09:10:34:807 GMT] 7e6202d9 WebAppRequest <
WebAppRequestDispatcherInfo.calculateInfo()
[01.09.14 09:10:34:807 GMT] 7e6202d9 WebAppRequest >
WebAppRequestDispatcher.dispatch()
[01.09.14 09:10:34:807 GMT] 7e6202d9 WebAppRequest D
WebAppRequestDispatcher.dispatch(): webapp request =
/webapp/SIForum/view.jsp
[01.09.14 09:10:34:807 GMT] 7e6202d9 WebAppRequest D
WebAppRequestDispatcherInfo.getTargetServlet().getServletName(): JSP 1.0
Processor
[01.09.14 09:10:34:807 GMT] 7e6202d9 WebAppRequest D
WebAppRequestDispatcher.dispatch(): forward attrib null, setting to current
servlet name
[01.09.14 09:10:34:807 GMT] 7e6202d9 WebAppRequest >
WebAppRequestDispatcher.handleWebAppDispatch()
[01.09.14 09:10:34:807 GMT] 7e6202d9 WebAppRequest D
WebAppRequestDispatcher.handleWebAppDispatch(): ref.servletname = JSP 1.0
Processor; ref.servletClassName com.sun.jsp.runtime.JspServlet
[01.09.14 09:10:35:028 GMT] 7e6202d9 HttpJspBase > init
[01.09.14 09:10:35:028 GMT] 7e6202d9 HttpJspBase < init
[01.09.14 09:10:35:028 GMT] 7e6202d9 HttpJspBase > service
[01.09.14 09:10:35:028 GMT] 7e6202d9 HttpJspBase D was.debug.enabled =
null
[01.09.14 09:10:35:218 GMT] 7e6202d9 HttpJspBase < service
[01.09.14 09:10:35:218 GMT] 7e6202d9 WebAppRequest <
WebAppRequestDispatcher.handleWebAppDispatch()
[01.09.14 09:10:35:218 GMT] 7e6202d9 WebAppRequest <
WebAppRequestDispatcher.dispatch()

0 nuovi messaggi