[jira] Closed: (UIMA-1702) Service fails to start when the broker of one of its delegates is missing

["Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-1702.
-------------------------------

    Resolution: Fixed

Fixed to detect broker failure on service startup and either disable the delegate (and a listener) or terminate the service. Which action is taken depends on error handling configuration defined in the deployment descriptor.

> Service fails to start when the broker of one of its delegates is missing
> -------------------------------------------------------------------------
>
>                 Key: UIMA-1702
>                 URL: https://issues.apache.org/jira/browse/UIMA-1702
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>             Fix For: 2.3AS
>
>
> Repeated logs on the console and in 5 activemq.log files:
> INFO  efaultMessageListenerContainer - Could not refresh JMS Connection - retrying in 5 ms
> javax.jms.JMSException: Could not connect to broker URL: tcp://gale-iod.basistech.com:8002. Reason: java.net.ConnectException: Connection refused: connect
> The error handling of <getMetadataErrors maxRetries="0" timeout="60000" errorAction="disable"/>
> is not applied ... aggregate service never initializes.  Deployed via -d option of runRemoteAsyncAE

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.