Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.8.1.2
-
Fix Version/s: 10.8.1.2
-
Component/s: JDBC, Network Server, SQL
-
Labels:None
-
Issue & fix info:Repro attached
-
Bug behavior facts:Crash
Description
The server stumbles on the following error if you try to return a null LOB as a procedure output arg:
java.lang.NullPointerException
at org.apache.derby.impl.drda.EXTDTAInputStream.length(EXTDTAInputStream.java:280)
at org.apache.derby.impl.drda.EXTDTAInputStream.isEmptyStream(EXTDTAInputStream.java:274)
at org.apache.derby.impl.drda.DRDAConnThread.writeFdocaVal(DRDAConnThread.java:7930)
at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(DRDAConnThread.java:7183)
at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLSTT(DRDAConnThread.java:4179)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:1021)
at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:294)
This kills the connection. I will attach a repro.
Attachments
Issue Links
- blocks
-
DERBY-4066 Allow functions/procedures to take Blob/Clob arguments
-
- Closed
-
-
DERBY-4869 Implement JDBC 4.1, the api increment introduced by Java 7
-
- Closed
-