commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hontvari Jozsef (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DAEMON-136) Jsvc does not exit when all non-daemon threads are died
Date Sun, 28 Feb 2010 15:49:05 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hontvari Jozsef updated DAEMON-136:
-----------------------------------

    Attachment: stack-mixed-long
                stack-long
                stack

Stack traces from a running jsvc process which have empty init(), start(), etc. methods.

> 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
>             Fix For: 1.0.1
>
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message