File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes Communication error while calling EJB from WAS Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Communication error while calling EJB from WAS" Watch "Communication error while calling EJB from WAS" New topic
Author

Communication error while calling EJB from WAS

suressssss mannnnnn
Greenhorn

Joined: Mar 26, 2005
Posts: 1
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.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Communication error while calling EJB from WAS
 
Similar Threads
How to access EJB deployed in Different Machine in websphere
J2ee application client not working!!!!
Operation timed out Error
Qualified EJB Name in Cluster
Problem in executing remote Java Swing client of an EJB application