Connection refused error when trying to to lookup EJB in iAS

Question

Hi,
I tried to write a client that uses an EJB in an 9.0.3 iAS running on windows NT SP6, and the JNDI lookup keeps failing with the following error:
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
java.net.ConnectException: Connection refused: connect
     java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
          RMIContext.java:134
     java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
          InitialContext.java:345
     void Samplecom.mind.ejb.stubs.AccountComplexStubClient.main(java.lang.String[])
          AccountComplexStubClient.java:24
I am using the following properties for the lookup:
env.putContext.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "ias_admin");
env.put(Context.SECURITY_CREDENTIALS, "ias_admin1");
env.put(Context.PROVIDER_URL, "ormi://localhost:23791/mindejb");
Where:
* 23791 is the port configured in the rmi.xml
* mindejb is the name of the module
* ias_admin1 is the correct password of ias_admin user
Similar properties worked for a stand alone oc4j. What have I done wrong?
Any help will be appreciated.
Thanks,
Avi

Answer 1

Hi -
I can resend what I think I would have said later on. No guarantees though ;-)
What you need to do is to look at the RMI port range allocated in the opmn.xml file for the OC4J instance you are trying to connect to. OPMN basically looks at the first number, and determines if the port is free. If it is, it will use it. If it's not, it will go to the next sequential number and try that, etc.
So if you have a defined port range of 3101-3200 and you only have one process, then it's a pretty safe bet (unless another rogue process has grabbed it) that the port you need will be the first one listed - 3101. If you specified two JVM processes to be started for the instance, then it's likely that 3101 and 3102 will be used.
I think that's what I'd written in the truncated text.
In our forthcoming 904 release, we're providing a port lookup service which will be able to be used by remote clients to discover the RMI ports used for OC4J instances. This will then avoid the client (and admins) needing to know and publish the specific ports used. Since OPMN itself knows which ports have been allocated, it can be queried by remote clients to find out where to connect. I've not seen the final spec, but I think this lookup will be transparent to the client in terms of code and will only require the addition of a prefix to the provider.url property used in jndi.propeties.
It's likely to be of a format such as opmn:lookup:ormi://<known-ias-host-location>.
Sorry about the truncation, it looks like that has now been rectified for the forums.
-steve-