db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendle...@amberpoint.com>
Subject Re: [jira] Commented: (DERBY-550) BLOB : java.lang.OutOfMemoryError with network JDBC driver (org.apache.derby.jdbc.ClientDriver)
Date Thu, 13 Jul 2006 23:26:56 GMT
David Van Couvering wrote:
> ... We should not 
> allow any other requests to be sent to the server over this connection 
> until the BLOB data is processed or cancelled 

I'm not quite sure how we would do this. What is preventing the client from,
say, calling ResultSet.next(), or going off to some other Statement object
and running some other query, etc.?

The DRDA protocol has a whole lot of logic regarding exactly how
the requestor and the server communicate about the state of the conversation,
what statements are in play and how to request or respond with actions on them,
what results have already been communicated, how to pick up and resume a
partially-fetched set of query results, etc.

DRDA may well have all the protocol mechanisms in place for suspending an
externalized data object partway through, picking it up later, etc., and we
may already have all that support in place in our network client libraries.

But I think there's some DRDA research waiting to be done here, that was the
main point I was trying to raise.



View raw message