"aaime74" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > > > Johnny Kewl wrote: >> >> This is an interesting question, and I'm going to "guess"... >> If you in a JSP page, I dont think the error can be trapped. >> >> If you in a servlet, yes I think a try catch will detect it, but only if >> you >> actually write something. >> > > Which I can't do. The WMS is an international standard, I cannot bend it > to my will, since the point of the application is to be fully conformant > to > it. > > This is a pity, I mean, the webapp container should have a way to check > the socket is gone bye bye without writing on it, no? >
No, the Servlet-API doesn't have a mechanism to asynchronously notify a Servlet about much of anything (since all communication is required to take place on one thread). As Johnny mentioned before, you might be able to do this in Tomcat 6 by using the AIO (aka Comet) features. With the standard Servlet interface, Tomcat won't even look at the Socket until you decide to do a read/write, so will have no idea that the Socket is dead until then. Google on things like "Comet" and "Ajax", and ask your doctor if it might be right for you ;-). > Cheers > Andrea > -- > View this message in context: > http://www.nabble.com/Any-way-to-check-the-client-abruptly-close-the-connection--tf4043946.html#a11496790 > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
