IMAPd Does Not Log (nor Telemetry) The Action Which Took So Long That The Client Gave Up
(Doc ID 2969609.1)
Last updated on AUGUST 22, 2023
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
On : Oracle Communications Messaging Server 18.104.22.168.20230227
IMAPd does not log (nor telemetry) the action which took so long that the client gave up
We had a bunch of messages stuck in the ims-ms channel queue on one backend, all going to a certain user+folder.
No messages had been successfully delivered to that user+folder for over 3 hours. All attempts were failing with "mailbox is busy".
When whatever process had the lock on the folder and eventually finished, there was no log entry about it.
There was a "From pstack, a thread/connection was doing a flag change. And a no "fc" event was logged.
Need additional logging in the transaction or telemetry log for the reason that the client gave up and disconnected.
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