Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: Thu, 24 Mar 2005 18:34:40 +0100
Message-Id: <200503241734.j2OHYe4G024504@ajax.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 33810]  -
    Stream closed errors from JSP tags under load

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33810>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33810


------- Additional Comments From p_rudrakshala@yahoo.com  2005-03-24 18:34 -------
(In reply to comment #20)
> As I said, if you wanted to avoid this kind of problems (which I do not mind
> fixing), you should avoid using close inside your tags, which is completely
useless.

I am not asking you to fix my tags. These are standard jakarta tags from taglibs
project. Please take a look at the stack trace. These are from BodyContentImpl
class from jasper runtime. There are no close() calls from the tags. This is an
issue that is internal to Tomcat/Jasper most probably from pooling of jasper
runtime objects. The same application was working fine for years with Weblogic
servers. Can you explain why it would work for few hours and fail later? If it
is due to close() calls from tag implementation, it should fail all the time. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org