Uploaded image for project: 'UIMA'
  1. UIMA
  2. UIMA-5747

UIMA-AS: Fix cause of the javax.jms.InvalidClientIDException in client code

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.10.2AS
    • 2.10.3AS
    • Async Scaleout
    • None

    Description

      UIMA-AS client code recently introduced naming of JMS client when creating broker connection. The code in question:

      connection.setClientID("ClientListener");

      This code was added to help identify uima-as connections during debugging. 

      The problem with the above is that the name is static. The first application succeeds. Any subsequent application launched in a separate process will fail since the JMS spec says that the ClientID must be unique.

      Fix the code to make ClientID unique.

      Attachments

        Activity

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

          People

            cwiklik Jaroslaw Cwiklik
            cwiklik Jaroslaw Cwiklik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment