ActiveMQ
  1. ActiveMQ
  2. AMQ-2169

Web Console spawns new threads for every refresh and never kills any

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.3.0
    • Component/s: None
    • Labels:
      None
    • Environment:

      Red Hat x86_64, 2.6.9-55 kernel
      Web console enabled (started in the same process as the broker)

      Description

      How to reproduce:

      • Use JMX to look at the threads.
      • Open the web console gui and hit refresh.

      For every refresh 1-2 new threads are spawned. These are never closed/killed and after a while the broker becomes unresponsive. (For us this happens after about 180-200 threads which corresponds to hitting refresh repeatedly for about one minute.)

      The threads are named ActiveMQ Session ID:someId and is of type DedicatedTaskRunner.

        Activity

        Erik Drolshammer created issue -
        Erik Drolshammer made changes -
        Field Original Value New Value
        Summary Web Console spaws new threads for every refresh and never kills any Web Console spawns new threads for every refresh and never kills any
        Hide
        Benjamin Darfler added a comment -

        I would love to get some movement on this! I was using the web console to fix https://issues.apache.org/activemq/browse/AMQ-1112

        Show
        Benjamin Darfler added a comment - I would love to get some movement on this! I was using the web console to fix https://issues.apache.org/activemq/browse/AMQ-1112
        Hide
        Gary Tully added a comment -

        scheduling for 5.3

        Show
        Gary Tully added a comment - scheduling for 5.3
        Gary Tully made changes -
        Fix Version/s 5.3.0 [ 11914 ]
        Gary Tully made changes -
        Assignee Gary Tully [ gtully ]
        Hide
        Gary Tully added a comment -

        scope of spring mvc beans was incorrect, should have been scope="request". Updated config to match changed in activemq-web-console. The duplication (which is not good) is the result of the broker config and properties files needing to be installation aware. Hense a distribution needs a separate file.

        Show
        Gary Tully added a comment - scope of spring mvc beans was incorrect, should have been scope="request". Updated config to match changed in activemq-web-console. The duplication (which is not good) is the result of the broker config and properties files needing to be installation aware. Hense a distribution needs a separate file.
        Gary Tully made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Hide
        Gary Tully added a comment -

        small update. pulled the query beans into their own file and include via import so that the duplication is removed.

        Show
        Gary Tully added a comment - small update. pulled the query beans into their own file and include via import so that the duplication is removed.
        Jeff Turner made changes -
        Project Import Fri Nov 26 22:32:02 EST 2010 [ 1290828722158 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        89d 23h 53m 1 Gary Tully 17/Jun/09 15:58

          People

          • Assignee:
            Gary Tully
            Reporter:
            Erik Drolshammer
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development