[
https://issues.apache.org/jira/browse/UIMA-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-3842.
-------------------------------
Resolution: Fixed
Modified to avoid closing shared connection in the listener destroy()
method.Instead calls listener shutdown method which handles connection cleanup.
> UIMA-AS listeners not shutting down cleanly
> -------------------------------------------
>
> Key: UIMA-3842
> URL: https://issues.apache.org/jira/browse/UIMA-3842
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.4.2AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.6.0AS
>
>
> While running extended tests I've noticed there were quite a few Exceptions
> coming from AMQ while uima-as service was shutting down. Traced this to code
> in UimaDefaultMessageListenerContainer.java that was doing this:
> __listenerRef.getSharedConnection().close();
> Since there are multiple instances of listeners, the connection was being
> closed while other listeners were still running causing the underlying AMQ
> code to complain as the connection was being yanked while in running state.
> Modified code to stop calling close on shared connection and instead call
> listener shutdown code that eventually closes the connection after the last
> listener stops.
--
This message was sent by Atlassian JIRA
(v6.2#6252)