OPENJPA-1699: Add documentation for fully materialized LOB issue with streaming LOBs and DB2

git-svn-id: https://svn.apache.org/repos/asf/openjpa/branches/2.0.x@1058758 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael Dick 2011-01-13 22:00:14 +00:00
parent 26d55bebb5
commit a56b9b26eb
1 changed files with 17 additions and 0 deletions

View File

@ -622,6 +622,23 @@ of DESCSTAT, DB2 metadata tables must be recreated by running the DSNTIJMS job.
See DB2 for z/OS documentation for additional information. See DB2 for z/OS documentation for additional information.
</para> </para>
</listitem> </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 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> </itemizedlist>
</section> </section>
</section> </section>