[
https://issues.apache.org/jira/browse/CAMEL-10283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-10283.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.18.0
There is a new sendTimeout option using 30 seconds by default.
This uses the async send api which requires Jetty 9.x, and therefore can only
be implemented from Camel 2.18 onwards where we upgraded jetty from 8 to 9 in
the websocket component.
> Add a timeout on WebSocketProducer sendMessages method
> ------------------------------------------------------
>
> Key: CAMEL-10283
> URL: https://issues.apache.org/jira/browse/CAMEL-10283
> Project: Camel
> Issue Type: Wish
> Components: camel-websocket
> Affects Versions: 2.17.2
> Environment: Ubuntu 14.04, full java project using camel-websockets
> Reporter: Jeremy
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 2.18.0
>
>
> We are encountering a problem with websocket component when our clients using
> web browsers are brutally loosing connection (closing laptop most of time).
> When we are sending updates from server to all clients, the WebSocketProducer
> iterate over all opened sockets and when it reaches the broken socket, it is
> just waiting for the idleTimeout to happen.
> At this step, the others clients are not able to interact with the server
> anymore cause the websocket producer is busy waiting on the broken socket and
> can't send messages to other clients.
> I'm looking for a work-around or something... maybe the ability to set a
> timeout on the client handshake when sending... I'm not an expert in network
> protocols.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
