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

Deadlock using JMX & copyMatchingMessagesTo

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 5.10.0
    • Fix Version/s: None
    • Component/s: JMX
    • Labels:
      None
    • Environment:

      Description

      Today we had an issue relating to a consumer that was somehow not properly ack'ing messages and letting the queue grow.

      We had the idea to use JMX operations to move messages we knew had been delivered and processed, but before hand tried to copy a few of the messages to a new destination to confirm using a selector of "JMSTimestamp<[timestampAsLongValueOfYesterdayMorning]" (obviously a long-based timestamp I've since forgotten to write down.

      I tested the Selector with a browse(String selector) operation, and that successfully returned the small handful easily.

      I invoked the copyMatchingMessagesTo Operation on the Queue JMX operation, and the attached Thread Deadlock occurred. At the time there were around 20,000 messages in the queue, all very small in size.(roughly 1k each as reported by the JMX averageMessageSize property)

      This doesn't give us much confidence in the ability to use Operational JMX to recover from strange scenarios. The total number of messages being copied was a small handful, 5-20 at most.

        Attachments

        1. amq_jstack.txt
          659 kB
          Paul Smith

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              psmith@apache.org Paul Smith
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: