RMI: "connection refused to host"

[Eskil Lind]

Hello.
I am using WAS 5.0.
I try to call an EJB in WAS from a batch-program (with Main) using
an ordinary jndi-lookup (iiop://hostname).
I get the error "connection refused to host" and "java.net.ConnectException: Connection refused".
I have tried both with the batchprogram residing on the same host as WAS and a host different from where the WAS is installed.
I have not enabled security or SSL on WAS. I have not changed any of the securitysettings in WAS since installation.
I wonder if the sas.client.props - file could be the problem ?
(in this file I made this change: com.ibm.CORBA.securityEnabled=false,
and I put in userid/pw for the variables: com.ibm.CORBA.loginPassword and com.ibm.CORBA.loginUserid)
In my .bat fil e for the batchprogram I refer to the sas.client.props with the statement: -Dcom.ibm.CORBA.ConfigURL="file:/C:/mydir/sas.client.props"
Is there anybody that could give me a hint on what I could check or do ?

[Rufus BugleWeed]

Am I correct in assuming that you have an application which needs to talk to a bean in the websphere contained. Did you go through the deploy process which binds all the websphere client code into your application?

[Eskil Lind]

Thanks for answer.
I have not done what you wrote in your answer.
This is my first time writing client code that are supposed to access a session bean (stateless) in websphere.
Could you please write me some lines about this bind process and where to have more information on this ?
(I am using websphere V5.0)

[Kyle Brown]

My first recommendation would be to buy my book and read the chapter on EJB client programming. My second recommendation would be to carefully read in the InfoCenter all of the chapters on EJB clients. Do a search for "launchclient.bat" and see where that leads you.
Kyle

[Rufus BugleWeed]

You can download all the websphere redbooks. It will take a lot longer than Kyle's book. Start with sg24-6195.