[prev in list] [next in list] [prev in thread] [next in thread]
List: activemq-dev
Subject: [jira] Issue Comment Edited: (AMQ-2453) start/control-script is not
From: Marc_Schöchlin_(JIRA) <jira () apache ! org>
Date: 2010-06-30 11:28:00
Message-ID: 23638570.28651277897280160.JavaMail.jira () thor
[Download RAW message or body]
[ https://issues.apache.org/activemq/browse/AMQ-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60361#action_60361 \
]
Marc Schöchlin edited comment on AMQ-2453 at 6/30/10 7:24 AM:
--------------------------------------------------------------
Thats right, "VirtualMachine.attach(PID)" also does not work with a IBM JVM (we are \
using activemq with a IBM JVM on a IBM Mainframe/System z Linux).
Maybe there is a jmx connector for a unix domain socket file available?
This might be very cool from a system administrator ´s view - because :
- you don ´t need to open and secure (ssl, accounts, passwords, ...) a tcp port
- it is possible to control permissions by simple file permissions
- simple configuration of the initscript
Best regards
Marc
was (Author: scoopex):
Thats right, "VirtualMachine.attach(PID)" also does not work with a IBM JVM (we \
are using activemq with a IBM JVM on a IBM Mainframe/System z Linux).
Maybe there is a jmx connector for a unix domain socket file available?
This might be very cool from a system administrator ´s view - because :
- you don ´t need to open and secure (ssl, accounts, passwords, ...) a tcp port
- it is possible to control permissions by simple file permissions
Best 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.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic