This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am trying to communicate from local Window WLS(8.1) to Unix WLS(8.1) which is clustered with two servers. I am using T3 protocol to communicate from local to UNIX as mentioned below
But it is giving the following error, javax.naming.CommunicationException. Root exception is java.net.ConnectException: t3://dappsn03-04.asianconnect.com:8301: Bootstrap to dappsn03-04.asianconnect.com/192.168.32.17:8301 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:125) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239) at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) 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 javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) I am using Initial Context to get the connection and here is the program:Can anyone help me to resolve this
I am getting the same error, when i run applet from IE through HTML. Did you got any solution for this.please tell me how to resolve this problem.
here is posing error for tracking purpose.
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) basic: Exception: java.lang.NullPointerException
please help me.
Joined: Mar 29, 2006
In connection with my previous mail, here i am posting Enviroment :
i completely forgot the solution how i resolved it. But the mail reason was, since it was clustered, the network administer will be giving the appropriate URL which will be connecting to either of the server. It works similar to load balancer. Earlier i was not giving the proper URL/Domain name.
I had the same problem when I was trying to start a managed node on a machine that was not also running the admin node. I tried replacing the machine name with the IP address on the managed node that had the problem but this made no difference.
I then noticed that the machine I was attempting to start the managed node on did not have an entry in the hosts file of the machine that running the admin server (I am not using DNS) so I added an entry. My managed node now starts.
I assume that the admin node will only accept requests from the managed nodes it is configured with but as the config of the managed node only had the name of the machine it had no way of determining which machine the request was coming from without the entry in /etc/hosts (in the absence of a DNS).
This may not be your problem but I hope it helps you to along the right lines.
Still wonder why executing the InitialContext code before the invocation of the libs provided lead to a different exception, but at least the problem seems to be the lack of etc/host configuration. The problem has been solved adding the definition of the host. [ November 28, 2008: Message edited by: Fausto Calderazzo ]
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 ......