CHECKIN_UNIVERSAL Call From RIDC API Is Failing With Bad Socket Error

(Doc ID 1985326.1)

Last updated on MAY 03, 2017

Applies to:

Oracle WebCenter Content - Version 11.1.1.8.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to execute the CHECKIN_UNIVERSAL service using RIDC API, an exception occurs. PING_SERVER and GET_SEARCH_RESULTS work fine.
After calling IdcClient.sendRequest(), ‘Bad socket’ errors are coming from RIDC code:

Feb 25, 2015 4:00:36 PM oracle.stellent.ridc.common.log.impl.BaseLogSupport log
WARNING: Bad socket detected, attempting retry [1]
Feb 25, 2015 4:00:36 PM oracle.stellent.ridc.common.log.impl.BaseLogSupport log
WARNING: Bad socket detected, attempting retry [2]


Then there is a 30 second delay.

Then the IdcClient.sendRequest() method throws an exception:


ERROR:
------------

oracle.stellent.ridc.protocol.ProtocolException: java.net.SocketTimeoutException: Read timed out
  at oracle.stellent.ridc.protocol.intradoc.HdaProtocol.readResponse(HdaProtocol.java:264)
  at oracle.stellent.ridc.IdcClient.sendRequest(IdcClient.java:184)
  at com.deltasoftinc.example.ridc.ContentServer.sendRequest(ContentServer.java:430)
  at com.deltasoftinc.example.ridc.ContentServer.addDocument(ContentServer.java:57)
  at com.deltasoftinc.example.ridc.RidcExample.main(RidcExample.java:45)
Caused by: java.net.SocketTimeoutException: Read timed out


Steps To Reproduce
--------------------------------
Run an RIDC Program with CHECKIN_UNIVERSAL service.

Cause

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