Blocked By Max Concurrent 32 Error For Many Users On MMP System
(Doc ID 2454439.1)
Last updated on MARCH 26, 2019
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
An error saying "blocked by max concurrent 32" occur for a lot of users over a 24 hour period on the MMP. This error is triggered after a DNS outage.
In the absence of dbhang/pstack output, it is not known whether:
- AService had threads stuck trying to connect, therefore the counter was accurate and threads were hung
- The counter got out of sync somehow
Also, similar DNS problems occurring world-wide and it is interesting that only these two systems had the MMP hung this way.
Until these two MMPs were restarted, they would generate messages like this:
at a rate of 130,000 to 150,000 per hour.
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