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] [Commented] (UIMA-5746) DUCC jobs that use a JMS service descriptor no longer work
Date Tue, 13 Mar 2018 17:36:00 GMT

    [ https://issues.apache.org/jira/browse/UIMA-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
> WARNING: Top Level Controller Initialization Exception.
> javax.jms.InvalidClientIDException: Broker: localhost - Client: ClientListener already
connected from tcp://

This message was sent by Atlassian JIRA

View raw message