My Oracle Support Banner

What do these errors indicate? weblogic.jms.common.jmsexception: Could Not Find Server $servername (Doc ID 1248564.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.
***Checked for relevance on 1-Oct-2015***

Goal

What do errors like these indicate when they occur during startup of Weblogic Server?

weblogic.jms.common.JMSException: could not find Server <servername> Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server <servername> Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:<servername>'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:<servername>'>
....
<Aug 11, 2010 2:15:16 PM GMT+00:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: <ejbname> is unable to connect to the JMS destination: <jms resource name>.

Solution

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
Goal
Solution


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