Author: mikedd
Date: Thu Jan 13 21:52:39 2011
New Revision: 1058756
URL: http://svn.apache.org/viewvc?rev=1058756&view=rev
Log:
OPENJPA-1699: Add documentation for fully materialized LOB issue with streaming
LOBs and DB2
Modified:
openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
Modified: openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
URL:
http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml?rev=1058756&r1=1058755&r2=1058756&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
(original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml Thu
Jan 13 21:52:39 2011
@@ -712,6 +712,23 @@ of DESCSTAT, DB2 metadata tables must be
See DB2 for z/OS documentation for additional information.
</para>
</listitem>
+ <listitem>
+ <para>
+When using LOBs with persistent attributes of a streaming data type (e.g.
+<literal>java.io.InputStream</literal>) 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.
+ </para>
+ <para>
+To work around this condition you may force fullyMaterializedLobData to true
in
+the connection URL as shown below :
+<programlisting>
+openjpa.ConnectionURL:
jdbc:db2://localhost:50000/demodb:fullyMaterializeLobData=true;progressiveStreaming=NO
+</programlisting>
+ </para>
+ </listitem>
</itemizedlist>
</section>
</section>
