db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Korneliussen <Andreas.Kornelius...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-550) BLOB : java.lang.OutOfMemoryError with network JDBC driver (org.apache.derby.jdbc.ClientDriver)
Date Mon, 10 Jul 2006 14:25:07 GMT
TomohitoNakayama wrote:
> Hello Andreas.
> 
> I see ...
> H mm. Complex circumstances ....
> 
> The program failed in creating error message of OutOfMemoryError ...
> 
> Please upload your application program.
> I want to make it possible to see the phenomena by myself.
> 
> Best regards.
> 

Hi,
Yes I will upload the program.

Note: the VM throws a OutOfMemoryException, which is caught in:
NetStatementReply.copyEXTDTA:

     protected void copyEXTDTA(NetCursor netCursor) throws 
DisconnectException {
         try {
             parseLengthAndMatchCodePoint(CodePoint.EXTDTA);
             byte[] data = null;
             if (longValueForDecryption_ == null) {
                 data = (getData(null)).toByteArray();
             } else {
                 data = longValueForDecryption_;
                 dssLength_ = 0;
                 longValueForDecryption_ = null;
             }
             netCursor.extdtaData_.add(data);
         } catch (java.lang.OutOfMemoryError e) {     <--- outofmemory
             agent_.accumulateChainBreakingReadExceptionAndThrow(new 
DisconnectException(agent_,
                 new 
ClientMessageId(SQLState.NET_LOB_DATA_TOO_LARGE_FOR_JVM),
                 e));  <----- message does not take parameters, causing 
assert failure
         }
     }

When it calls new ClientMessageId(...), it fails with the assert, since 
the message does not take any parameters (here e is added as parameter 
to the message)

Andreas

Mime
View raw message