"!app", "!bea", "!comp" is displayed in JNDI tree, and failed to register a context (Doc ID 1957056.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle WebLogic Server - Version 10.3.6 to 10.3.6
Oracle WebLogic Server - Version 12.1.1.0 to 12.1.1.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

 When a Connection Factory of JMS module is used, and Local JNDI Name "java:" is set,
there will be "!app", "!bea" and "!comp" in JNDI tree, and JNDI context below "java:" cannot be registered.
A sample case to reproduce this problem is described below.

For example, to execute the workaround of Document:1283599.1,
Access to Admin console,
go to services -> messaging -> JMS modules -> (Any created JMS Module) -> (Any created Connection Factory) -> advanced,
and set Local JNDI Name as "java:/ConnectionFactory". Save this change and activate it.


After applying this change, access to any server which is targetted as JMS Module.
Go to (Any targetted server) -> config -> general tab and click the item of JNDI tree.

It will be confirmed that there are "!app", "!bea" and "!comp" in JNDI tree.
There is no context under "java:" context.

Note: If some namings are used for Local JNDI Name instead of "java:/ConnectionFactory", the results are below.

"java:/ConnectonFactory1": reproduced
"java1:/ConnectionFactory1": not reproduced
"java1:/ConnectionFactory": not reproduced
"foo:/bar": not reproduced

Author could not confirmed this problem with the name "java", "javax", "weblogic".
And this problem could not be confirmed on WLS 12.1.3, too.

 

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