Himanshu Mishra created AMQ-7367:
------------------------------------
Summary: wrapper.java.maxmemory not dynamically modifiable
Key: AMQ-7367
URL: https://issues.apache.org/jira/browse/AMQ-7367
Project: ActiveMQ
Issue Type: Wish
Components: AMQP
Reporter: Himanshu Mishra
Hi,
I was exploring activemq for my java project, where I was willing to start it
as a service with given java memory arguments. Activemq utilizes java wrapper
service for starting itself as a service. Java wrapper service has a
configuration wrapper.java.maxmemory for specifying -Xmx value.
For an user it may not be possible to go and change wrapper.conf file
everytime; so I was building an user interface for supplying this value at the
time of starting activemq. Application too may not have write access to the
file. The only thing we could do is to supply wrapper.java.maxmemory through
command line to wrapper service. Shell script
<activemq>\linux\bin\linux-x86-32\activemq does not allow us to do that. I have
added one parameter *$ADDITIONAL_CONF* to this script
COMMAND_LINE="$CMDNICE $WRAPPER_CMD $WRAPPER_CONF
wrapper.syslog.ident=$APP_NAME wrapper.pidfile=$PIDFILE wrapper.daemonize=TRUE
$ANCHORPROP $IGNOREPROP $LOCKPROP *$ADDITIONAL_CONF*" to this shell script.
Is it a good option to add? The reason I am asking this is, one of the feature
of wrapper service is getting blocked.
Thanks in advance for valuable inputs!!!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
