[
https://issues.apache.org/jira/browse/UIMA-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006490#comment-14006490
]
Burn Lewis commented on UIMA-3827:
----------------------------------
So it's by-design that UIMA-AS doesn't fail if the broker is missing since it
may be about to come online. I found the warning message in a different log
file.
But I've reproduced the http case where the broker is up but missing activemq
jars cause the service connection to fail. I now see the following message
04:36:35.635 - 227:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure:
WARNING: Uima AS Service:IndriSupportingPassageRetrieval Listener Unable To
Connect To Broker: http://bluej544:8081 Retrying ...
The logs are in ~burn/logs/S-1419/13004/
I see that Spring does pass in a throwable to handleListenerSetupFailure so
maybe that would help ... or maybe its a silent failure!
> Missing activemq jars cause a http service to falsely claim to be up
> --------------------------------------------------------------------
>
> Key: UIMA-3827
> URL: https://issues.apache.org/jira/browse/UIMA-3827
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.4.2AS
> Reporter: Burn Lewis
> Assignee: Jerry Cwiklik
> Priority: Minor
> Fix For: 2.6.0AS
>
>
> If the apache-activemq/lib/optional jars are missing an http service fails to
> connect to its broker but reports successful initialization. Since the
> pinger cannot reach the service any dependent jobs are stuck forever
> WaitingForServices.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
