users@glassfish.java.net

Re: IMQ cluster issue

From: <glassfish_at_javadesktop.org>
Date: Wed, 16 Sep 2009 14:15:47 PDT

OK, so I've added the following line to the "/opt/glassfish/nodeagents/app-a/idms-prod-a/imq/instances/idmsprodidmsproda/props/config.properties" file:

[b]imq.cluster.url=file\://opt/glassfish/config/cluster.config[/b]

and created the "/opt/glassfish/config/cluster.config" file with the following line in it:

[b]imq.cluster.masterbroker=mq://app-a:37676[/b]

Upon restarting the instance, the MQ instance still restarts with the following:

[b][16/Sep/2009:15:54:47 CDT] Arguments: -javahome /usr/jdk/instances/jdk1.5.0/jre/.. -Dimq.cluster.masterbroker=mq://app-c:37676/ -Dimq.cluster.brokerlist=mq://app-a:37676/,mq://app-d:37676/,mq://app-b:37676/,mq://app-c:37676/ -Dimq.cluster.nowaitForMasterBroker=true -varhome /opt/glassfish/nodeagents/app-a/idms-prod-a/imq -startRmiRegistry -rmi
RegistryPort 37776 -Dimq.imqcmd.user=admin -passfile /var/tmp/asmq6727135897778847642.tmp -save -name idmsprodidmsproda -port 37676 -bgnd -silent[/b]


It doesn't appear that the MQ service even reads the config.properties file, instead Glassfish starts the message queue with specific options. The question is, how can I get GF to use the same masterbroker option across all of the instances?
[Message sent by forum member 'mcking' (mark_at_mccoyfam.net)]

http://forums.java.net/jive/thread.jspa?messageID=364294