-
Type:
Improvement
-
Status: Done
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.0, 3.5.0, 3.0.1, 3.0.0, 2.6.4, 2.6.3, 2.6.2, 2.6.1, 2.6.0
-
Component/s: documentation
-
Labels:None
-
Support Ticket IDs:
Section 3 "Managing server processes" should explain that shutting down cleanly is important.
We give a create-rc-script to create an init script that can be used to achieve a proper shutdown. Likewise, the Windows Service will also shutdown the DJ instance.
- 2.6.x https://backstage.forgerock.com/#!/docs/opendj/2.6/admin-guide#chap-server-process
- 3.0.0 https://backstage.forgerock.com/#!/docs/opendj/3/admin-guide#chap-server-process
What we don't have is a guide stating why it's detrimental to kill an OpenDJ or OpenAM w/ Embedded DJ or to reboot a server that has either of these running on it.
DJ in any form needs to be properly shutdown "before" any reboots take place. Not doing so can create any number of issues as seen here. DJ needs to properly shutdown to release any internal locks and write database specific information to the je.config.csv, je.info.0 and je.stat.csv files.