When using JMS Adapter to IBM Webspehere MQ JMS you get the runtime exception: MQJMS1111: JMS1.1 The required Queues/Publish Subscribe services are not set up (Doc ID 1347708.1)

Last updated on AUGUST 17, 2011

Applies to:

Oracle SOA Platform - Version: 11.1.1.4.0 and later   [Release: 11gR1 and later ]
Information in this document applies to any platform.

Symptoms

You have an installation of Oracle Fusion Middleware 11g Release 1 Patchset 3 (11.1.1.4.0) where you have developed and deployed composites that leverage the Oracle JMS Adapter to access JMS messages that are utilizing IBM WebSphere MQ for message transport/persistence services.

The composite application is polling for the arrival of messages that have been created to follow a publish/subscribe paradigm and are therefore stored within an IBM WebSphere MQ Topic. The composite application deploys successfully but at execution time, within the diagnostic log for the SOA managed server (${DOMAIN_HOME}/servers/soa_server1/logs/soa_server1-diagnostic.log) you receive the following exception:

[2011-08-04T19:38:31.303-04:00] [soa_server1] [WARNING] [oracle.soa.adapter]
[tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@15107b2]
[userId: <anonymous>] [ecid: 0000J6N6ExRFo2f_TXT4ic1EEm^h000002,0]
[APP: soa-infra] JMSAdapter READ_MSGS_FROM_TOPIC [[
BINDING.JCA-12134
ERRJMS_ERR_CR_TOPIC_CONS.
ERRJMS_ERR_CR_TOPIC_CONS.
Unable to create Topic consumer due to JMSException.
Please examine the log file to determine the problem.

at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:559)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:493)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:346)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:920)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:894)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:151)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: javax.jms.JMSException:
           MQJMS1111: JMS1.1 The required Queues/Publish Subscribe services are not set up {0}

at com.ibm.mq.jms.MQConnection.setSubscriptionStores(MQConnection.java:3755)
at com.ibm.mq.jms.MQConnection.getMQPubSubServices(MQConnection.java:3686)
at com.ibm.mq.jms.MQSession.addPubSubServices(MQSession.java:6609)
at com.ibm.mq.jms.MQSession.createTopic(MQSession.java:4688)
at com.ibm.mq.jms.MQTopicSession.createTopic(MQTopicSession.java:623)
at oracle.tip.adapter.jms.JMS.JMSDestination.getTopic(JMSDestination.java:108)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:531)
... 8 more

]]

Changes

You *may* have previously been successful when accessing an MQ 6.0 Server environment using MQ 6.0 client libraries and the same JMS Adapter configuration but see the errors when the SOA environment is re-configured to access an MQ 7.0 Server.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms