From d916e6feb8c7dfc325e7ac1c8a8b9a00b5c7176c Mon Sep 17 00:00:00 2001 From: Michael Dick Date: Thu, 13 Jan 2011 21:52:39 +0000 Subject: [PATCH] OPENJPA-1699: Add documentation for fully materialized LOB issue with streaming LOBs and DB2 git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@1058756 13f79535-47bb-0310-9956-ffa450edef68 --- .../src/doc/manual/supported_databases.xml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/openjpa-project/src/doc/manual/supported_databases.xml b/openjpa-project/src/doc/manual/supported_databases.xml index 8a4120c56..35de3ea57 100644 --- a/openjpa-project/src/doc/manual/supported_databases.xml +++ b/openjpa-project/src/doc/manual/supported_databases.xml @@ -712,6 +712,23 @@ of DESCSTAT, DB2 metadata tables must be recreated by running the DSNTIJMS job. See DB2 for z/OS documentation for additional information. + + +When using LOBs with persistent attributes of a streaming data type (e.g. +java.io.InputStream) in the case of very large lob, DB2 JCC +driver will automatically use progressive streaming to retrieve the Lob data. +With progressiveStreaming, the inputStream retrieved (see red below) must be +fully materialized before the next iteration of call to rs.next(). By default +this will result in a LobClosedException when OpenJPA processes the InputStream. + + +To work around this condition you may force fullyMaterializedLobData to true in +the connection URL as shown below : + +openjpa.ConnectionURL: jdbc:db2://localhost:50000/demodb:fullyMaterializeLobData=true;progressiveStreaming=NO + + +