db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5760) Missing argument in some XJ022 errors
Date Fri, 11 May 2012 12:33:51 GMT
Knut Anders Hatlen created DERBY-5760:

             Summary: 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:
            Reporter: Knut Anders Hatlen
            Assignee: Knut Anders Hatlen
            Priority: Minor

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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message