[
https://issues.apache.org/jira/browse/AMQ-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-2453.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 5.4.2)
(was: 5.4.0)
5.7.0
Assignee: Timothy Bish (was: Dejan Bosanac)
Added LSB compliant header to the scripts for systems that use it.
> 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: Timothy Bish
> Fix For: 5.7.0
>
> 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
