My Oracle Support Banner

No Data Returned While Reading BODYEOB Response Length, Repeating Read (Doc ID 2904248.1)

Last updated on NOVEMBER 22, 2023

Applies to:

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

Symptoms

On : Oracle Communications Messaging Server 8.1.0.19.20220711

A message was stuck in the queue on an "MTA" system, trying to go out through an "MX" system, but repeatedly failing.

From "imsimta qm history", originally, the failures were:

 

It seems like it is only waiting 1 minute rather than the specified timeout=300, so it seems like the timeout is not being obeyed.

This is effecting more than just the outbound traffic.
A couple of hundred thousand di="451 4.3.0 Unable to read CONNECT response length [slot 1 name 1]" errors have been observed for connections coming in from the Internet, in the last week.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.