Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-9432

WebSocket transports close connection after 30 seconds due to default Jetty idle timeout

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 6.0.1
    • 6.1.0, 6.0.2
    • Transport
    • None
    • Patch Available
    • Patch

    Description

      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.

      Attachments

        1. disable-default-jetty-idle-timeout.patch
          9 kB
          Albertas Vyšniauskas

        Activity

          People

            jbonofre Jean-Baptiste Onofré
            thezbyg Albertas Vyšniauskas
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1h 20m
                1h 20m