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

IllegalMonitorStateException in default topic consumer of maven-activemq-perf-plugin

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.4.2
    • Fix Version/s: 5.5.0
    • Component/s: Performance Test
    • Labels:
    • Environment:

      maven-activemq-perf-plugin

      Description

      Running

      mvn activemq-perf:consumer -Dfactory.brokerURL=tcp://localhost:61616 
      -Dconsumer.destName=topic://Test -Dconsumer.sessAckMode=autoAck -Dconsumer.recvType=count 
      

      generates

      Exception in thread "JmsConsumer0 Thread" java.lang.IllegalMonitorStateException
              at java.lang.Object.wait(Native Method)
              at java.lang.Object.wait(Object.java:485)
              at org.apache.activemq.tool.JmsConsumerClient.receiveAsyncCountBasedMessages(JmsConsumerClient.java:176)
              at org.apache.activemq.tool.JmsConsumerClient.receiveMessages(JmsConsumerClient.java:54)
              at org.apache.activemq.tool.JmsConsumerClient.receiveMessages(JmsConsumerClient.java:67)
              at org.apache.activemq.tool.JmsConsumerClient.receiveMessages(JmsConsumerClient.java:72)
              at org.apache.activemq.tool.JmsConsumerSystem.runJmsClient(JmsConsumerSystem.java:62)
              at org.apache.activemq.tool.AbstractJmsClientSystem$1.run(AbstractJmsClientSystem.java:85)
              at java.lang.Thread.run(Thread.java:619)
      

      Using -Dconsumer.asyncRecv=false resolves the problem.

        Attachments

          Activity

            People

            • Assignee:
              tabish Timothy A. Bish
              Reporter:
              tmielke Torsten Mielke

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment