Admin Server Dies When Accessing Managed Server's JNDI Tree (Doc ID 1471472.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version 10.3.4 to 12.1.1.0
Information in this document applies to any platform.

Symptoms

When an empty JNDI name element exists in the JDBC config file, the admin server process will crash with no error message. Below is the test to reproduce the crash:

  1. Create a datasource with a JNDI name.
  2. Target the datasource to the managed server.
  3. Remove the JNDI name from the JDBC config file (i.e., <jndi-name></jndi-name>).
  4. Restart the domain.
  5. Try to display the managed server's JNDI tree.
  6. The admin server's java process terminates without any information in the server log. No dump/core file is created.

The same result was observed on WLS 10.3.4, 10.3.5, 10.3.6, and 12.1.1. Also note that the admin server dies only in production mode. In development modes an OutOfMemoryError occurs instead.

Changes

WLS was upgraded from 10.3.0 to 10.3.4.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms