My Oracle Support Banner

NameNotFoundException When Doing a Lookup of the JNDI Tree for the Resource in Oracle GlassFish Server (Doc ID 1499513.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle GlassFish Server - Version 3.1.2 and later
Information in this document applies to any platform.

Symptoms

The following is the scenario which triggers this problem:

There are two clusters. Cluster A runs client applications that access services via RMI-IIOP on cluster B. Cluster A also has a local JDBC connection pool defined. The application running on cluster A can look up the connection pool on cluster A successfully. After doing so, it looks up the remote service on cluster B. Once that remote lookup is done it is no longer possible to perform a lookup for any resource local to cluster A. Only resources on cluster B can be looked up.  A restart of the cluster is required to restore the ability to lookup cluster A resources.

NameNotFoundException is thrown in the GlassFish Server log when doing a lookup of the JNDI tree for the resource.  The log shows the following stack trace for the exception.

 






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
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.