db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-550) BLOB : java.lang.OutOfMemoryError with network JDBC driver (org.apache.derby.jdbc.ClientDriver)
Date Fri, 07 Jul 2006 14:29:52 GMT
Tomohito Nakayama (JIRA) wrote:

>    [ http://issues.apache.org/jira/browse/DERBY-550?page=comments#action_12419714 ] 
>
>Tomohito Nakayama commented on DERBY-550:
>-----------------------------------------
>
>I intended to resolve this issue as "Cannot Reproduce" as next url.
>http://issues.apache.org/jira/browse/DERBY-1472#action_12419712
>
>However, I reconsidered.
>
>I won't resolve DERBY-550, "BLOB : java.lang.OutOfMemoryError with network JDBC driver
(org.apache.derby.jdbc.ClientDriver)",
>because it seems to be true that OutOfMemoryError happens "in server side".
>
>Title of DERBY-550 does not say that Error happens in client side.
>Then, this issue is not mistaken completely.
>
>Description of the issue "writting all the file into memory (RAM) before sending ",  is
mistaken.
>
>  
>
Sorry for  my own propagation of confusion over  this issue.  When 
filing  DERBY-326  and seeing similar code in the client I suspected 
there might be streaming  issues  in the client as well.  I  then took 
DERBY-550 as confirmation of that  when I saw it filed against the 
client and described in this way.

In addition to changing the component to Network Server, changing the  
DERBY-550 description as follows might clarify things sufficiently.
from

"Using the org.apache.derby.jdbc.ClientDriver driver to access the
Derby database through network, the driver is writting all the file into 
memory (RAM) before sending
it to the database. "

to more of a a description of the functional problem:

"Using the org.apache.derby.jdbc.ClientDriver driver to access the
Derby database through network, sending a large amount of parameter data 
with setBinaryStream will cause Network Server  to throw an 
OutOfMemoryException.

I am not sure if setCharacterStream is also at issue. If so it could be 
filed as a separate issue.

Kathey


Mime
View raw message