DM_EAI Must Have Socket Connection/Read Timeout Configuration
Last updated on FEBRUARY 23, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.3.0]
On Oracle Communications Billing and Revenue Management(BRM), 220.127.116.11.0. Version,
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.
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