activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk de Kok (JIRA)" <>
Subject [jira] Commented: (AMQ-2453) start/control-script is not suitable for professional environments
Date Fri, 15 Jan 2010 16:18:48 GMT


Dirk de Kok commented on AMQ-2453:

hi there,

I had a short look a the script here and the activemq site (
For me as a software engineer and not system engineer it is a bit difficult to say what the
best way is, but this is my input:

- process should run like a daemon in the background
- process should do proper logging
- process should be available for status checks (e.g. via jmx)
- process should run like a specified user (e.g. activemq) and not root
- should use PID file 
- should be possible to configure for automatic startup and shutdown

What I miss right now (but might have overlooked):

- example directory layout (where binaries, config files, startup script)
- clear definition of responsibilities of files (controlling process, configuration, etc).
Right now too much is in some files
- how to install for automatic startup/shutdown with the system (on linux for me in particular:))

just my 2 cents :)


> start/control-script is not suitable for professional environments
> ------------------------------------------------------------------
>                 Key: AMQ-2453
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>            Reporter: Marc Schöchlin
>            Assignee: Rob Davies
>             Fix For: 5.4.0
>         Attachments: activemq, usage-example.txt
> The start-scripts "activemq" and "activemq-admin" do not seem to be ready for production
> 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.
You can reply to this email to add a comment to the issue online.

View raw message