MID Server fails to start if "mid.log.command_audit.enable" MID property is set - Known Error

MID Server fails to start if "mid.log.command_audit.enable" MID property is set Description On San Diego release, once "mid.log.command_audit.enable" property is configured and set to true. It creates a race condition with Bootstrapping logic causing incomplete MID Server initialization causing it to fail to start.

Steps to Reproduce

1. On San Diego, configure MID Server property "mid.log.command_audit.enable" and set to true

2. Restart MD Server

3. Check MID Server logs for the following log entries: 11/08/22 00:24:15 (494) StartupSequencer SEVERE *** ERROR *** Failed to load remote properties: null

4. You might have to restart MID Server several times to get this to kick in.

Workaround Workaround (if Customer wish to continue using 'mid.log.command_audit.enable' property):

Remove "mid.log.command_audit.enable" property if configured Start MID so that it can come up Add MID Config param 'mid.rest.record_insert.retry_backoff' with default value of 1.5 Add back "mid.log.command_audit.enable" property Related Problem: PRB1620218