D3 Numbers RPC Connexion ?

As noted in the case, the RPC connections in MAXUSERS is part of the 3 for 1 licensing scheme and that RPC connections consume standard licenses. Was this forum post made before or after we settled all of that within the case? As far as what’s preventing the fourth connection, I have no clue, but it’s not licensing unless you’re out of normal user licenses as well.

Thank you for the clarification.

The forum post and the support case were taking place at approximately the same time, so it is possible that the licensing details had not yet been fully clarified when the forum post was written.

From your explanation, it appears that the issue is not related to licensing, as user licenses are still available when the problem occurs.

One additional observation: our environment regularly receives updates from about 13 different servers through RPC. However, these updates are very short-lived, typically involving a single record update, so the RPC connection is opened and released almost immediately.

The issue only appears with long-running update processes. In the scenario described, two different users launch update jobs that keep multiple RPC connections active for approximately 2 to 3 minutes. It is during these situations that an additional RPC connection appears to be blocked.

As a temporary workaround, I asked the two users not to run these long-running update processes at the same time. Since implementing this recommendation, I have not received any further reports indicating that the problem is still occurring.

Since licensing does not appear to be the cause, we will continue to monitor the situation and investigate any other factors that could explain this behavior.

Thank you for your help and clarification.