Error: address pool is full

When the address pool is full error occurs, it is usually due to insufficient concurrency. How can I confirm whether this is the cause?

Under Manage>Intelligent Operations>Platform Log, you can see the current number of online users in the system, and then compare the concurrency in the registration information page to determine whether the number of concurrent purchases has been exceeded.

The solution is to reduce the number of concurrent users or increase the maximum number of concurrent users.

1. Check the server status

Open the decision-making platform http://localhost:8075/webroot/decision, click Manage>Intelligent Operations>Platform Log, the "Access Statistics" is shown in the figure below:

The system status displays the name of the report being accessed, accessing user IP and accessing username, access time, and the current number of online users of the system.

Now you can access a built-in template in decision-making platform,such as: Directory/Report/Typical Report/Detail Report

Then refresh the platform, select Manage>Intelligent Operations>Platform Log>Access Statistics, you can see that the number of online users in the current system is 1, and you can also see the Detail Report you just accessed, as shown in the following figure:

2. Check registration information

Click Manage>Registration in the decision-making platform to view the version information, as shown in the figure below:

Concurrency is 2, and concurrency is the maximum number of concurrent purchases. If the maximum number of concurrent users is less than the number of online users in the current system, the address pool is full error will occur.