File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes BEA/Weblogic and the fly likes Getting CommunicationException Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Getting CommunicationException" Watch "Getting CommunicationException" New topic
Author

Getting CommunicationException

sathish kannan
Greenhorn

Joined: Jul 11, 2002
Posts: 29
Hi

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


t3://ipaddress ortnumber

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

ankush purwar
Ranch Hand

Joined: Sep 02, 2005
Posts: 46
Try to use IP Address rather than name.
sathish kannan
Greenhorn

Joined: Jul 11, 2002
Posts: 29
I tried with both IP address and hostname, it is not working.
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61092
    
  66

"sathish", you have already been asked on at least one other occasion to adjust your display name to meet JavaRanch standards. This is not optional. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it prior to your next post.

Be aware that accounts with invalid display names are removed.

bear
JavaRanch Sheriff


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
ankush purwar
Ranch Hand

Joined: Sep 02, 2005
Posts: 46
The other causes may your cluser configuration or network configuration.
Try to check it over there ?
Satish Kumar
Greenhorn

Joined: Mar 13, 2006
Posts: 1
Hi Satish,

I too am facing the same problem, can you let me know how the issuse was solved.

Regards,
Satish
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61092
    
  66

"Satish",

Same thing goes for you as for "sathish" -- take a look at the JavaRanch Naming Policy and adjust your display name to match it.

Your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.

bear
JavaRanch Sheriff
Sreeni Mallela
Greenhorn

Joined: Mar 29, 2006
Posts: 3
Hi Satish,

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.

Thanks
Sreeni


Sreeni Mallela
Sreeni Mallela
Greenhorn

Joined: Mar 29, 2006
Posts: 3
Hi,

In connection with my previous mail, here i am posting
Enviroment :

weblogic 9.1
JRE 1.5.0_06

Thanks
Sreeni
subramanian arumugam
Greenhorn

Joined: Aug 08, 2007
Posts: 3
Hi

Please share the solution of this problem

Thanks
subramanian
subramanian arumugam
Greenhorn

Joined: Aug 08, 2007
Posts: 3
Hi

Please share the solution of this problem

Thanks
subramanian
subramanian arumugam
Greenhorn

Joined: Aug 08, 2007
Posts: 3
Hi

Please share the solution of this problem

Thanks
subramanian
sathish kannan
Greenhorn

Joined: Jul 11, 2002
Posts: 29
Hi Sreeni

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.

Regards
Sathish
Kevin Cross
Greenhorn

Joined: Feb 01, 2005
Posts: 1
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.
Fausto Calderazzo
Greenhorn

Joined: Nov 26, 2008
Posts: 5
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 ]
Hemanth H Bhat
Greenhorn

Joined: Apr 14, 2008
Posts: 15
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
 
wood burning stoves
 
subject: Getting CommunicationException