Document the effect of shutdown on in progress transactions and open connections.

• Key: DERBY-4165
• Type: Improvement
• Status: Closed
• Resolution: Fixed
• Priority: Minor
• Assignee: Kathey Marsden
• Reporter: Kathey Marsden
• Component/s: Documentation
• Affects Version/s: 10.6.0.0
• Fix Version/s: 10.5.2.0, 10.6.0.0

Description

I have noticed if the database is shutdown various operations on open connections can cause NullPointerExceptions, assertion failures and other issues. The documentation should recommend that existing open connections be closed before shutting down the database or the engine and that unexpected behavior may occur if connections are reused after shutdown.

Comments

[Kathey Marsden]

Attached is a patch for this issue. Please review.

[Kim Haase]

Thanks again, Kathey. This looks great.

You might want to break the new paragraph into lines of up to 80 characters.

Also, the phrase "erroneous errors" seems redundant -- would just "errors" convey the meaning intended?

[Kathey Marsden]

Marking urgent for 10.5.2. I plan to fix this.

[Kathey Marsden]

Thanks Kim for reviewing the patch. By "erroneous errors" I wanted to convey that we can't begin to predict what you are going to get, but it is certain to be bad. I think maybe just "errors" seems to soft. Can you think of a better word than erroneous?

[Kathey Marsden]

I spoke with Laura Stewart who agreed with Kim that "erroneous" was redundant and suggested an attention <note> tag for emphasis instead. Here is a new patch and html file with the recommended changes from Kim and Laura.

[Kim Haase]

Laura's suggestion of using an Attention note works perfectly. Thanks for breaking up the lines, too. From a writing standpoint, +1 to commit, I'd say.

[Kathey Marsden]

Committed revision 793658 to 10.5. I don't plan to backport further.