Restrictions in this version of MQe

This version of MQe JMS implements the Point-to-Point subset of JMS with a few restrictions. It does not implement any of the optional classes:
  • The application server classes ConnectionConsumer, ServerSession, and ServerSessionPool
  • The XA classes:
    • XAConnection
    • XAConnectionFactory
    • XAQueueConnection
    • XAQueueConnectionFactory
    • XAQueueSession
    • XASession
    • XATopicConnection
    • XATopicConnectionFactory
    • XATopicSession
It does not implement the TemporaryQueue class, which means that the QueueRequestor class will not work or the MapMessage and StreamMessage classes.

In the QueueConnectionFactory, the createQueueConnection() method that takes a username and password as parameters is not implemented, MQe does not have the concept of a user. The method with no parameters is implemented.

When a message is read from a queue but not acknowledged, the message is returned to the queue for redelivery. In this case the JMSRedelivered header field should be set in the message. MQe JMS does not set this header field.

MQe JMS can put messages to a local queue or an asynchronous remote queue and it can receive messages from a local queue. It cannot put to or receive messages from a synchronous remote queue.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.