I think in every SCJD-assignment and every design exists the problem to perform a half-write during server-shutdown. But in the newer assignments there are no requirements to implement a complete server shutdown with database-locking. In the
thread "Shutdown Server Properly" some ranchers discussed a complex server shutdown-scenario, and Mark Spritzler wrote:
You guys are going way overboard. I have been here at JavaRanch in this forum for over three years now, most of them as the bartender, and this has got to be the most stubborn group of programmers I have seen so far. Get over it, and realize that if Sun wanted you to go this far, they would be charging a lot more than $250. They want a simple straight-forward solution that still tests skills. Going overboard like this is not going to gain extra points, but can cause you to lose points. I have seen this over and over again. After you get your score, you will come back and say, I guess I went to far.
Since I have read this I don't want to implement too much to close my server. Or is it really necessary to check that there are no activ clients on my server before I start the shutdown?