4 Replies Latest reply on Sep 15, 2010 9:43 AM by Aspi Engineer

    Unable to call setClientId after getClientId

    Aspi Engineer Newbie



      The HQ JMS connection class (HornetQConnection.java) currently will throw an "IllegalStateException" exception if the sequence of events is:

      - create a connection

      - call getClientId

      - call setClientId


      This seems like a defect, or at best, a restriction that serves no purpose. The getClientID method sets the "justCreated" flag to false. Can this method be changed to not set "justCreated = false"?


      Why? We are using a third party ESB product and would like to integrate HQ with it. The third party product executes calls in the sequence:

      - create connection

      - getClientId

      - setClientId


      Since HQ does not allow this sequence of API calls, integration of HQ with the third party product fails.



      Aspi Engineer

      Putnam Investments