activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <>
Subject [jira] Commented: (AMQ-2453) start/control-script is not suitable for professional environments
Date Fri, 18 Jun 2010 14:10:55 GMT


Dejan Bosanac commented on AMQ-2453:

A modified script has been committed with svn revision 956005

I made a few changes:

- copied the part from the old script that sets ACTIVEMQ_HOME to the current dir if it isn't
already set and /opt/activemq does not exists
- refactored around seq as it does not exists on OS X
- added logic to create data folder if it doesn't exist (maybe this can be made even more
- used bash as echo -n is bash specific
- fixed some typos

This is only the starting point, so we should test this thoroughly in various environments
and make it rock solid for the next release (I tested it so far on OS X)

The one thing I observed is that we need to improve the stop logic as "regular stop method"
isn't called asynchronously, so the waiting loop doesn't do much.

Thanks for the contribution Marc.

> 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: Dejan Bosanac
>             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