Portal error - Unable to start service. [BRN.118.1022]

, , ,
1

Purpose: This sections helps in solving the following issue of broker settings not proper in portal. You may experience the following log trace in Portal log files. This problem cud occur if there is an error during manual editing of config files in Portal server.

2009-10-21 18:39:34 BST (messaging : FATAL) - JMSProvider.onStartup() : Unable to start service. [BRN.118.1022] Broker Storage Read Error: Unable to load context WmJmsNamingContext from: Broker::JmsNaming::WmJmsNamingContext. Broker Exception: The host ‘’ was found, but no Broker Server is running on port of that host.; class com.webMethods.rtl.msg.jms.broker.BrokerProvider, role master=true
javax.naming.CommunicationException: [BRN.118.1022] Broker Storage Read Error: Unable to load context WmJmsNamingContext from: Broker::JmsNaming::WmJmsNamingContext. Broker Exception: The host ‘’ was found, but no Broker Server is running on port of that host. [Root exception is Broker Not Running (101-1020): The host ‘’ was found, but no Broker Server is running on port of that host.
]
at com.webMethods.jms.naming.BrokerContextStore.loadBindings(BrokerContextStore.java:310)
at com.webMethods.jms.naming.WmJmsNamingContext.(WmJmsNamingContext.java:81)
at com.webMethods.jms.naming.WmJmsNamingCtxFactory.getInitialContext(WmJmsNamingCtxFactory.java:34)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)

Caused by: Broker Not Running (101-1020): The host ‘’ was found, but no Broker Server is running on port of that host.
at COM.activesw.API.client.BrokerConnection.init(BrokerConnection.java:469)
at COM.activesw.API.client.BrokerConnection.getConnection(BrokerConnection.java:737)
at COM.activesw.API.client.BrokerClient.initClient(BrokerClient.java:9510)
at COM.activesw.API.client.BrokerClient.(BrokerClient.java:505)
at com.webMethods.jms.naming.BrokerConnection.connectToBroker(BrokerConnection.java:110)
at com.webMethods.jms.naming.BrokerContextStore.loadBindings(BrokerContextStore.java:111)

2009-10-21 18:40:05 BST (eventService : WARN) - Error obtaining service for JMS topic com.webMethods.nis.events, exception :[POP.011.0044] Error obtaining JMS topic for name: “com.webMethods.nis.events”
com.webMethods.portal.system.PortalRuntimeException: [POP.011.0044] Error obtaining JMS topic for name: “com.webMethods.nis.events”
at com.webMethods.rtl.msg.jms.JMSTopic.(JMSTopic.java:116)
at com.webMethods.rtl.msg.jms.JMSTopic.(JMSTopic.java:94)
at com.webMethods.rtl.event.RemoteDeliverer.initJMS(RemoteDeliverer.java:129)

2009-10-21 18:40:06 BST (eventService : WARN) - Error obtaining service for JMS queue com.webMethods.nis.heartbeat.event.queue, exception :[POP.011.0053] Error obtaining JMS queue for name: “com.webMethods.nis.heartbeat.event.queue”
com.webMethods.portal.system.PortalRuntimeException: [POP.011.0053] Error obtaining JMS queue for name: “com.webMethods.nis.heartbeat.event.queue”
at com.webMethods.rtl.msg.jms.JMSQueue.(JMSQueue.java:75)
at com.webMethods.rtl.event.QueueDeliverer$EventQueue.initJMS(QueueDeliverer.java:252)
at com.webMethods.rtl.event.QueueDeliverer$EventQueue.start(QueueDeliverer.java:209)
at com.webMethods.rtl.event.QueueDeliverer.start(QueueDeliverer.java:46)
at com.webMethods.rtl.event.DeliveryService.startRemoteDelivery(DeliveryS

Steps to follow

  1. Ensure brokerServer is up and running in its port (for e.g., 6159)
  2. Ensure BrokerServer is configured properly in IntegrationServer
  3. Navigate to file path mentioned below and follow steps

STOP THE PORTAL SERVER

Please take a backup of the below file before editing
brokerJMS.xml <WM_HOME>/Portal/server/default/config
server.xml <WM_HOME>/Portal/server/default

Edit brokerJMS.xml

  1. Find the following tag section




  3. Check for BrokerName, hostname and port details
  4. Verify and edit correct details
  5. Save the file

Edit server.xml

  1. Find the following tag section

  2. false
    <JMS_BROKER_NAME type=‘java.lang.String’>BrokerName</JMS_BROKER_NAME>
    <JMS_HOST type=‘java.lang.String’>hostname</JMS_HOST>
    <JMS_PORT type=‘int’>port</JMS_PORT>
  3. Check for BrokerName, hostname and port details
  4. Verify and edit correct details
  5. Save the file
  • Restart the Portal Server
  • Check for the Portal logs progress. You should not be getting any errors related to Broker Connection with MWS.
  • Navigate to Messaging in MWSConsole
  • Check and confirm your brokerServer is connected and configured properly.

Suggestions are welcome

Regards
Karpaga V