OpenDJ tends to show resilience when restarting after a crash or after the server process is killed abruptly. OpenDJ might have to replay the last few entries in a transaction log. Generally OpenDJ returns to service quickly.
You can find Berkeley Java Edition database recovery messages in the
database log file, such as
/path/to/opendj/db/userRoot/je.info.0. The following
shows two example messages from that log, the first written at the beginning
of the recovery process, the second written at the end of the process.
111104 10:23:48:967 CONFIG [/path/to/opendj/db/userRoot]Recovery underway, found end of log ... 111104 10:23:49:015 CONFIG [/path/to/opendj/db/userRoot]Recovery finished: Recovery Info ...
What can take some time during server startup is preloading database
content into memory when the server starts. Objects cached in memory do not
survive a crash. By default, OpenDJ does not cache objects in memory before
starting to accept client requests. You can however set a
preload-time-limit for the database cache of your
backend if you do want to load objects into the database cache before
OpenDJ begins accepting client connections.
