When the directory service is busy with large operations, the JVM wrapper kills the jvm and restarts after several unanswered pings. Often times, I find that when the wrapper starts, it takes 2 or 3 tries to get it up and running because it is impatient.
What settings can I tweak to make the wrapper more patient? Large operations are quite common and I'm okay with the system hanging a bit while it processes all the data (e.g., batch operations in studio), because it needs to get done.
