You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mladen Turk (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/07 16:26:51 UTC
[jira] [Resolved] (DAEMON-136) Jsvc does not exit when all
non-daemon threads are died
[ https://issues.apache.org/jira/browse/DAEMON-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mladen Turk resolved DAEMON-136.
--------------------------------
Resolution: Incomplete
Please provide a test case so we can verify your claims.
I'm closing this issue, but you are free to reopen it
wit something we can use for testing
> Jsvc does not exit when all non-daemon threads are died
> -------------------------------------------------------
>
> Key: DAEMON-136
> URL: https://issues.apache.org/jira/browse/DAEMON-136
> Project: Commons Daemon
> Issue Type: Bug
> Components: Jsvc
> Affects Versions: 1.0.2
> Environment: Ubuntu 9.10, Sun Java 1.6.0_16
> Reporter: Hontvari Jozsef
> Priority: Minor
> Attachments: stack, stack-long, stack-mixed-long
>
>
> A jsvc dameon keeps running even if all non-dameon Java threads are exited. It can be reproduced by creating a start class with the usual four, but empty functions. The symtom does not change if init() takes a few seconds of time. I have attached three stack traces, using different jstack options, I don't see anything special, however.
> The workaround is to explicitly call System.exit() at places where the system can finish its work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira