DM_EAI Must Have Socket Connection/Read Timeout Configuration (Doc ID 942524.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.1]
Linux x86-64
Checked for relevance on 5-Feb-2013.
***Checked for relevance on 13-Oct-2014***
*** Checked for relevance on 05-29-2016 ***

Symptoms

The dm_eai process must not rely on default TCP timeout settings. It must have its own pin.conf configurable timeout so that any socket function calls (e.g. connect(), read(), etc.) fail to return in a certain time (in seconds or sub-seconds), the operation fails (i.e. does not wait forever or until a TCP/IP level timeout of multiple minutes).

Steps To Reproduce :

Configure EAI DM (sys/dm_eai/pin.conf) for HTTP plugin and connect to a web service that is configured to receive the request and drop it without any response. Also need to be able to test hung connect and "100" continue response but nothing thereafter, of course.


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