[
https://issues.apache.org/jira/browse/UIMA-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-2776.
-------------------------------
Resolution: Fixed
Added a timer thread to periodically check state of each jms session and close
inactive ones. This deals with a bug in AMQ which causes broker OOM. The broker
holds on to messages even though a destination no longer exists as long as
there are producer sessions open. The fix is to close the sessions after some
(configurable) amount of inactivity.
> UIMA-AS not managing broker sessions
> -------------------------------------
>
> Key: UIMA-2776
> URL: https://issues.apache.org/jira/browse/UIMA-2776
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.4.0AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.4.1AS
>
>
> UIMA-AS service doesn't manage broker sessions which leads to broker OOM in
> some use cases. Current code keeps sessions open even if clients terminate.
> If a client terminates before the broker delivers outstanding messages to it,
> such messages are never purged from brokers memory. This is because the
> service has a jms session open. Broker only cleans such messages if either a
> session is closed or a connection is closed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
