Looks as if your service is still trying to use DUCC's broker on port 61617
... please ensure that your service is using the application broker's port
61616
~Burn
On Tue, Nov 21, 2017 at 8:03 AM, priyank sharma
wrote:
> Still Facing the same issue after starting the startBroker.sh.
>
> Logs fro
Still Facing the same issue after starting the startBroker.sh.
Logs from the service
DuccAbstractProcessContainer.deploy() User Container deployed
Deployed Processing Container - Initialization Successful - Thread 1
21 Nov 2017 18:30:13,072 INFO AgentSession - T[1] notifyAgentWit
>From DUCC Book:
-
5.5 Application Broker for UIMA-AS Services
UIMA-AS services require a separate ActiveMQ broker. An application broker
can be started using a script in the UIMA-AS distribution bundled with
DUCC.
export UIMA_HOME=$DUCC_HOME/apache-uima
$UIMA_HOME/bin/startBroker
Service logs
21 Nov 2017 14:32:57,227 INFO SM.ServiceHandler - N/A T[69]
runCommands Running 0 API Tasks.
21 Nov 2017 14:32:57,227 INFO SM.ServiceHandler - N/A T[69]
processUpdates Processing updates.
21 Nov 2017 14:32:57,227 INFO SM.ServiceSet - 18 T[69]
determinePingerStatus pinger dat
