PDBI connection to EPAP server failure. Error: We have hit our limit of active PDBI connections.

Asset ID:	1-72-2351237.1
Update Date:	2018-02-07
Keywords:

Solution Type Problem Resolution Sure

Solution 2351237.1 : PDBI connection to EPAP server failure. Error: We have hit our limit of active PDBI connections.

Applies to:

Oracle Communications EAGLE (Software) - Version EPAP 15.0 and later
Information in this document applies to any platform.

Symptoms

The PDBI clients unable to establish connection to EPAP server for provisioning updates.

EPAP reporting PDBI connection failure with the following error in logs:-

Error: We have hit our limit of active PDBI connections.

In some cases, error code "1020" is observed in PDBA message logs.

Cause

The PDBI client connections has reached its maximum connections.

There is a limit to the number of PDBI connections, the default is 16 clients. If an attempt is made to connect more than the current connection limit, the connection request is automatically decline with a return error code and socket is closed.

Although the default limit is 16 PDBI connections, the system is configurable to support up to the max 128 connections.

Solution

The workaround to clear the error immediately by restarting the PDBA process. All current PDBI connections will be force exited, and new connections could be established.

For permanent resolution, the following procedure to increase PDBI client connections to max 128.

1. Logon to EPAP server at Active Provisioning site.

2. Stop PDBA process.

# service Pdba stop

3. Edit PDBA config to increase PDBI connections to 128.

# uiEdit PDBA_MAX_ACTIVE_CONNS 128

4. Start PDBA process.

# service Pdba start

5. Verify with Provisioning team if PDBI client connections successfully.

* It is highly recommended that the same steps to be applied on Standby Provisioning site. As such PDBI connection capacity will be available in case of Active Provisioning switchover.

Attachments

This solution has no attachment