You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Marc Schöchlin (JIRA)" <ji...@apache.org> on 2010/10/06 15:36:44 UTC
[jira] Reopened: (AMQ-2453) start/control-script is not suitable
for professional environments
[ https://issues.apache.org/activemq/browse/AMQ-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marc Schöchlin reopened AMQ-2453:
---------------------------------
With activemq 5.4.1 the new initscript is part of the activemq distribution.
There are still parts of the old start/control-script infrastructure for unix/linuxmacos systems
included in the activemq delivery.
This should be removed, because this confuses activemq-users.
Distribution should not contain the follwing folders/files:
apache-activemq-5.4.1/bin/activemq-admin : All functionality of bin/activemq-admin is implemented in bin/activemq
apache-activemq-5.4.1/bin/linux-x86-32 : This is only needed for jsw
apache-activemq-5.4.1/bin/linux-x86-64 : This is only needed for jsw
apache-activemq-5.4.1/bin/macosx : This is only needed for jsw
apache-activemq-5.4.1/bin/wrapper.jar : This is only needed for jsw
In my current work-environment admins and developers were confused of having two different start environments - i think
it´s a good idea to cleanup the distribution.
Regards
Marc
> start/control-script is not suitable for professional environments
> ------------------------------------------------------------------
>
> Key: AMQ-2453
> URL: https://issues.apache.org/activemq/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
>
> 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.
-
You can reply to this email to add a comment to the issue online.