You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2018/03/13 15:33:00 UTC
[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&focusedCommentId=16397115#comment-16397115 ]
Burn Lewis commented on UIMA-5746:
----------------------------------
To reproduce first set the environment variable defaultBrokerURL, then register the service:
$DUCC_HOME/bin/ducc_services --register $DUCC_HOME/examples/simple/FixedSleep.service
then run the job twice:
$DUCC_HOME/bin/ducc_submit -f $DUCC_HOME/examples/simple/1.jms.job
$DUCC_HOME/bin/ducc_submit -f $DUCC_HOME/examples/simple/1.jms.job
> 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)