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

Unable to retrieve JMS message; Caused by: Setting clientID on a used Connection is not allowed.

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Not A Problem
    • 5.15.13
    • None
    • Broker, JMS client
    • None

    Description

      In Dell Boomi we are using JMS connector with GET action for Active MQ to subscribe data from Topic using Durable Subscription Name. In connector we enabled Connection pool with Maximum idle time as 0 sec.

      And we tried to schedule process for every 1 min/2min/5min interval  but we see below error more frequently for every 3 execution we have this error for 2nd execution.

       

      Error Message :

      Unable to retrieve JMS message; Caused by: Setting clientID on a used Connection is not allowed.

       

      We also noticed all times process executing happening on specific node for both success and failure.

       

      We tired of few Active MQ properties to close connection like jms.closeTimeout but it doesn’t worked for us. So could you  please help us on this issue .

       

      Also, we have tested with disabling pooling and it worked fine .But for better performance we are needed pooling enable.

      And also idle time we have changed to 10000ms , 5000ms and tested but we see same issue in pooling enable mode.

      Please let me know in case if you need any other details.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mattrpav Matt Pavlovich
            ggirisatna@gmail.com Giridharan Jayaseelan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment