User Experience: MQ Attendees: Siva, Ramesh, Sudeer, Anissa, Jagadesh, Siraj, Meena, Nazrul Summary:
- GlassFish v2 has nice set of features planned.
- Inprocess MQ
- Performance improvement by short-circuiting network operations
- Sticky connection balancing
- Address list is modified for each server instance to point to co-located LOCAL broker
- "auto-clustering" for non-HA mode
- First AS broker instance becomes the master broker. In the event the first instance is removed, a cluster re-start is needed. Second instance from the list will be selected as the master broker.
- High availability cluster
- This feature requires HADB. Will only work in Sun Java System Application Server 9.1 EE. MQ team will consider in-memory in future release.
- configure-ha-cluster will make MQ highly available also.
- For REMOTE type configuration, user may use mqadmin and hadbadmin.
- MQ uses unicast based peer to peer heartbeat to determince failures.
Open Issues:
- Need sizing guide for HADB usage with MQ - Siva to follow-up with MQ team
- Blog about v2 features - Siva
- We should make sure people can copy hadb bits in the lib directory and use MQ in HA mode. - Siva
- MQ HA UIs in Admin GUI needs to be updated for GlassFish since it will not have HADB. - Anissa, Siva
- Should we allow user to select and change master broker? - Siva
|