Re: IOException with Tomcat Comet during write/flush

ok, if the stack trace comes from an async thread, then it just means the CometEvent is closed and has been recycled Filip On 08/14/2009 06:01 PM, Jason Ward wrote: Filip - everything below that is from our (proprietary) classes. I'll see if I can extract it into a standalone project or at lea

Re: IOException with Tomcat Comet during write/flush

Filip - everything below that is from our (proprietary) classes. I'll see if I can extract it into a standalone project or at least clean it to the point where I can distribute. Hope to get that to you on Monday. As I said tho, the crux of the problem is coming from the first ioex which doesn'

Re: IOException with Tomcat Comet during write/flush

don't clip the stack trace please, do you have the full one? On 08/14/2009 03:24 PM, Jason Ward wrote: Hello, I'm seeing IOExceptions when writing/flushing my Comet servlet OutputStream. The fist exception is difficult to pinpoint, but it seems it raises and ERROR event which ultimately enact

IOException with Tomcat Comet during write/flush

Hello, I'm seeing IOExceptions when writing/flushing my Comet servlet OutputStream. The fist exception is difficult to pinpoint, but it seems it raises and ERROR event which ultimately enacts a event.close(). This in turn results in the following stack trace for subsequent operations: java.l