Remote JNDI Lookup using Logical DNS Name from Veritas Cluster Server service

(Doc ID 423371.1)

Last updated on OCTOBER 20, 2017

Applies to:

Oracle Containers for J2EE - Version: 10.1.3.1.0 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.
***Checked for relevance on 07-Apr-2012***

Symptoms

When doing JNDI lookups from a remote client using the provider url
(opmn:ormi://logicalhostname:18510:oc4j/app)

fails with error "Error obtaining server list form OPMN on host..."

If, the provider url
opmn:ormi://hostname:18510:oc4j/app

is used, everything is fine.

Since the machine is part of a cluster it is important to be able to use the logical host name in
the JNDI lookup provider url. Logical hostname is actually a Veritas Cluster Server service
group. This group's hostname is used by the RMI/JNDI clients. The logical hostname has its own ip
address that differs from the ip of the actual host running the AS instances.

Using a logical hostname is desirable since the cluster server might fail over to another machine
and the clients should not have to know about the hostnames of the hosts that are part of the
cluster.

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