Enpd Cannot Handle Lots Of SSL Connections
(Doc ID 2872044.1)
Last updated on MAY 25, 2022
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
Why can imapd handle lots of SSL connections, but enpd cannot?
It seems that using ENS over SSL is unusable.
A new UAT system, which is much more representative of our production hardware, just logged a complaint from msprobe about ens-ssl connections taking 13 seconds:
While this UAT system is much more representative of our production hardware, it is still no where near our production load.
If enpd cannot handle ENS over SSL on this UAT system, it will not work in production.
How is it that imapd can handle lots of SSL connections, but enpd cannot?
For our current usage, ENS traffic is restricted to the local system. Even that is difficult with SSL, because connecting to 127.0.0.1 fails certificate validation.
Since it is all within the local system, SSL is not really needed.
But if something off-system needed ENS, this would be a real problem.
Also, Cassandra *requires* ENS between the systems.
But, this *may* be less of a problem with Cassandra because so many imapd processes should not be needed with Cassandra.
But, it is confusing as to why enpd suffers so much from this, while imapd is perfectly capable of handling MANY more SSL connections.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!