• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

Communication error while calling EJB from WAS

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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.
 
Did Steve tell you that? Fuh - Steve. Just look at this tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
reply
    Bookmark Topic Watch Topic
  • New Topic