[DERBY-5760] Missing argument in some XJ022 errors

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.8.3.3, 10.9.1.0
• Component/s: JDBC
• Issue & fix info: Patch Available
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 11/May/12 12:32
• Updated: 17/Jul/13 21:19
• Resolved: 22/May/12 08:38

Description

EmbedBlob and EmbedClob some times wrap IOExceptions in an SQLException with SQLState XJ022 (SQLState.SET_STREAM_FAILURE), but they don't always specify the message argument, so the error message ends up like this:

java.sql.SQLException: Unable to set stream: '

{0}

'.

(The detailed error message does appear in a chained exception, so it's not a very big problem, but it looks a bit odd.)

I don't know of a way to expose these exceptions in a test. I just noticed it when I added some manual asserts to force a failure when investigating another issue.

The fix should be simple: Use the helper method Util.setStreamFailure() that sets the message argument automatically.

Issue Links

• is related to: DERBY-6289 Derby 10.8 backport issue (summer 2013)
• relates to: DERBY-6289 Derby 10.8 backport issue (summer 2013)