Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-4224

SetClientID does not have an effect

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 0.14
    • None
    • Broker-J
    • Windows 7 64-bit, Java 1.6

    Description

      Hi everyone,
      I am currently evaluating QPID and AMQP in general. I have a JMS test application that works perfectly on a JMS compliant broker (non AMQP) and now I am trying to port it to QPID using only JMS features. Unfortunately I am having problems changing the client ID. I am aware that I can specify it in the AMQ://... string on startup, but since I want to read that string from a single .properties file, that is not a nice solution for 200 clients in parallel. Instead I tried using the setClientID method and setting the ignore_setClientID flag. The only effect this had was to ignore the error that is normally thrown.

      Below you can see the source code that basically does nothing other than reporting the requested ID change. Is there any workaround or solution to this problem??
      Thank you very much for your support,
      Holger

      public void setClientID(String clientID) throws JMSException
      {
      checkNotClosed();
      // in AMQP it is not possible to change the client ID. If one is not specified
      // upon connection construction, an id is generated automatically. Therefore
      // we can always throw an exception.
      if (!Boolean.getBoolean(ClientProperties.IGNORE_SET_CLIENTID_PROP_NAME))

      { throw new IllegalStateException("Client name cannot be changed after being set"); }

      else

      { _logger.info("Operation setClientID is ignored using ID: " + getClientID()); }

      }

      Attachments

        Activity

          People

            Unassigned Unassigned
            night Holger Caesar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 96h
                96h
                Remaining:
                Remaining Estimate - 96h
                96h
                Logged:
                Time Spent - Not Specified
                Not Specified