cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andriy Redko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5417) Support optional JAX-RS 2.0 ConnectionCallback
Date Fri, 17 Jan 2014 02:01:25 GMT

    [ https://issues.apache.org/jira/browse/CXF-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874312#comment-13874312
] 

Andriy Redko commented on CXF-5417:
-----------------------------------

Hi Sergey,

It seems like Tomcat 7 is a bit more detailed: I was able to catch ClientAbortException steadily
in case when client disconnects. I also re-tested with Jetty (sorry, I had a small bug in
the code), and in most cases I was able to receive EofException in the same situation, when
client disconnects abruptly. The open question is: we still need to send something because
flush() may work or may not - it depends if there is something to flush or not. When server
has nothing to flush, exception is not thrown because basically communication is not happening.
Still, Jetty's EofException is not  very obvious to treat is as disconnection. 

What do you think?
Thanks.

Andriy

> Support optional JAX-RS 2.0 ConnectionCallback
> ----------------------------------------------
>
>                 Key: CXF-5417
>                 URL: https://issues.apache.org/jira/browse/CXF-5417
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS, Transports
>            Reporter: Sergey Beryozkin
>            Priority: Minor
>
> https://jax-rs-spec.java.net/nonav/2.0/apidocs/javax/ws/rs/container/ConnectionCallback.html
> lets JAX-RS 2.0 applications receive the notifications when a given client has disconnected.
> We can probably build something on top of the Jetty-specific connector and also enhance
CXF Continuation API. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message