WsnInitCtxFac NMSV0602E: Naming Service unavailable -communications error - Websphere

This is a discussion on WsnInitCtxFac NMSV0602E: Naming Service unavailable -communications error - Websphere ; Invoking ejb method (running ejb client) from wps portal 5.1 /WAS 6 and ejb server is running on WAS 6.1 . They are on different networks through firewall. I did following things 1) opened fire wall rules for ports between ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: WsnInitCtxFac NMSV0602E: Naming Service unavailable -communications error

  1. WsnInitCtxFac NMSV0602E: Naming Service unavailable -communications error

    Invoking ejb method (running ejb client) from wps portal 5.1 /WAS 6
    and ejb server is running on WAS 6.1 . They are on different networks through firewall.

    I did following things
    1) opened fire wall rules for ports between server and client
    2) made CSIv2_SSL setting coprrectly & exported LTPA token
    3)using correct bootstrap port numbers


    The EJB invocation works fine locally from RAD6 (client & server on same network)

    but when we call ejb method through firewall it gives following exception :

    WsnInitCtxFac W NMSV0602E: Naming Service unavailable. A communications error occurred.

    * could some body help here as what needs to done , your help is much apprecited


    Thanks in Advance

  2. Re: WsnInitCtxFac NMSV0602E: Naming Service unavailable -communications er

    I found the following on IBM portal - but not tried it tough


    ================================================== ====================
    NMSV0602E: Naming Service unavailable. A communications error occurred.


    Cause
    If BOOTSTRAP_ADDRESS is not specify in the setupClient.sh|bat file, during the execution of the launchClient.sh|bat command, the NMSV0602E warning message will be generated when trying to connect to a remote server or local server.

    Resolving the problem
    There are two solutions to work around this problem:

    A. Edit SERVERPORTNUMBER in the setupClient.sh|bat file.

    The setupClient file is under the Ports panel and there you will find the port.

    UNIX Example using BootstrapPort of a remote server equal to 2822

    /launchClient.sh -CCBootstrapPort=2822

    Note: Depending on your application to the remote connection, additional parameters may be required to execute launchClient.sh command.

+ Reply to Thread