Re: Stream closed- IOException exception

2014-03-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Prashant, On 3/6/14, 12:43 AM, Prashant Kadam wrote: >> May be I failed to explain properly my understanding, I will >> explain the scenario once again No, I get it. You just aren't answering the questions I'm asking. >> I am including one jsp in

RE: Stream closed- IOException exception

2014-03-06 Thread Martin Gainty
> Date: Thu, 6 Mar 2014 11:13:22 +0530 > Subject: Re: Stream closed- IOException exception > From: prashantkada...@gmail.com > To: users@tomcat.apache.org > > On Wed, Mar 5, 2014 at 9:34 PM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > >

Re: Stream closed- IOException exception

2014-03-05 Thread Prashant Kadam
On Wed, Mar 5, 2014 at 9:34 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Prashant, > > On 3/5/14, 9:14 AM, Prashant Kadam wrote: > > On Wed, Mar 5, 2014 at 7:11 PM, Prashant Kadam > > wrote: > > > >> > >> > >> > >> On Mon, M

Re: Stream closed- IOException exception

2014-03-05 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Prashant, On 3/5/14, 9:14 AM, Prashant Kadam wrote: > On Wed, Mar 5, 2014 at 7:11 PM, Prashant Kadam > wrote: > >> >> >> >> On Mon, Mar 3, 2014 at 10:55 PM, Christopher Schultz < >> ch...@christopherschultz.net> wrote: >> > Prashant, > > On 3

Re: Stream closed- IOException exception

2014-03-05 Thread Prashant Kadam
On Wed, Mar 5, 2014 at 7:11 PM, Prashant Kadam wrote: > > > > On Mon, Mar 3, 2014 at 10:55 PM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> Prashant, >> >> On 3/3/14, 6:04 AM, Prashant Kadam wrote: >> > please help ... I

Re: Stream closed- IOException exception

2014-03-05 Thread Prashant Kadam
On Mon, Mar 3, 2014 at 10:55 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Prashant, > > On 3/3/14, 6:04 AM, Prashant Kadam wrote: > > please help ... I have removed whitespaces by adding > > *.jsp > > true > > but still

Re: Stream closed- IOException exception

2014-03-03 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Prashant, On 3/3/14, 6:04 AM, Prashant Kadam wrote: > please help ... I have removed whitespaces by adding > *.jsp > true > but still i am facing same > error. This may or may not do anything. > I tried to increase the buffer size also as,

Re: Stream closed- IOException exception

2014-03-03 Thread Konstantin Kolinko
2014-03-03 15:04 GMT+04:00 Prashant Kadam : > > stuck on this issue for more than 2 weeks now and need to close it ASAP > please help. > Any help/ pointer would be highly appreciated. > If nothing else helps, try running with a debugger to find when the said response is being committed. https://w

Re: Stream closed- IOException exception

2014-03-03 Thread Prashant Kadam
please help ... I have removed whitespaces by adding *.jsp true but still i am facing same error. I tried to increase the buffer size also as, <%@ page buffer="800kb" autoFlush="false" %> but still same error stuck on this issue for more than 2 weeks no

Re: Stream closed- IOException exception

2014-03-02 Thread Prashant Kadam
On Sat, Mar 1, 2014 at 1:33 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Prashant, > > On 2/28/14, 7:54 AM, Prashant Kadam wrote: > > thanks Mark and Konstantin for your reply > > > > If you create the simplest possible JSP

Re: Stream closed- IOException exception

2014-02-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Prashant, On 2/28/14, 7:54 AM, Prashant Kadam wrote: > thanks Mark and Konstantin for your reply > > If you create the simplest possible JSP that demonstrates the > issue (start with the one you have and remove as much as you can) > and then post t

Re: Stream closed- IOException exception

2014-02-28 Thread Prashant Kadam
thanks Mark and Konstantin for your reply If you create the simplest possible JSP that demonstrates the issue (start with the one you have and remove as much as you can) and then post that JSP here, we can take a look. >> as you can see in stacktrace, there are many jsps forwarding request to ano

Re: Stream closed- IOException exception

2014-02-28 Thread Prashant Kadam
also for other navigation in my application, i can see below exception line with all the already posted stack trace ... javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: org.apache.jasper.JasperException: java.lang.IllegalStateException: Exception occu

Re: Stream closed- IOException exception

2014-02-28 Thread Prashant Kadam
Please find below stack trace Feb 28, 2014 4:50:10 PM org.apache.catalina.core.ApplicationDispatcher invoke SEVERE: Servlet.service() for servlet jsp threw exception java.io.IOException: Stream closed at org.apache.jasper.runtime.JspWriterImpl.ensureOpen(JspWriterImpl.java:210) at org.apa

Re: Stream closed- IOException exception

2014-02-28 Thread Konstantin Kolinko
2014-02-28 13:11 GMT+04:00 Prashant Kadam : > Hi > > I am in process of upgrading from tomcat 7.0.33 to 7.0.52 but I am facing > IOException: Stream closed in one of the layout jsp. Underlying exception > is jasper exception - *org.apache.jasper.JasperException: > java.lang.IllegalStateException

Re: Stream closed- IOException exception

2014-02-28 Thread Mark Thomas
On 28/02/2014 09:11, Prashant Kadam wrote: > Hi > > I am in process of upgrading from tomcat 7.0.33 to 7.0.52 but I am facing > IOException: Stream closed in one of the layout jsp. Underlying exception > is jasper exception - *org.apache.jasper.JasperException: > java.lang.IllegalStateException

Stream closed- IOException exception

2014-02-28 Thread Prashant Kadam
Hi I am in process of upgrading from tomcat 7.0.33 to 7.0.52 but I am facing IOException: Stream closed in one of the layout jsp. Underlying exception is jasper exception - *org.apache.jasper.JasperException: java.lang.IllegalStateException: Response has already been committed*. Same code is w