My Oracle Support Banner

Web App Startup Fail Because Jndi Name Not Found Exception (Doc ID 1556832.1)

Last updated on FEBRUARY 05, 2019

Applies to:

Oracle WebLogic Server - Version 10.3.1 and later
Information in this document applies to any platform.

Symptoms

Application got a problem from jndi NameNotFoundException.

There are two servers within cluster, one is named ms01 and another is ms02, and all the jms services(distribute queue) within them were targetted to migratable targets, for example: jms_for_ms01 to ms01(migratable) and jms_for_ms02 to ms02(migratable).

NameNotFoundException is thrown when implementing the following steps:

1. Migrate jms service within ms01 to ms02(migration success)
2. Shutdown ms01
3. Start ms01
4. During starting ms01 process, the application deployed at ms01 got jndi name not found exception and server start failed since application start failed.

 

Detailed Steps to reproduce the issue:

1. Build domain

1.1. Configure a domain named "jms_domain"
1.2. Create 2 servers, named "ManagedServer1" and "ManagedServer2"
1.3. Create a cluster named "Cluster-0", add the servers "ManagedServer1" and "ManagedServer2" to this cluster.
1.4. Create a Machine name "Machine-0"
1.5. Configure Node Manager and add servers "ManagedServer1" and "ManagedServer2"
1.6. Start managed servers

2. Configure JMS

2.1 Create a FileStore named "jmsfs1", target to server "ManagedServer1(migrateable)"
2.2 Create a FileStore named "jmsfs2", target to server "ManagedServer2(migrateable)"
2.3 Create a JMS Server "JMSServer1" with persistent store "jmsfs1", and target to "ManagedServer1(migrateable)"
2.4 Create a JMS Server "JMSServer2" with persistent store "jmsfs2", and target to "ManagedServer2(migrateable)"
2.5 Create a JMS Module named "JMSModule1" and target to cluster "Cluster-0"
2.6 Create a Subdeployment "subdeployment-all", target to "JMSServer1" and "JMSServer2"
2.7 Create a Distributed Queue, name is "dist-queue-1", jndi is "dist-queue-1", target to "subdeployment-all"

3.Deploy test case

3.1 Deploy customer uploaded test case "APlusWeb.war", target to "Cluster-0" and start the application.

4.Test Process

4.1 Logon WebLogic Admin console and click "Lock & Edit"
4.2 Navigate to jms_domain -> Environment -> Migratable Targets
4.3 Check "ManagedServer1 (migratable)" and "New hosting server" select another server, then click "Migrate" button.
4.4 Wait until "Status of Last Migration" change to "done", and click "Activate Changes"
4.5 Navigate to jms_domain -> Environment -> servers -> Control
4.6 Check "ManagedServer1" and click "Shutdown->Force Shutdown Now" button
4.7 Check "ManagedServer1" and click "Start" button.
4.8 Wait a while, till the State of "ManagedServer1" change to "ADMIN", and the "Status of Last Action" change to FAILED.
4.9 View "ManagedServer1" log
4.10 You will see a NameNotFoundException in the log file. Following is the detail error message:

Changes

 

Cause

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
Symptoms
 Detailed Steps to reproduce the issue:
Changes
Cause
Solution
References


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