db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1191) Some SQLExceptions, for example those generated from BrokeredStatements, do not print to derby.log even when derby.stream.error.logSeverityLevel=0
Date Fri, 07 Apr 2006 14:53:23 GMT
Some SQLExceptions, for example those generated from BrokeredStatements,  do not print to derby.log
even  when  derby.stream.error.logSeverityLevel=0
-----------------------------------------------------------------------------------------------------------------------------------------------------

         Key: DERBY-1191
         URL: http://issues.apache.org/jira/browse/DERBY-1191
     Project: Derby
        Type: Bug

  Components: JDBC  
    Versions: 10.1.2.3, 10.2.0.0, 10.1.3.0    
    Reporter: Kathey Marsden


I found this when working on DERBY-1047.   Exceptions thrown  using 
org.apache.derby.impl.jdbc.Util.generateCsSQLException()
do not print to derby.log even when derby.stream.error.logSeverityLevel=0

For example the attached repro  generates an expected exception but does not  print the error
to the log.

java -Dderby.stream.error.logSeverityLevel=0 Derby1047


This causes an expected exception to be thrown but it does not print to the derby.log

10.2.0.0 alpha
Apache Derby
Apache Derby Embedded JDBC Driver
done creating  table
COL1
-----------
1
2
PASS: Expected Exception can'tholdable cusror in global xact:Cannot set holdability ResultSet.HOLD_CURSORS_OVER_COMMIT
for a global transaction.
COL1
-----------
1
2
3


The code generating the exception is in org.apache.derby.iapi.jdbc.BrokeredStatement

  final void checkHoldability() throws SQLException {
        int holdability = controlCheck().checkHoldCursors(resultSetHoldability);
        if (holdability != resultSetHoldability)
            throw Util.generateCsSQLException(SQLState.CANNOT_HOLD_CURSOR_XA);

    }


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message