activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Schöchlin (JIRA) <j...@apache.org>
Subject [jira] [Commented] (AMQ-2453) start/control-script is not suitable for professional environments
Date Tue, 10 Jul 2012 13:41:36 GMT

    [ https://issues.apache.org/jira/browse/AMQ-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410336#comment-13410336
] 

Marc Schöchlin commented on AMQ-2453:
-------------------------------------

Please remove the no longer needed files apache-activemq-5.x.x/bin/{activemq-admin,linux-x86-32,linux-x86-64,macosx,wrapper.jar}

Please add the script header to the script apache-activemq-5.x.x/bin/activemq to prevent SLES
systems to complain about
broken lsb-headers

{code}
insserv: missing `Required-Stop:'  entry: please add even if empty.
insserv: warning: script 'activemq' missing LSB tags and overrides
insserv: warning: script 'activemq' missing LSB tags and overrides
insserv: Default-Start undefined, assuming default start runlevel(s) for script `activemq'
{code}

Script header:
{code}
#!/bin/sh

### BEGIN INIT INFO
# Provides:          activemq
# Required-Start:    $remote_fs $network $syslog
# Required-Stop:     $remote_fs $network $syslog
# Default-Start:     3 5
# Default-Stop:      0 1 6
# Short-Description: Starts ActiveMQ
# Description:       Starts ActiveMQ Message Broker Server
### END INIT INFO
{code}
                
> start/control-script is not suitable for professional environments
> ------------------------------------------------------------------
>
>                 Key: AMQ-2453
>                 URL: https://issues.apache.org/jira/browse/AMQ-2453
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>            Reporter: Marc Schöchlin
>            Assignee: Dejan Bosanac
>             Fix For: 5.4.0, 5.4.2
>
>         Attachments: activemq, usage-example.txt
>
>
> The start-scripts "activemq" and "activemq-admin" do not seem to be ready for production
use.
> Reasons:
> - Server does not run in background
>   => this can be done by redirecting output to a file and run in background
>   => in my opinion this should be implemented directly in java
>   => the console log should be written by log4j to <install-root>/data/console.log
> - The process should be started on a non-root user 
>   => use 'su -c "$COMMAND" - $RUN_AS_USER' 
>   => this should be defined in /etc/activemq.conf
> - The script should support a "reload" feature to reload the configurartion
>   (if activemq supports reloading)
> - The script should support a "status" option
>   => this should show a quick overview about the state of activemq
>   => this should return a value != 0 if the service is not working
>      (this is important for cluster integration)
> Does anybody already working on these items?
> Do you have suggestions for a implementation?

--
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

       

Mime
View raw message