My Oracle Support Banner

Clarity Around Actual MMP Connection Failures (Doc ID 2823235.1)

Last updated on NOVEMBER 23, 2021

Applies to:

Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.

Goal

Looking for some clarity around actual MMP connection failures.

Referring to:
Does Tsock_connectbyname Try Again Automatically When It Gets “failed To Bind The Socket”? (Doc ID 2361269.1)

The above document says, "Basically, the warning can be ignored if the address is 0.0.0.0; but could indicate a problem otherwise."
It also describes what the error looks like when it can be ignored, but it would be helpful if it also described the error when it really is a problem.

Also, ignoring an error that happens hundreds of thousands of times per day is not fun, as there were 83,000 during one hour.

Referring to:

Enh Bug 31112151 - Reduce warnings from tsock_connectbyname() when large numbers of established client connections

As per the README, this Enh is marked as having been Fixed in MS 8.1.0.6
Despite this, lots of these messages are being observed using Messaging Server 8.1.0.12.20210903 64bit (built Sep  3 2021).

A problem was observed with another app component apparently running out of ephemeral ports, on these same systems.

The presence of these errors from AService adds to the confusion, makes it more difficult to identify if there really is a problem.
 

Solution

To view full details, 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 a vibrant support community of peers and Oracle experts.