dumpNameSpace Command Invocation Fails with javax.naming.ServiceUnavailableException

Technote (troubleshooting)


Problem(Abstract)

When invoking the dumpNameSpace command against an application server JVM, it results in a failure similar to the following:

Getting the initial context ERROR: Could not get the initial context or unable to look up the starting context.
Exiting: Exception received: javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:localhost:2811".
Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809.
Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. [
Root exception is org.omg.CORBA.OBJ_ADAPTER: ORB_CONNECT_ERROR (5) - couldn't get Server Subcontract:org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No vmcid: IBM minor code: B8F completed: No]
javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:localhost:2811". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. Root exception is org.omg.CORBA.OBJ_ADAPTER: ORB_CONNECT_ERROR (5) - couldn't get Server Subcontract:org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No vmcid: IBM minor code: B8F completed: No
at com.ibm.rmi.corba.ORB.connect(ORB.java:3595)
at com.ibm.rmi.corba.ORB.internalConnect(ORB.java:3619)
at com.ibm.CORBA.iiop.ORB.internalConnect(ORB.java:2055)

Cause

This particular exception can occur if the following two conditions are met:

(1) Global security is disabled on the target application server

(2) sas.client.props file contains this entry:
com.ibm.CORBA.securityEnabled=true

This is a mismatch whereby the client believes that security is enabled, but the server is not enforcing security.

In the problem scenario above, the client is the dumpNameSpace script.


Resolving the problem

The solution is to do one of the following:

1. If security is required, configure and enable global security on the target application server.

or

2. If security is not required, change the sas.client.props file to contain the following entry:

com.ibm.CORBA.securityEnabled=false


Cross reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
JNDI/Naming

Software version:

6.1, 7.0, 8.0, 8.5, 8.5.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

Base, Enterprise, Network Deployment

Reference #:

1221317

Modified date:

2005-11-01

Translate my page

Machine Translation

Content navigation