Orchestrator Fails with too many Database Connections
I have created an orchestration attempting to release credit holds on orders if the order had previously been released from a hold. I am getting errors around database connections.
Generally, here's what happens:
- Data Request to get a list of orders on hold (normally would be 100 or less, could be up to 1000 records)
- For each record
- Data request to fetch the first date it was ever released from a hold
- If record found
- Form request to release the hold
What I'm seeing is that this will fail trying to execute data requests, based on running out of database connections. It seems directly tied to the JDBj Maximum Connections setting on the AIS server (basically if this is set to 50 it fails after 50 records are processed; increase it to 150 and we can process 150 records).