Page Comparison

...

If your purge schedules are all the same, then change them. Use something along these lines to run at 10 minute intervals:
0 0 0 ? * SUN
0 10 0 ? * SUN
0 20 0 ? * SUN
0 30 0 ? * SUN

Alternate Solution

Update semarchy.xml to allow more active connections. You may find that staggering the purge schedule fully solves your problem. If so, then there is no need to update semarchy.xml. But if you find that you are still exhausting your supply of available connections, then you should increase the maxActive connections.

The default connection sample for a data location looks like this:

        <Resource name="jdbc/SEMARCHY_CUSTOMER_B2C_MDM" auth="Container"
                factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" type="javax.sql.DataSource"
                driverClassName="org.postgresql.Driver" url="jdbc:postgresql://localhost:5432/postgres"
                username="semarchy_customer_b2c_mdm" password="semarchy_customer_b2c_mdm"
                maxActive="8" maxIdle="8" minIdle="0" maxWait="15000" initialSize="1"
                defaultAutoCommit="false" rollbackOnReturn="true" validationQuery="select 1"
                testOnBorrow="true" timeBetweenEvictionRunsMillis="45000"
                validationInterval="60000" />

If you have arrived at this article, you have probably encountered "pool empty" problems. In that case, increase maxActive from "8" to "32" as a good starting point.

The choices here are not one-size-fits-all. You'll need analysis of your expected usage along with experimentation to determine the best parameters for your needs.

Related articles

...