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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10.2AS
• Fix Version/s: 2.10.3AS
• Component/s: Async Scaleout
• Assignee: Jaroslaw Cwiklik
• Reporter: Jaroslaw Cwiklik
• Created: 13/Mar/18 18:08
• Updated: 15/Mar/18 22:39
• Resolved: 15/Mar/18 22:39

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.