GlassFish Server Open Source Edition 3.1 - JMS and Message Queue enhancements

Scope of the Project

(Note: Broker Embedded = MQ configured to run in same VM as GlassFish, Remote = MQ running on same machine, w/Lifecycle controls, Remote = MQ unmanaged, in remote VM See also GlassFish Embedded Sub-project page; See also EJB-5 from the EJB 3.1 Sub-project page.)

Feature Overview

JMS support for embedded Glassfish instances

• Description

This task involves providing complete JMS support to Glassfish when it is running in an embedded mode. All three modes of MQ integration- embedded/local and remote will be supported. However, MQ clusters will not be supported since cluster service requires some minimum broker properties or commandline parameters and requires portmapper service running.

• Sub-tasks

GlassFish Meessage Queue 4.5 will be integrated into GlassFish Server, Open Source Edition 3.1. Please also see the GlassFish MQ project for more information.

Support for different modes of MQ integration within embedded GF:
The following subtasks are the first level of support for integrating JMS capabilities with embedded GF.
JMS-1: Support for running a stand-alone embedded MQ broker within embedded GlassFish
JMS-2: Support for running a stand-alone Local MQ broker within embedded GlassFish
JMS-3: Support for running a stand-alone Remote MQ broker within embedded GlassFish

Starting MQ with no/minimum ports:
MQ currently requires a minimum of four ports to be started- Port mapper, JMS service, Cluster Service and JMS admin. The following two requirements are advanced enhancements to the JMS-1 requirement:

JMS-4: Running embedded MQ broker without starting any ports: In cases where the only JMS communication required is within the same JVM, no ports need to be started unnecessarily. Applications would communicate with MQ using the new APIDirect mode.

JMS-5: Running embedded MQ broker with minimum number of ports: This would translate into MQ starting only the JMS service and port mapper ports.

• Owners

Satish, Nigel/Amy

• Estimate

TBD

JMS clustering and HA support

• Description:

This task involves enhancements to GlassFish 3.1 to support MQ's clustering capabilities. MQ currently supports two modes of clustering – conventional clustering (service HA) and enhanced clustering (includes data HA, which relies on a HA database).

• Subtasks:

JMS-6: Support for conventional clustering of MQ brokers in Local mode.
JMS-7: Support for enhanced clustering of MQ brokers in Local mode
JMS-8: Support for conventional clustering of MQ brokers in Remote mode
JMS-9: Support for enhanced clustering of MQ brokers in Remote mode

This is the level of support that has been available in earlier releases of GlassFish.

• Related features:

Clustering of MQ brokers in embedded mode:
This has not been supported in earlier releases of GlassFish. To support enhanced cluster in embeded mode, there is an issue with having to restart the MQ broker in the event of a potential split-brain (e.g. under network partition if a broker unable to update its heartbeat within the configured monitor interval). When a potential split-brain is detected, it is very important to terminate any in-flight data access right away hence the broker JVM will need to be halted and restarted. Restarting an embedded broker without exiting the JVM would increase seriously the risk to data integrity. The following two requirements are an extension of this feature:
JMS-10: Support for conventional clustering of MQ brokers in Embedded mode
JMS-11: Support for enhanced clustering of MQ brokers in Embedded mode

JMS-12 Improvements to MQ's conventional clustering (master broker):
MQ conventional clustering architecture requires a master broker on creation/update/deletion of durable subscription and physical destination and sync-up with master broker on a broker startup. This imposes the requirement for the master broker to be started before the remaining broker instances can start and function correctly. They have been several complaints from users running into "master broker not started" errors if there are delays in the start-up of the master broker.

• Owners:

Satish, Nigel and Amy Kang

• Schedule:

TBD

Support for Resource Adapters

• Description:

GlassFish currently ships with JMSRA as the default resource adapter. JMSRA is a system RA hence in is available out-of-the-box. Currently, JMSRA also manages the broker life-cycle (starting and stopping the broker) in embedded and local modes.

• Subtasks:

JMS-13: Integration with IBM Websphere MQ through GenericJMSRA:
GlassFish also ships GenericJMSRA for integration with other JMS provides. We currently support integration with IBM Websphere MQ.

• Related tasks:

JMS-14: Direct mode support for RAs:
This will allow other RA's to use the 'Direct mode' rather than TCP to connect to an in-process MQ broker. Currently, this feature is only available to JMSRA. Performance test suggests this can approximately double messaging performance compared with TCP mode.

JMS-15: Separation of Life-cycle management components from JMSRA:
At present, JMSRA functions as both a MQ broker lifecycle management component and as a JCA based resource adapter. This means that even if JMSRA is not required as a RA, it must nevertheless be started in order to perform broker lifecycle management. This work would involve spliting JMSRA into separate RA and lifecycle management components. Post this change, there would not be a need to start JMSRA unless it was actually needed.

• Owners:

Nigel, Satish

• Schedule:

TBD

Enhancements to JMS related Admin commands for cluster support

• Description:

JMS-16: Enhance the existing JMS related admin commands (such as - create-jms-host, delete-jms-host, list-jms-hosts, create-jms-resource, delete-jms-resource, list-jms-resources, create-jmsdest, delete-jmsdest, list-jmsdest, flush-jmsdest, jms-ping, etc.) for cluster support.

• Subtasks:

None

• Owners:

Satish

• Schedule:

TBD

Integration of MQ's monitoring capabilities with the GlassFish 3 monitoring framework

• Description:

The task involves leveraging and enhancing MQ's monitoring capabilities so that they can be accessible using the new Glassfish 3 monitoring framework.

• Subtasks:

JMS-17: Integrating of existing JMX based MQ broker metrics with GF monitoring framework: There are currently exposed through JMX
JMS-18: Integrating of existing command-line based MQ metrics with GF 3: Currently these can only be accessed through the MQ command line
JMS-19: Adding MQ client-side metrics: There are currently no metics available on the MQ client-side.

• Owners:

Satish, Nigel

• Schedule:

TBD

WebLogic DD support

• Description:

JMS-20: Support for weblogic-jms.xml in GlassFish. A detailed feasability study is available here

• Subtasks:

None

• Owners:

TBD

• Schedule:

TBD

Coherence support

• Description:

JMS-21: Enhancement to MQ to use Coherence for high availability in lieu of MySQL.

• Subtasks:

None

• Owners:

TBD

• Schedule:

TBD

VisualVM Plugin Enhancements

• Description:

MQ 4.4U1 currently offers a plugin to VisualVM to allow the state of a running MQ broker to be easily viewed. Description here. Quick start guide here.
It is proposed to enhance this to support broker clusters, allow charting of runtime data and provide various other improvements. Proposals here.

• Tasks:

JMS-22: VisualVM Plugin Enhancements

Other enhancements

• Tasks:

JMS-23: Glassfish RFE 6893609 (Glassfish MQ LOCAL startup options should be configurable)

JMS-24: Glassfish issue 11721 (GF does not allow all required passwords to be passed to managed MQ broker))

One-pager / Functional Specification

• These will be linked from the table above

Milestone Schedule

Dependencies on other Glassfish components:

JMS-06, JMS-07, JMS-08, JMS-09, JMS-16, JMS-10 and parts of JMS12a, JMS12b are all dependent on cluster support being added to Glassfish. In particular:

• config-api to access cluster related information
• Listener interfaces for dynamic addition/deletion of instances from a cluster.

Task List

Here's the same information in a different form, showing the internal dependency between tasks carried out by the MQ team (left column) and by the GF JMS team (right column):

Dev Tests

• Todo

Quality

• Link to Test Plans

Documentation

• Link to Documentation

References / Links

• WebLogic DD support

Email Alias

• Please contact us at dev@glassfish.java.net