[jira] [Updated] (UIMA-5747) UIMA-AS: Fix cause of the javax.jms.InvalidClientIDException in client code
[
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)
[jira] [Created] (UIMA-5747) UIMA-AS: Fix the cause of the javax.jms.InvalidClientIDException in client code
Jerry Cwiklik created UIMA-5747:
---
Summary: UIMA-AS: Fix the 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
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)
[jira] [Commented] (UIMA-5746) DUCC jobs that use a JMS service descriptor no longer work
[
https://issues.apache.org/jira/browse/UIMA-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397337#comment-16397337
]
Jerry Cwiklik commented on UIMA-5746:
-
The error is caused by UIMA-AS client bug. The code is assigning a static name
to a broker connection via Connection.setClientID("ClientListener");
If one application that uses UIMA-AS client is launched all is well. Any
additional application launched in a separate process will fail since the JMS
ClientID must be unique according to the JMS spec. The naming of a connection
was added in UIMA-AS 2.10.2 as means to identify connections during debugging.
Within the same process one can have many UIMA-AS clients, since all of them
use a shared connection to the broker.
There is nothing to fix in DUCC for this. The bug is in the UIMA-AS 2.10.2.
> DUCC jobs that use a JMS service descriptor no longer work
> --
>
> Key: UIMA-5746
> URL: https://issues.apache.org/jira/browse/UIMA-5746
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
>Reporter: Burn Lewis
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> Any JPs after first get:
> Mar 12, 2018 3:38:19 PM
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
> notifyOnInitializationFailure
> WARNING: Top Level Controller Initialization Exception.
> javax.jms.InvalidClientIDException: Broker: localhost - Client:
> ClientListener already connected from tcp://192.168.3.13:46402
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (UIMA-5746) DUCC jobs that use a JMS service descriptor no longer work
Burn Lewis created UIMA-5746: Summary: DUCC jobs that use a JMS service descriptor no longer work Key: UIMA-5746 URL: https://issues.apache.org/jira/browse/UIMA-5746 Project: UIMA Issue Type: Bug Components: DUCC Reporter: Burn Lewis Fix For: 2.2.2-Ducc Any JPs after first get: Mar 12, 2018 3:38:19 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl notifyOnInitializationFailure WARNING: Top Level Controller Initialization Exception. javax.jms.InvalidClientIDException: Broker: localhost - Client: ClientListener already connected from tcp://192.168.3.13:46402 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: board report due for March
Here's the proposed board report (to be submitted later today). Let me know of any changes needed. Thanks! -Marshall Board report for Apache UIMA, for March 2018. Apache UIMA's mission: the creation and maintenance of open-source software related to the analysis of unstructured data, guided by the UIMA Oasis Standard. Dates: 05 Mar 2018 (new) last release - UIMA Java SDK 3.0.0 03 May 2016 (no change) last PMC addition 18 Apr 2017 (no change) last Committer addition Releases: 05 Mar 2018 Apache UIMA Java SDK 3.0.0 07 Feb 2018 Apache UIMA Asynchronous Scaleout (UIMA-AS) 2.10.2 Activity: Java SDK, UIMA-AS, DUCC, RUTA are actively being worked on. The Java SDK version 3.0.0 was finally released after an extensive ramp up involving 2 alpha releases and one beta release. Our last committer addition was William Colen, who is contributing to the C++ implementation of the UIMA framework. Mailing list activity remains moderate. Community: The community continues to be moderately active. There has been a bit of discussion around moving more to GIT; some are in favor; others feel it would be a significant workload increase for which they don't have time. Issues: No Board level issues at this time.
