My Oracle Support Banner

OC4J Web Service Intermittently Throwing javax.naming.CommunicationException Errors (Doc ID 1378751.1)

Last updated on MAY 30, 2019

Applies to:

Web Services - Version 10.1.3.0.0 to 10.1.3.5
Information in this document applies to any platform.

Symptoms


In SOA Suite 10.1.3.x a web service application calls an EJB that is deployed in WebLogic.  From time to time, an intermittent error is generated by the web service application code deployed to SOA Suite.  The error is similar to the following:

ERROR 2011-01-28 13:56:27,134 [AJPRequestHandler-RMICallHandler-1222] com.tcs.iesb.opi.ejb.OPIOrderServiceEJBImpl-
amdocs.epi.appserver.ClientConnectionException
at amdocs.epi.appserver.weblogic_8.ClientAppserverConnectionCls.lookup(ClientAppserverConnectionCls.java:153)
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://<IP>:<PORT>: Bootstrap to host1/<IP>:<PORT> failed. It is likely that the remote side declared peer gone on this JVM]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:49)
Caused by: java.net.ConnectException: t3://<IP>:<PORT>: Bootstrap to host1/<IP>:<PORT> failed. It is likely that the remote side declared peer gone on this JVM
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:204)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:154)



The only way to resolve the issue is to restart the SOA instance.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.