[DERBY-1560] When receiving EXTDTA object, the client should avoid keeping the entire LOB in memory for large LOBs

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.3.1
• Fix Version/s: 10.3.3.1
• Component/s: Network Client
• Assignee: Unassigned
• Reporter: Fernanda Pizzorno
• Created: 21/Jul/06 14:23
• Updated: 02/Jun/10 12:51
• Resolved: 02/Jun/10 12:51

Description

When a LOB is streamed from the Server to the Client, the Client reads all the data from the stream into a byte array. This can cause OutOfMemoryError if the LOB is large > than total memory in the VM.

To avoid this problem, instead of reading the streamed data into a byte array, the Client could read the data into a stream which will keep the data in memory when possible and store the data on disk when there is not enough memory. This stream could be based on the implementation suggested in DERBY-1341.

Issue Links

• is related to: DERBY-550 BLOB : java.lang.OutOfMemoryError with network JDBC driver (org.apache.derby.jdbc.ClientDriver)
• relates to: DERBY-208 Add support to retrieve lobs for Network Server by locator rather than matierializing the LOB