[
https://issues.apache.org/jira/browse/AMQ-9432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821711#comment-17821711
]
ASF subversion and git services commented on AMQ-9432:
------------------------------------------------------
Commit b2a808466d6ec4412c9a6d6162ccf29fd4a0225f in activemq's branch
refs/heads/activemq-6.0.x from Albertas Vyšniauskas
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=b2a808466 ]
AMQ-9432 Disable default Jetty WebSocket idle timeout
(cherry picked from commit 2ddc3c07466feb087a4d25958c0f45116eb8d0ca)
> WebSocket transports close connection after 30 seconds due to default Jetty
> idle timeout
> ----------------------------------------------------------------------------------------
>
> Key: AMQ-9432
> URL: https://issues.apache.org/jira/browse/AMQ-9432
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Transport
> Affects Versions: 6.0.1
> Reporter: Albertas Vyšniauskas
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Attachments: disable-default-jetty-idle-timeout.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Hello,
> after update to ActiveMQ 6.0.1, WebSocket based transports unexpectedly close
> after 30 seconds of inactivity. This is caused by Jetty update, because after
> version 10.0 default idle timeout is set to 30 seconds (see
> [https://github.com/jetty/jetty.project/commit/7e5dcda7085ce2267d4db1598d12a4aa89db5107).]
> In previous versions idle timeout was disabled by default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
