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/05/16 18:49:11 UTC

[jira] Commented: (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:comment-tabpanel&focusedCommentId=59374#action_59374 ] 

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

We should remove jsw wrapper scripts  - this is a ugly solution from a linux/unix  sysadmin's view....popular projects like tomcat and jboss
also do not need hacks like this....

See also:   https://issues.apache.org/activemq/browse/AMQ-2105?focusedCommentId=59373&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_59373

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