[
https://issues.apache.org/jira/browse/UIMA-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-2038:
--------------------------------
Description: UIMA AS two stop options dont seem to work reliably. Neither
's' nor 'q' on the command line force a clean shutdown of the process.
Actually, there is also a related problem. Namely, when the shutdown succeeds
it appears that the Shared Connection that all Spring listeners use is not
closed which leads to an ugly exception on the broker console. This happens
every time the service is terminated. Review listeners shutdown code and make
sure that when the last listener terminates the connection is stopped before
the process exits. Also, make sure that uima threads from custom pools are
daemon threads to allow the jvm to collect them on shutdown. NOTE: AMQ version
4.x internal threads are not daemon threads and there is special code in the
listener to wait for them to stop before exiting. Newer AMQ version use daemon
threads so shutting down AMQ is much more reliable. (was: UIMA AS two stop
options dont seem to work reliably. Neither 's' and 'q' on the command line
force a clean shutdown of the process. Actually, there is also a related
problem. Namely, when the shutdown succeeds it appears that the Shared
Connection that all Spring listeners use is not closed which leads to an ugly
exception on the broker console. This happens every time the service is
terminated. Review listeners shutdown code and make sure that when the last
listener terminates the connection is stopped before the process exits. Also,
make sure that uima threads from custom pools are daemon threads to allow the
jvm to collect them on shutdown. NOTE: AMQ version 4.x internal threads are not
daemon threads and there is special code in the listener to wait for them to
stop before exiting. Newer AMQ version use daemon threads so shutting down AMQ
is much more reliable. )
Minor update to the description
> UIMA AS process does not terminate reliably
> -------------------------------------------
>
> Key: UIMA-2038
> URL: https://issues.apache.org/jira/browse/UIMA-2038
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.3.1AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> UIMA AS two stop options dont seem to work reliably. Neither 's' nor 'q' on
> the command line force a clean shutdown of the process. Actually, there is
> also a related problem. Namely, when the shutdown succeeds it appears that
> the Shared Connection that all Spring listeners use is not closed which leads
> to an ugly exception on the broker console. This happens every time the
> service is terminated. Review listeners shutdown code and make sure that when
> the last listener terminates the connection is stopped before the process
> exits. Also, make sure that uima threads from custom pools are daemon threads
> to allow the jvm to collect them on shutdown. NOTE: AMQ version 4.x internal
> threads are not daemon threads and there is special code in the listener to
> wait for them to stop before exiting. Newer AMQ version use daemon threads so
> shutting down AMQ is much more reliable.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
