You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/12/11 07:37:08 UTC

[jira] Updated: (GERONIMO-1058) Client container outputs misleading shutdown messages even if threads still running

     [ http://issues.apache.org/jira/browse/GERONIMO-1058?page=all ]

Aaron Mulder updated GERONIMO-1058:
-----------------------------------

    Fix Version: 1.1

> Client container outputs misleading shutdown messages even if threads still running
> -----------------------------------------------------------------------------------
>
>          Key: GERONIMO-1058
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1058
>      Project: Geronimo
>         Type: Bug
>   Components: application client
>     Versions: 1.0-M5
>     Reporter: Nell Gawor
>     Priority: Minor
>      Fix For: 1.1

>
> If a client application has a main method that starts additional threads and then returns, the client container outputs and logs messages that it is shutting down:
>  > 12:03:20,584 INFO  [CommandLine] Server shutdown begun
>  > 12:03:20,584 DEBUG [GBeanInstanceState] GBeanInstanceState for:
>  > geronimo.config:name="org/apache/geronimo/ClientSystem" State changed
>  > from running to stopping
> while in fact the client application threads are still running.  If possible, the client container should not output these messages until all the threads have exited.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira