Error with SessionBeans:Destination Unreachable

Question

Hi all,
I'm trying to develop a simple Session Bean using Weblogic 8.1.
While deploying i got message as ejbc successful.
But while running client application i got following error.
Please anyone help to resolve this.
Thanks,
latha
E:\slsb>java Client
Exception in thread "main" javax.naming.CommunicationException [Root exception i
s java.net.ConnectException: t3://raghu:7001: Destination unreachable; neste
d exception is:
java.net.SocketException: Invalid argument: connect; No available router
to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
nTranslator.java:47)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
tialContextFactoryDelegate.java:636)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:306)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at Client.main(Client.java:12)
Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachab
le; nested exception is:
java.net.SocketException: Invalid argument: connect; No available router
to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:296)
... 7 more

Answer 1

Please check the following:
1. Check whether the weblogic is running on the localhost.
2. Check the port address is right or wrong
(I have never used weblogic so I can't tell you how to check it, if you don't know then browse the google)
3. Change the server name to 127.0.0.1 in the client code.
If the server is running perfectly at 127.0.0.1:7001 then there should be no problem. So check this constraints first.
Note: I have used Websphere there are lots of ports, the one I need for lookup in websphere is the BOOTSTRAP_ADDRESS. There are many other ports also. In websphere one can create multiple profile and for that profil;e this prot address varies from 2809,2810... etc.. I don't know whether in weblogic it is called as BOOTSTRAP_ADDRESS or not. But you have ensure that the particular port for weblogic (to perform lookup) is 7001 in your m/c. Please search through google for getting information on how to know the port in weblogic.