Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.1.3.1, 10.2.1.6
-
None
-
Low
-
Repro attached
Description
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); }Attachments
Attachments
Issue Links
- is related to
-
DERBY-4350 javaException is created but not thrown or logged in DRDAConnThread.closeStream(InputStream stream)
- Closed
- relates to
-
DERBY-3319 Logical connections do not check if a transaction is active on close
- Closed