GlassFish Wiki : AppserverMqIntegrationOptions

AS/MQ integration possibilities

The matrices below attempt to list all possible integrations between appserver (AS) and Sun Java System Message Queue(MQ). Please add your inputs as comments.

Non-HA single-instance AS/MQ broker integration (PE)

AS_MQ integration mode	Advantages	Disadvantages
DIRECT	AS controls broker lifecycle, AS/broker located in the same VM, network stack bypassed, no administrator intervention required	Less stable as MQ's Flow control interfered by AS' use of the VM. In clustered mode, failure of a clustered instance, would mean message inavailability (ie messages published to the broker associated with that instance) until that instance comes up.
EMBEDDED	AS controls broker lifecycle, AS/broker located in the same VM, no administrator intervention required	Less stable as MQ's Flow control interfered by AS' use of the VM, network overhead. In clustered mode, failure of a clustered instance, would mean message inavailability (ie messages published to the broker associated with that instance) until that instance comes up.
LOCAL	AS controls broker lifecyle, broker started out-of-process, no administrator intervention required	one additional broker process. lifecycles of AS/MQ not in sync. In clustered mode, failure of a clustered instance's broker, would mean message inavailability (ie messages published to the broker associated with that instance) until that broker is started.
REMOTE	administrator manually starts broker using mq admin tools. Allows sharing of MQ broker across multiple AS instances. AS instance is 'lighter' as it doesn't manage a MQ process	AS does not manage lifecycle startup, administrator intervention required

. Non-HA clustered AS/MQ broker integrations (EE clusters - out-of-the-box AS/MQ cluster setup for EE clusters)
.. all the advantages/disadvantages listed above in PE are valid in non-HA AS/MQ clusters as well.. Uses the traditional non-HA MQ cluster mode

AS_MQ integration mode	Advantages	Disadvantages
DIRECT/EMBEDDED		In clustered mode, failure of a clustered instance, would mean message inavailability (ie messages published to the broker associated with that instance) until that instance comes up.
LOCAL		In clustered mode, failure of a clustered instance's broker, would mean message inavailability (ie messages published to the broker associated with that instance) until that broker is started. The MQ cluster's lifecycle is tied to an AS cluster.

Jspwiki style: h2

. HA clustered AS/MQ broker integrations
.. all the advantages/disadvantages listed above for PE are valid in HA AS/MQ clusters as well.. Uses the new "HA-cluster" in MQ 4.1

AS_MQ integration mode	Advantages	Disadvantages
DIRECT/EMBEDDED	Lightweight AS instance as AS and MQ are in the same process. Interesting optimizations are possible since sticky loadbalancing would ensure that production and consumption could happen in the same VM.	EMBEDDED mode is apparently less stable as mentioned above.
LOCAL	AS/MQ could share same HADB connection pool configuration or AS could be directed to let MQ use a separate HADB conn pool. AS drives MQ's HADB usage. Ease of administration as administrator uses asadmin GUI.	The MQ cluster's lifecycle is tied to an AS cluster
REMOTE	Potential to fine-tune HADB conn.pools based on MQ cluster-usage	Extra HADB configuration required by an administrator

Jspwiki style: h2

%%
traditional non-HA MQ cluster mode