OC4J Web Service Intermittently Throwing javax.naming.CommunicationException Errors
Last updated on APRIL 18, 2018
Applies to:Web Services - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
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:
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://18.104.22.168:1001: Bootstrap to host1/22.214.171.124:1001 failed. It is likely that the remote side declared peer gone on this JVM]
Caused by: java.net.ConnectException: t3://126.96.36.199:1001: Bootstrap to host1/188.8.131.52:1001 failed. It is likely that the remote side declared peer gone on this JVM
The only way to resolve the issue is to restart the SOA instance.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms