[
https://issues.apache.org/jira/browse/AMQ-9432?focusedWorklogId=907367&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-907367
]
ASF GitHub Bot logged work on AMQ-9432:
---------------------------------------
Author: ASF GitHub Bot
Created on: 28/Feb/24 15:08
Start Date: 28/Feb/24 15:08
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1155:
URL: https://github.com/apache/activemq/pull/1155#issuecomment-1969189326
As the idle timeout set to 30s by default has been introduced in Jetty 10.
So it makes sense to force it in ActiveMQ to be consistent with previous
version. Being able to configure the timeout can be in another PR.
Issue Time Tracking
-------------------
Worklog Id: (was: 907367)
Time Spent: 1h 10m (was: 1h)
> 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 10m
> 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)
