|
Problem(Abstract) |
In WebSphere Application Server V5.0 releases, when using
embedded messaging, the following exception might be created when a
message-driven bean (MDB) module starts:
WMSG0019E: Unable to start MDB Listener CacheMDB, JMSDestination
DCacheClusterTopic : javax.jms.JMSException: MQJMS1010: not implemented
at
com.ibm.mq.jms.TopicConnectionImpl.createConnectionConsumer(TopicConnectionImpl.java:182)
at
com.ibm.ejs.jms.JMSTopicConnectionHandle.createConnectionConsumer(JMSTopicConnectionHandle.java:118)
at
com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:392) |
|
|
|
Cause |
This problem results from the way the topic connection
factory that is associated with the MDB listener port is configured. If
the topic connection factory is XA-enabled, the use of the DIRECT setting
for the Port property on the topic connection factory is not supported.
Using the DIRECT setting causes the MQJMS1010 exception. |
|
|
Resolving the
problem |
Follow these steps to resolve the problem:
- Reconfigure the topic connection factory, and change the value of the
Port property from DIRECT to QUEUED.
- Save the changes.
- Restart the application server.
The following information is provided in the WebSphere Application Server
administrative console:
Port
Identifies which of the two ports that connections use to connect to the
Java Message Server (JMS). The QUEUED port is for full-function JMS
publish/subscribe support. The DIRECT port is for nonpersistent,
non-transactional, nondurable subscriptions only.
Message-driven beans cannot use the direct listener port for
publish/subscribe support. Therefore, any topic connection factory that is
configured with the Port value set to Direct cannot be used with
message-driven beans. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|