[
https://issues.apache.org/jira/browse/UIMA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-3950.
-------------------------------
Resolution: Fixed
Modified listener code to prevent thread from exiting on connection problems.
Fixes the cause of multiple calls on defineCasPool. The thread in question
remains viable while Spring tries to recover the connection
> UIMA-AS allows multiple calls on defineCasPool() which results in an exception
> ------------------------------------------------------------------------------
>
> Key: UIMA-3950
> URL: https://issues.apache.org/jira/browse/UIMA-3950
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.6.0AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.6.1AS
>
>
> The UIMA-AS uses a custom thread pool to enable pinning of threads to
> specific AE instances. This is needed to enforce a design where a thread used
> to initialize AE instance is also used for calling process() on that instance.
> The thread pool is plugged in to the jms listener (for the input queue). The
> pool is configured with a fixed number of threads (=scaleout factor).
> Due to a bug in the uima-as failover code, a thread (from the pool) was
> exiting (due to connectivity problem). The problem was replicated by using a
> bad broker URL on the top level service.Since the thread pool was told to
> maintain a fixed number of threads, the exit of a thread caused
> a new thread creation and subsequent attempt to initialize another AE
> instance which then led to a call to defineCasPool() again. The uima core
> doesnt allow multiple calls to define cas pool and throws an exception.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
