uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <...@uima.apache.org>
Subject [jira] [Updated] (UIMA-5747) UIMA-AS: Fix cause of the javax.jms.InvalidClientIDException in client code
Date Tue, 13 Mar 2018 18:09:01 GMT

     [ https://issues.apache.org/jira/browse/UIMA-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jerry Cwiklik updated UIMA-5747:
--------------------------------
    Summary: UIMA-AS: Fix cause of the javax.jms.InvalidClientIDException in client code 
(was: UIMA-AS: Fix the cause of the javax.jms.InvalidClientIDException in client code)

> UIMA-AS: Fix cause of the javax.jms.InvalidClientIDException in client code
> ---------------------------------------------------------------------------
>
>                 Key: UIMA-5747
>                 URL: https://issues.apache.org/jira/browse/UIMA-5747
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.10.2AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Major
>             Fix For: 2.10.3AS
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message