[jira] [Updated] (DERBY-5760) Missing argument in some XJ022 errors

["Mamta A. Satoor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-5760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-5760:
-----------------------------------

    Fix Version/s: 10.8.3.1
    
> Missing argument in some XJ022 errors
> -------------------------------------
>
>                 Key: DERBY-5760
>                 URL: https://issues.apache.org/jira/browse/DERBY-5760
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.9.1.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Mamta A. Satoor
>            Priority: Minor
>             Fix For: 10.8.3.1, 10.9.1.0
>
>         Attachments: d5760-1a.diff
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira