(Doc ID 2268814.1)
Last updated on NOVEMBER 11, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
The ECE EM-Gw has the “reject-on-overload” feature where in when all the EM gateway threads were busy, any new connection would get rejected.
However, there could be situations where in the threads are busy for a short duration and we might be rejecting CM transactions which otherwise might have succeeded if we had waited for a fraction of a second. If there are 10 threads and a 11th connection came in when all the 10 threads are busy, we will reject this connection. But, instead if we had put it in the request queue, any thread that would have become free in the next millisecond would have picked it up.
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