MQSeries.net :: View topic

oinvertedworld · Posted: Tue Feb 19, 2008 4:28 am Post subject: Able to publish but not subscribe

Hi,

I am using WAS 6 and MQ 6 and have a TopicConnectionFactory (jms/topicFactory) and Topic Destination (jms/forwardedAlerts) configured in WAS 6. I have an EAR application with one MDB that reads from a Queue and then connects to the TopicConnectionFactory and publishes a message on that topic. This works fine.

But I also have another EAR file with an MDB bean (HTTPDeliveryBean) that is configured to listen on a listener port that is bound to the same TopicConnectionFactory and Topic Destination. When a message is published to that topic (from the other EAR), I get a NoBrokerResponseException from the EAR with HTTPDeliveryBean, and HTTPDeliveryBean never gets created or invoked. (Note that I have set the broker version to 1)

Below is the detailed stack trace that I get:

00000038 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jms/topicFactory. The exception which was received is com.ibm.mq.jms.NoBrokerResponseException: MQJMS5053: *** No broker response. Please ensure that the broker is running. If you are using the WebSphere MQ broker check that your brokerVersion is set to V1 ***

00000083 JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB HTTPDeliveryBean , JMSDestination jms/forwardedAlerts : com.ibm.mq.jms.NoBrokerResponseException: MQJMS5053: *** No broker response. Please ensure that the broker is running. If you are using the WebSphere MQ broker check that your brokerVersion is set to V1 ***
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.getBrokerResponse(MQBrokerSubscriptionEngine.java:3041)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openSubscription(MQBrokerSubscriptionEngine.java:307)
at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openSubscription(MQMigrateSubscriptionEngine.java:200)
at com.ibm.mq.jms.MQConnectionBrowser.pubSubSetup(MQConnectionBrowser.java:429)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:306)
at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:130)
at com.ibm.mq.jms.MQConnection.createConnectionBrowser(MQConnection.java:3591)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:456)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:360)
at com.ibm.mq.jms.MQConnection.createConnectionConsumer(MQConnection.java:3128)
at com.ibm.ejs.jms.JMSTopicConnectionHandle.createConnectionConsumer(JMSTopicConnectionHandle.java:112)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:526)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:653)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:962)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java(Compiled Code))
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2033
at com.ibm.mq.MQQueue.getMsg2(MQQueue.java:1071)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.getBrokerResponse(MQBrokerSubscriptionEngine.java:3034)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openSubscription(MQBrokerSubscriptionEngine.java:307)
at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openSubscription(MQMigrateSubscriptionEngine.java:200)
at com.ibm.mq.jms.MQConnectionBrowser.pubSubSetup(MQConnectionBrowser.java:429)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:306)
at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:130)
at com.ibm.mq.jms.MQConnection.createConnectionBrowser(MQConnection.java:3591)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:456)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:360)
at com.ibm.mq.jms.MQConnection.createConnectionConsumer(MQConnection.java:3128)
at com.ibm.ejs.jms.JMSTopicConnectionHandle.createConnectionConsumer(JMSTopicConnectionHandle.java:112)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:526)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:653)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:962)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java(Compiled Code))
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))

-I have run dspmqbrk to ensure that the broker is running.
-I have also run the MQ-included script that creates the JMS queues.

Here is my resource.xml configuration:

- <factories xmi:type="resources.jms.mqseries:MQTopicConnectionFactory" xmi:id="MQTopicConnectionFactory_1203323189344" name="topicConnectionFactory" jndiName="jms/topicFactory" authMechanismPreference="BASIC_PASSWORD" XAEnabled="true" port="0" transportType="BINDINGS" queueManager="MyQM" brokerQueueManager="MyQM" brokerVersion="MA0C" clientID="client1" cloneSupport="false" pubSubCleanup="SAFE" pubSubCleanupInterval="3600000" msgSelection="CLIENT" publishAckInterval="25" sparseSubscriptions="false" statRefreshInterval="60000" substore="MIGRATE" multicast="DISABLED" directAuth="BASIC" failIfQuiesce="true" pollingInterval="5000" rescanInterval="5000" useConnectionPooling="true">
<connectionPool xmi:id="ConnectionPool_1203323189344" />
<mapping xmi:id="MappingModule_1203323189344" mappingConfigAlias="DefaultPrincipalMapping" authDataAlias="" />
<sessionPool xmi:id="ConnectionPool_1203323189345" />
</factories>
<factories xmi:type="resources.jms.mqseries:MQTopic" xmi:id="MQTopic_1203388222797" name="deliveryTopic" jndiName="jms/forwardedAlerts" persistence="APPLICATION_DEFINED" priority="APPLICATION_DEFINED" specifiedPriority="0" expiry="APPLICATION_DEFINED" specifiedExpiry="0" baseTopicName="forwardedAlerts" useNativeEncoding="false" integerEncoding="Normal" decimalEncoding="Normal" floatingPointEncoding="IEEENormal" targetClient="JMS" />
</resources.jms:JMSProvider>

Any help would be much appreciated as I am truly at my wits' end on this!

Much thanks