[DERBY-6706] Derby does not check invalid configuration option name in derby.properties

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.10.2.0
• Component/s: Miscellaneous
• Labels: configuration invalid
• Environment: all
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Sai Zhang
• Created: 14/Aug/14 22:05
• Updated: 15/Oct/15 15:57

Description

Dear Derby Developers,

This is a simple-to-fix but annoying problem in Derby.

Derby simply does not check an invalid configuration option name specified in derby.properties.

For example,

if I want to set:

derby.database.forceDatabaseLock=False

However, I mis-spell the configuration name, like:

ddddddddddddderby.database.forceDatabaseLock=False

Seems that derby simply ignores this mis-spelled configuration option rather than issuing a warning to inform me the potential problems in using Derby. This happens to me a few times, and is really annoying.

I would suggest to check the validity of every configuration option name in the configuration file. Please let me know your thoughts.

-Sai

Issue Links

• relates to: DERBY-5970 Check that connection attributes have legal values.
• relates to: DERBY-2844 PropertyUtil should not silently ignore syntax errors in a property file