crowd.polling.startdelay JVM parameter is not respected

Issue Summary

The is a JVM parameter in Crowd, -Dcrowd.polling.startdelay, that should delay the sync of any external directories upon startup by the number of miliseconds specified in the JVM parameter.

This was working until Crowd 2.12.0.  Since then, this parameter only effects the start of the first sync once the directory is enabled.

Environment

• Crowd 2.12.0 or later
• Remote directory such as LDAP or AD

Steps to Reproduce

1. Start Crowd
2. Add the remote directory
   1. Set the sync interval to 10 minutes
   2. You can see the directory will sync every 10 minutes
3. Stop Crowd
4. Add the JVM parameter, and set it to 900000ms (15 minutes)
5. Start Crowd

Expected Results

The next sync should take place at least 15 minutes after start-up.  This is the case in Crowd versions pre 2.12.0

Actual Results

The sync will continue at its normal pattern, every 10 minutes, based off the last successful sync time.

Notes

It appears, in 2.12.0 and later, that this parameter is only respected when adding a new directory.  For example:

• When adding a new directory in Crowd, Crowd should automatically sync it within a few minutes of the directory being added.
• If the JVM parameter is set, Crowd will respect that delay, and only sync once the delay has expired.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available