[ Plnwvr ] ProjectID : 13 [ Plnwvr ] UserID : 8557 [ Plnwvr ] Server : localhost [ Plnwvr ] Port : 80 [ Plnwvr ] Protocol : T3 [ Plnwvr ] NB : Using T3 protocol. If this fails, please attempt using HTTP ! [ Plnwvr ] URL is : t3://localhost:80 [ Plnwvr ] null javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:80: Bootstrap to localhost/127.0.0.1:80 failed. It is likely that the remote side declared peer gone on this JVM] at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:48) at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:739) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:345) at weblogic.jndi.Environment.getContext(Environment.java:263) at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117) at javax.naming.spi.NamingManager.getInitialContext(Unknown Source) at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at javax.naming.InitialContext.init(Unknown Source) at javax.naming.InitialContext.<init>(Unknown Source) at com.planweaver.client.MasterApplet.getInitialContext(MasterApplet.java:1064) at com.planweaver.client.MasterApplet.init(MasterApplet.java:219) at sun.applet.AppletPanel.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.net.ConnectException: t3://localhost:80: Bootstrap to localhost/127.0.0.1:80 failed. It is likely that the remote side declared peer gone on this JVM at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199) at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:137) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:331) ... 10 more Caused by: java.rmi.ConnectException: Bootstrap to localhost/127.0.0.1:80 failed. It is likely that the remote side declared peer gone on this JVM at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:329) at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:255) at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:199) at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:220) at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:187) ... 12 more java.lang.NullPointerException at com.planweaver.client.MasterApplet.init(MasterApplet.java:290) at sun.applet.AppletPanel.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
Please help me.
Thanks Sreeni Mallela
Sreeni Mallela
Romano Guizzetti
Greenhorn
Joined: Oct 18, 2006
Posts: 1
posted
0
Hi, I had the same error and the problem was that caller was using a DNS name and callee answered using IP. In your case since you are using localhost may be that Weblogic is not configured to listen on all addresses (localhost + machine name + IP). I hope this can help you.
Regards
Romano
Hemanth H Bhat
Greenhorn
Joined: Apr 14, 2008
Posts: 15
posted
0
Well i also encountered the same problem when posting a message on to the JMS queue This queue is deployed on a managed server on weblogic 8.1
the actual problem here is if you give the Listen Address (The IP address or DNS name this server uses to listen for incoming connections) under myserver----> Configuration---->general---->Listen Address: TAB if there is a DNS Name entered here then you will encounter this problem
please clear this text box and your problem would be resolved ......
Regards
Hemanth
Hemanth H Bhat
Greenhorn
Joined: Apr 14, 2008
Posts: 15
posted
0
Well i also encountered the same problem when posting a message on to the JMS queue This queue is deployed on a managed server on weblogic 8.1
the actual problem here is if you give the Listen Address (The IP address or DNS name this server uses to listen for incoming connections) under myserver----> Configuration---->general---->Listen Address: TAB if there is a DNS Name entered here then you will encounter this problem
please clear this text box and your problem would be resolved ......
Regards
Hemanth
scott edmiston
Greenhorn
Joined: Dec 04, 2009
Posts: 1
posted
0
solution that worked for me is while configuring the admin server supply its IP address as Listen address instead of domain name and same with managed server listen address. Also use a different port for managed server (listen port) property