[
https://issues.apache.org/jira/browse/CAMEL-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254927#comment-15254927
]
Daniel Tremblay commented on CAMEL-7612:
----------------------------------------
Camel doesn't set the time at the appropriate time for Jetty to use, so it
doesn't work. You are better off using the Jetty component directly. Claus:
pointing the other way is just not the right way to approach this problem.
I've had this problem in Camel since version 2.12.
> Setting maxIdleTime in endpoint
> -------------------------------
>
> Key: CAMEL-7612
> URL: https://issues.apache.org/jira/browse/CAMEL-7612
> Project: Camel
> Issue Type: Bug
> Components: camel-websocket
> Affects Versions: 2.12.3
> Environment: Linux CentOS 6.5, OpenJDK 1.7.0.55.x86_64, WebBrowser:
> Chromium 31.0.1650.63, ServiceMix 5.0.0
> Reporter: Daniel Tremblay
> Priority: Minor
>
> I created a camel-websocket endpoint with this uri:
> websocket:/alerts?maxIdleTime=30000.
> The websocket is successfully created on the browser and messages can flow
> back and forth. The maxIdleTime should be 30 seconds. However it times out
> at 300 seconds (5 minutes).
> My initial goal was to set the timeout to 15 minutes, instead of the default
> 5 minutes, but changing this setting does not seem to change the default.
> I've modified the camel-websocket component to set the maxIdleTime on the
> controller, but this doesn't work either. I'm not sure if the error is in
> Jetty or Camel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
