[
https://issues.apache.org/jira/browse/QPID-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marnie McCormack resolved QPID-352.
-----------------------------------
Resolution: Fixed
Fix Version/s: M2
Amended qpid-server and qpid-run to move variables from conf file into
qpid-server and check for env overriding in qpid-run for QPID_JAVA_MEM to allow
config in prod envs. Left original qpid-server.conf as think other packaging
methods may still use.
> Remove *.conf configuration file from Java broker config model
> --------------------------------------------------------------
>
> Key: QPID-352
> URL: https://issues.apache.org/jira/browse/QPID-352
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: M1
> Reporter: Marnie McCormack
> Assigned To: Marnie McCormack
> Fix For: M2
>
>
> At present, when users execute the qpid-server.sh script, qpid-run uses the
> corresponding qpid-server.conf file to set the following:
> QPID_LIBS=$QPID_HOME/lib/qpid-incubating.jar:$QPID_HOME/lib/bdbstore-launch.jar
> export JAVA=java \
> JAVA_VM=-server \
> JAVA_MEM=-Xmx1024m \
> CLASSPATH=$QPID_LIBS
> Propose moving this config into qpid-server.sh itself, and amend to allow
> environment variables to be read first - and only set to defaults if not. For
> production packaging, having a scriptname.conf file is actually overhead
> which is not helpful.
> Also, since so much defaulting/checking already done in qpid-run this stuff
> is really not significant enough to have it's own conf file imho !
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
