Thank you some much for your help in such a short time.
Thank you for showing me the right direction to work on.

On Wed, Sep 8, 2010 at 11:39 PM, Maximilian Stocker 
<m...@talentoyster.com>wrote:

> Tomcat is *not* getting stuck.
>
> There is a bug in com.infodata.ifs.core.IFSCoreServlet which is attempting
> to send an HTTP error *after* content has already been sent.
>
> On the otherwise this powerbuilder or whatever client is waiting for data
> that is never going to come because the application itself has error-ed out.
>
> The reason that restarting tomcat is "fixing" the issue is that is closing
> the socket etc and the client app assumes the connection is dead and
> retries.
>
> In short this is 100% an application programming error and you are in the
> wrong place to get help with it. Go start with finding and fixing (or
> reporting or whatever it is you need to do) the bug in
> com.infodata.ifs.core.IFSCoreServlet
>
> -----Original Message-----
> From: Sumeet Chitte [mailto:chittesum...@gmail.com]
>  Sent: Wednesday, September 08, 2010 2:03 PM
> To: Tomcat Users List; jba...@javasystemsolutions.com
> Subject: Re: Tomcat 5.0 which gets stuck
>
> Thank you for your response.
>
> I will tell you some more details.
>
> We are using an Powerbuilder application which calls the documents from
> server.
>
> This server uses a third party tool, which uses Apache Tomcat 5.0.
>
> What happens is that this Tomcat service gets stuck sometimes and the
> Powerbuilder application gets frozens because of this. If we go to the
> services it shows that the Tomcat services is still running but if we stop
> and restart this service the issue is resolved.
>
> Hope it gives you some more idea about the problem.
>
> On Wed, Sep 8, 2010 at 10:20 PM, John Baker
> <jba...@javasystemsolutions.com>wrote:
>
> > I thought an illegal state exception would occur if an attempt was made
> to
> > write to a socket that's now shut but you are right, it looks more like
> an
> > attempt to perform an internal redirect after response has been committed
> > (although that message should appear in the logs).
> >
> > -----Original Message-----
> > From: Maximilian Stocker <m...@talentoyster.com>
> > Date: Wed, 8 Sep 2010 12:43:01
> > To: 'Tomcat Users List'<users@tomcat.apache.org>
> >  Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
> > Subject: RE: Tomcat 5.0 which gets stuck
> >
> > I don't know what you mean by "We are using Apache Tomcat 5.0 which gets
> > stuck sometimes and needs a stop and restart" but the stack trace you
> posted
> > is almost certainly evidence of a bug in your code.
> >
> > It's an illegal state exception to try and send an error if you have
> > already sent "normal" content in some way. Which you almost certainly
> have.
> >
> > So the stack trace shows a bug in your code. But what do you mean that
> > tomcat "gets stuck"? What exact symptoms does this display.
> >
> > As to the other poster I am not sure what sort of guess that was but
> there
> > is nothing in that stack trace relating to broken pipes, timeouts, broken
> > sockets etc. This is an HTTP protocol error (caused by poorly written
> code)
> > not a TCP level error.
> >
> > -----Original Message-----
> > From: Sumeet Chitte [mailto:chittesum...@gmail.com]
> > Sent: Wednesday, September 08, 2010 12:19 PM
> > To: users@tomcat.apache.org
> > Subject: Fwd: Tomcat 5.0 which gets stuck
> >
> >  Hi,
> >
> > We are using Apache Tomcat 5.0 which gets stuck sometimes and needs a
> stop
> > and restart.  We are using Microsoft Windows 2000 Service Pack 4.
> >
> > Below is the error from the log file,
> >
> > Kindly provide some solution.
> >
> > 2010-09-07 10:33:38 StandardWrapperValve[IFSCoreServlet]:
> Servlet.service()
> > for servlet IFSCoreServlet threw exception
> > java.lang.IllegalStateException
> >  at
> >
> >
> org.apache.coyote.tomcat5.CoyoteResponseFacade.sendError(CoyoteResponseFacade.java:324)
> >  at
> > com.infodata.ifs.core.IFSCoreServlet.sendError(IFSCoreServlet.java:1159)
> >  at
> com.infodata.ifs.core.IFSCoreServlet.service(IFSCoreServlet.java:1057)
> >  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> >  at
> >
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
> >  at
> >
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
> >  at
> >
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
> >  at
> >
> >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> >  at
> >
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> >  at
> >
> >
> org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
> >  at
> >
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
> >  at
> >
> >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> >  at
> >
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> >  at
> >
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
> >  at
> >
> >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> >  at
> >
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
> >  at
> >
> >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
> >  at
> >
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> >  at
> >
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> >  at
> >
> >
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
> >  at
> >
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
> >  at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
> >  at
> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
> >  at
> >
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
> >
> > --
> > Thanks & Regards,
> > Sumeet G. Chitte | Software Engineer,
> > IBM,EGL 'A' Block, Off Indiranagar,
> > Kormagala Intermediate Ring Road,
> > Bangalore : 560071
> > Mail: suchi...@in.ibm.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >
>
>
> --
> Thanks & Regards,
> Sumeet G. Chitte | Software Engineer,
> IBM,EGL 'A' Block, Off Indiranagar,
> Kormagala Intermediate Ring Road,
> Bangalore : 560071
> Mail: suchi...@in.ibm.com
> Mob: 09620902544,09922922911.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>


-- 
Thanks & Regards,
Sumeet G. Chitte | Software Engineer,
IBM,EGL 'A' Block, Off Indiranagar,
Kormagala Intermediate Ring Road,
Bangalore : 560071
Mail: suchi...@in.ibm.com
Mob: 09620902544,09922922911.

Reply via email to