You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/01/23 15:35:39 UTC
DO NOT REPLY [Bug 16363] New: -
Stack Overflow accessing compiled JSP - Tomcat 3.2.4 and JDK 1.4.1
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16363>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16363
Stack Overflow accessing compiled JSP - Tomcat 3.2.4 and JDK 1.4.1
Summary: Stack Overflow accessing compiled JSP - Tomcat 3.2.4 and
JDK 1.4.1
Product: Tomcat 3
Version: 3.2.3 Final
Platform: All
OS/Version: Other
Status: NEW
Severity: Critical
Priority: Other
Component: Unknown
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: rob@relicore.com
We're running a standalone Tomcat 3.2.4 installation (yes, I know I marked this
as 3.2.3 Final, but there's no option for 3.2.4 Final) under Sun JDK 1.4.1
(Win2K or Solaris 2.8), with the jar files containing our code having been
compiled under Sun JDK 1.3.1. Hitting a certain page will invariably cause a
Stack Overflow. I was able to capture one in-progress:
"Thread-28" prio=5 tid=0x24C65070 nid=0x698 runnable [2bb4c000..2bb4fd8c]
at java.lang.Class.getName(Native Method)
at org.apache.tomcat.core.ContextManager.handleError
(ContextManager.java:1146)
at org.apache.tomcat.core.Handler.service(Handler.java:312)
at org.apache.tomcat.core.ServletWrapper.service
(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.handleError
(ContextManager.java:1177)
...
at org.apache.tomcat.core.Handler.service(Handler.java:312)
at org.apache.tomcat.core.ServletWrapper.service
(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.handleError
(ContextManager.java:1177)
at org.apache.tomcat.core.Handler.service(Handler.java:312)
at org.apache.tomcat.core.ServletWrapper.service
(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.handleError
(ContextManager.java:1177)
at org.apache.tomcat.core.ContextManager.service
(ContextManager.java:759)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection
(HttpConnectionHandler.java:213)
at org.apache.tomcat.service.TcpWorkerThread.runIt
(PoolTcpEndpoint.java:416)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run
(ThreadPool.java:501)
at java.lang.Thread.run(Thread.java:536)
The "..." is mine - the trace was 250 lines long when I nabbed it.
The page that seems to trigger it has the following general structure:
=====================
<%@ page language="java" contentType="text/html"%>
<%@ page import blah blah blah%>
<%@ include file="newToolbarSetup.jsp"%>
<%
java code
%>
<HTML>
<HEAD>
blah blah blah
</HEAD>
<%@ include file="newToolbar.jsp"%>
</HTML>
=====================
newToolbarSetup.jsp is as follows:
<%@ page errorPage="badstate.jsp?debug=log" %>
<%
various Java code setting attrs on request and response and
doing some calculation and variable definition
%>
=====================
newToolbar.jsp is as follows:
<%
java code
%>
<BODY>
stuff
</BODY>
=====================
badstate.jsp is as follows:
<%@ page language="java" contentType="text/html" %>
<%@ page import blah blah blah%>
<%@ page isErrorPage="true" %>
<%
java code
%>
<HTML>
<HEAD>
stuff
</HEAD>
<BODY>
stuff
</BODY>
</HTML>
=====================
This worked fine under Tomcat 3.2.4 and JDK 1.3.1, and broke immediately when
we switched to JDK 1.4.1. As an experiment, I subbed JDK 1.3.1 back in,
deleted all of the files in my work directory, and verified that it still works
under 1.3.1. Then, if I delete the work files again and sub 1.4.1 back in, it
breaks again. So it looks like a Tomcat 3.2.4/JDK 1.4.1 incompatibility. But
I've been unable to find anything documented.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>