You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2024/02/28 15:08:00 UTC

[jira] [Assigned] (AMQ-9432) WebSocket transports close connection after 30 seconds due to default Jetty idle timeout

     [ https://issues.apache.org/jira/browse/AMQ-9432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré reassigned AMQ-9432:
-----------------------------------------

    Assignee: Jean-Baptiste Onofré

> 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
>  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)