When you say two separate MQ , are you referring to 2 separate brokers instances of open mq (that is present in glassfish) ? please let me know if understood this correctly
You can start standalone (open mq) broker instances using GFHOME/imq/bin/imqbrokerd command, this will start a standalone MQ broker instance, of course the lifecycle of this will not be controlled by glassfish and you need to manage this, an instance of glassfish is capable of controlling the lifecycle of only one broker, the one that is configured as default_JMS_host in the JMS service configuration.
However, applications deployed in glassfish can connect to this standalone broker, if you configure your connection factories used by the application (asadmin create-jms-resource) with the addreslist (and other properties) of this broker instance.
An Open MQ jms instance can be integrated with glassfish using one of the following integration modes,
EMBEDDED : This means that the lifecycle (start and stop) of the broker instance (default_jms_host) is controlled by glassfish and the broker is started in the same process as that of the application server.
LOCAL: This means that the lifecycle of the broker instance (default_jms_host) is controlled by glassfish and the broker is started in a separate process.
REMOTE : The broker is started and managed externally and glassfish will only try and connect to it (does not control the start/stop) during glassfish startup.
if you have any specific queries please post them.
[Message sent by forum member 'rampsarathy' (rampsarathy)]
http://forums.java.net/jive/thread.jspa?messageID=213338