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 <priyank.sha...@orkash.com> wrote: > 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] notifyAgentWithStatus > ... Job Process State Changed - PID:4487. Process State: Running. JMX > Url:service:jmx:rmi:///jndi/rmi://S18:2105/jmxrmi Dispatched State Update > Event to Agent with IP:192.168.10.118 > Nov 21, 2017 6:30:13 PM org.apache.uima.adapter.jms.ac > tivemq.UimaDefaultMessageListenerContainer onException > WARNING: Service: SVODescriptor Runtime Exception > Nov 21, 2017 6:30:13 PM org.apache.uima.adapter.jms.ac > tivemq.UimaDefaultMessageListenerContainer onException > WARNING: Jms Listener Failed. Endpoint: SVOQueueNew Managed By: > tcp://S18:61617 Reason: org.apache.activemq.ConnectionFailedException: > The JMS connection has failed: Force close due to SecurityException on > connect > Nov 21, 2017 6:30:13 PM org.apache.uima.adapter.jms.ac > tivemq.UimaDefaultMessageListenerContainer handleListenerSetupFailure > WARNING: Uima AS Service:SVODescriptor Listener Unable To Connect To > Broker: tcp://S18:61617 Retrying Until Successful ... > Nov 21, 2017 6:30:13 PM org.apache.uima.adapter.jms.ac > tivemq.UimaDefaultMessageListenerContainer onException > WARNING: Service: SVODescriptor Runtime Exception > Nov 21, 2017 6:30:13 PM org.apache.uima.adapter.jms.ac > tivemq.UimaDefaultMessageListenerContainer onException > WARNING: Jms Listener Failed. Endpoint: SVOQueueNew Managed By: > tcp://S18:61617 Reason: javax.jms.JMSException: Stopped. > Nov 21, 2017 6:30:13 PM org.apache.uima.adapter.jms.ac > tivemq.UimaDefaultMessageListenerContainer handleListenerSetupFailure > WARNING: Uima AS Service:SVODescriptor Listener Unable To Connect To > Broker: tcp://S18:61617 Retrying Until Successful ... > 17/11/21 18:30:13 WARN activemq.UimaDefaultMessageListenerContainer: > Could not refresh JMS Connection for destination 'queue://SVOQueueNew' - > silently retrying in 5 ms. Cause: User name [null] or password is invalid. > > Thanks and Regards > Priyank Sharma > > On Tuesday 21 November 2017 04:56 PM, Lou DeGenaro wrote: > >> export UIMA_HOME=$DUCC_HOME/apache-uima >> > >
