[
https://issues.apache.org/jira/browse/UIMA-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik reopened UIMA-5894:
---------------------------------
Reassign to 3.0.0-Ducc
> UIMA-DUCC: the WS broker health checker should create new connection
> --------------------------------------------------------------------
>
> Key: UIMA-5894
> URL: https://issues.apache.org/jira/browse/UIMA-5894
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Major
> Fix For: 2.3.0-DUCC
>
>
> Current broker health checker in the WS uses Camel's producer to send JMS
> pings to itself. This producer is optimized to use Connection factory and
> reuse existing connections. Although this is efficient, it does not test an
> important scenario where a broker keeps serving existing connections but
> refuses to accept new ones.
> So to test broker viability the health checker should create new broker
> connection for every ping. Spring's JmsTemplate provides such function.
> Modify Camel route in WebServerConfiguration code to not publish pings. This
> route should continue to run on the timer but the ping should be dispatched
> by new code in WebServerStateProcessor.process().
> This code will use JmsTemplate to publish WebServerStateDuccEvent to the WS
> topic
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
