2 Replies Latest reply: Jun 21, 2012 4:58 AM by 945010 RSS

    Getting JMS Exception while starting the managed servers

    945010
      Hi ,

      I have Savvion BPM tool hosted on WebLogic server 10.3 version.Before the manage servers coming to Running state its throwing the below mention warning message.Can anybody help me to identify what could be the reason the managed server the below exceptions.

      Thanks in advance...


      <Jun 19, 2012 3:54:32 AM EDT> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server sbmejb2.>
      <Jun 19, 2012 3:54:33 AM EDT> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server sbmejb2.>
      <Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
      <Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
      *<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLServiceMDB is unable to connect to the J*
      MS destination: jms/BLAdminTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:34 AM EDT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster addres
      s "sbmejb1,sbmejb2">
      <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCacheSyncMDB is unable to connect to the
      JMS destination: jms/BLCacheSyncTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLSessionMDB is unable to connect to the J
      MS destination: jms/SBMTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:34 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.177.16.126:16103 for pr
      otocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
      <Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "sbmejb1" for domain "sb
      m76" running in Production Mode>
      <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLBizStoreMDB is unable to connect to the
      JMS destination: jms/SBMTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCheckDueMDB is unable to connect to the
      JMS destination: jms/SBMTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLEmailMDB is unable to connect to the JMS
      destination: jms/SBMTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLResumeWSMDB is unable to connect to the
      JMS destination: jms/SBMTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MConsoleServiceMDB is unable to connect to
      the JMS destination: jms/SBMTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EPServiceMDB is unable to connect to the J
      MS destination: jms/SBMTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:42 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EventReaderBean is unable to connect to th
      e JMS destination: jms/BPAdminTopic. The Error was:
      weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
      Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
      Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
      eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
      <Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
      <Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>