GigaSpaces JMS Limitations

Added by Gilad David Maayan, last edited by Aleia Hutcherson on May 26, 2008  (view change)
  GigaSpaces 5.X

Documentation Home
Quick Start Guide
Release Notes

Previous release
  Search Here
Searching GigaSpaces Platform 5.X Documentation

                                               
Summary: Known limitations of the GigaSpaces virtual JMS implementation.

Overview

  • Unification of messaging domains as part of the JMS 1.1 specification is not supported.
  • GSJMSAdmin is used as the admin tool to find destinations and connection factories. Lookup using InitialContext directly is not supported.
  • Session.recover() and JMSRedelivered message header flag is not supported
  • JMS message priority is not supported.
  • Spec expects an immediate null return message value from a stopped/closed session/connection using sync consumer.receive(). We do not support this behavior – client is blocked till operation is completed.
  • JMS Selectors support limitations:
    • Support for Selectors using JMS Message headers or JMS Provider Properties. No selectors support for the user defined custom JMS message properties.
    • Adding/modified/removing properties on the fly is not supported.
    • TimeOut parameter is not supported.
    • JMS Selectors Query options we are limited to GigaSpaces JDBC API capabilities.
  • MDB support for WebLogic, JBoss and Webshpere.
  • JMS using JMX libraries which might cause clashes with Application Server JMX implementation.

Wiki Content Tree

Your Feedback Needed!

We need your help to improve this wiki site. If you have any suggestions or corrections, write to us at techw@gigaspaces.com. Please provide a link to the wiki page you are referring to.

Labels

 
(None)