Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Mon, 10 Jul 2006 16:25:07 +0200
From: Andreas Korneliussen <Andreas.Korneliussen@Sun.COM>
Subject: Re: [jira] Commented: (DERBY-550) BLOB : java.lang.OutOfMemoryError
 with network JDBC driver (org.apache.derby.jdbc.ClientDriver)
In-reply-to: <44B25BF0.8010901@basil.ocn.ne.jp>
To: derby-dev@db.apache.org
Reply-to: Andreas.Korneliussen@Sun.COM
Message-id: <44B26343.90807@sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.2 (X11/20060427)
References: <22130645.1152283292630.JavaMail.jira@brutus>
 <44B2523D.3010802@basil.ocn.ne.jp> <44B253D6.60900@sun.com>
 <44B25BF0.8010901@basil.ocn.ne.jp>

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