The default liveness probe in the templates don't have any initial delay.

there is an unnecessary race between the probe and the startup, which sometimes causes JDV to restart due to liveness probe failure at startup

(e.g. " No such file or directory: '/opt/jolokia/etc/jolokia.properties" due to the joloikia init scripts not being run yet)