You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/07/19 23:20:57 UTC

[jira] [Closed] (AMQ-2931) ActiveMQ warning - needing Java shutdown hook.

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

Timothy Bish closed AMQ-2931.
-----------------------------

    Resolution: Not A Problem

ActiveMQ does use a shutdown hook. The warning is generated from a method that is deprecated but left in for legacy support.

> ActiveMQ warning - needing Java shutdown hook.
> ----------------------------------------------
>
>                 Key: AMQ-2931
>                 URL: https://issues.apache.org/jira/browse/AMQ-2931
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.0
>            Reporter: Robert Liguori
>            Priority: Minor
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Starting Apache ActiveMQ 5.4.0 shows the following warning:
>  WARN | destroyApplicationContextOnStop parameter is deprecated, please use shutdown hooks instead
> ---------------------------------------------------------------------------------------
> Case Study: Apache  Servicemix applies the appropriate fix:
> From: http://servicemix.apache.org/getting-started.html
> Stopping ServiceMix
> For both Windows and Unix installations, terminate ServiceMix by typing "CTRL-C" on the command line where ServiceMix is running. ServiceMix uses the Java shutdown hook to cleanly shut down the container. 
> Java Shutdown Hook: http://download.oracle.com/javase/1.4.2/docs/guide/lang/hook-design.html
> ---------------------------------------------------------------------------------------
> The issue is for the Apache ActiveMQ to use teh the shutdown hook as is done with Servicemix, therefore correcting the problem and removing the warning.
> Thanks.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira