Error happened with slapd (Provisioning Server) process has stopped in Vaap.

Products

• CA Identity Suite

Issue/Introduction

Provisioning Server process has stopped by itself in Vaap

Environment

Vaap 14.4.2

Cause

Configured a Policy Xpress to fetch data directly from the Provisioning Server via port 20389 as a ldap server.

 

Resolution

Stop using Provisioning Server bind as ldap server in Policy Xpress to fetch data.

Instead, if using the PX Policy built-in functions for accounts (like get account value) then  IM would use the existing JIAM session pools for communicating with the Provisioning Server. But if using LDAP direct then IM would need to establish a new JNDI connection to the specified host/port.

If needing to establish a new JNDI connection that means more time/resources and also means you can overwhelm the Provisioning Server with load as by default the Provisioning Server's slapd is configured to accept 200 connections.