[
https://issues.apache.org/jira/browse/UIMA-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1137.
-------------------------------
Resolution: Fixed
The service reports the fact that the broker is not available and will wait
until the broker starts. Once the broker becomes available the service
initializes and is ready for processing.
> Service hangs if deployed before broker is ready
> ------------------------------------------------
>
> Key: UIMA-1137
> URL: https://issues.apache.org/jira/browse/UIMA-1137
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2
> Reporter: Burn Lewis
> Priority: Minor
>
> When both a service and its broker are restarted together (e.g. after a
> reboot) the service will fail to initialize if the broker is not ready. The
> service claims it is shutting down, e.g. with 3 lines such as:
> >>>> Terminating Controller:StoryBoundary Unable To Initialize Listener Due
> >>>> to Invalid Broker URL:tcp://telly.watson.ibm.com:61616
> but it then hangs.
> The service should wait for the broker, and log to the console when it has
> successfully connected. Could also log a "still trying" indication every
> minute or so. Would be nice to suppress these spring error msgs:
> org.springframework.jms.listener.AbstractJmsListeningContainer$SharedConnectionNotInitializedException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
