My Oracle Support Banner

Topic based Message Driven Bean (MDB) Application does not get Loaded in a Glassfish cluster (Doc ID 1147403.1)

Last updated on JULY 31, 2018

Applies to:

Sun Java System Message Queue - Version: 4.1 to 4.4 - Release: 4.1 to 4.4
Sun GlassFish Enterprise Server - Version: 2.1 and later    [Release: 2.1 and later]
Information in this document applies to any platform.


The Message Driven Bean (MDB) application that consumes from Topic messages does not get loaded when the Glassfish server instance is started. This could happen if the application is run in a Glassfish instance that is part of a Glassfish cluster. The failure of such an event will be logged into the instance's server.log as follows:

com.sun.messaging.jms.JMSException: [ADD_CONSUMER_REPLY(15)] [C4036]: A broker error occurred. :[503] [B4288]: Creation of consumer on topic testtopic is not allowed on service jms because service restriction [NO_SYNC_WITH_MASTERBROKER] is in effect. user=guest, broker=localhost:3700(47276)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.throwServerErrorException(
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.addInterest(
at com.sun.messaging.jmq.jmsclient.WriteChannel.addInterest(
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.addInterest(
at com.sun.messaging.jmq.jmsclient.Consumer.registerInterest(
at com.sun.messaging.jmq.jmsclient.MessageConsumerImpl.addInterest(
at com.sun.messaging.jmq.jmsclient.MessageConsumerImpl.init(
at com.sun.messaging.jmq.jmsclient.MessageConsumerImpl.(
at com.sun.messaging.jmq.jmsclient.TopicSubscriberImpl.(
at com.sun.messaging.jmq.jmsclient.UnifiedSessionImpl.createSubscriber(
at com.sun.messaging.jmq.jmsclient.UnifiedSessionImpl.createSubscriber(
at com.sun.messaging.jms.ra.SessionAdapter.createSubscriber(
[#|<Timestamp>|WARNING|sun-appserver2.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;xxxx;_RequestID=yyyyyy;|CORE5021: Application NOT loaded: [xxxx]|#]

In summary, the error "Creation of consumer on topic testtopic is not allowed on service jms because service restriction [NO_SYNC_WITH_MASTERBROKER]" indicates that the Message Queue (MQ) master broker was not up and the MDB application is not started or usable as a result.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.