Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Communication error while calling EJB from WAS

 
suressssss mannnnnn
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am having the following environment setup.
machine A - Solaris Webspshere Application Server 5.0
machine B - Solaris Webspshere Application Server 5.0
machine C - Windows WSAD Server Test enironment.

I have deployed an EJB in machine A, machine B and machine C.

I am able to call the ejbs from Machine A and Machine B from machine C.(using jsp client).
Client(C) Server(A or B) --> Successful.


When I try to call the ejb from machine A TO machine B or machine B to machine A or machine A to machine C or machine B to machine C.
Client(B) Server(A or C) --> failure.
Client(A) Server(C or B) --> failure.

I am to ping and telnet to ORB port for all machines.

I am getting the following error,
NMSV0602E: Naming Service unavailable. A communications error occurred.
Explanation: A connection to the name server could not be made when attempting create an initial context.
User Response: The most like causes are that the provider URL is incorrect or that the name server identified by the provider URL is not running. Make sure that the name server is running and that the host and port in the provider URL are correct. Also, make sure that the host identified in the provider URL can be ping'ed from the machine on which the JNDI client is running. Refer to the trace output accompanying this message for more information about the root cause.

From the solaris machine(A&B) I am not able to call any other EJBS. But I am able to call the ejbs from Solaris (A&B) from my WSAD(C).

Is there any security restrictions there in Solaris WAS for blocking outgoing requests?

Pls help me .

Thanks
Suresh.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic