home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC69458 Status: Geschlossen

JCC DRIVER HANGS IN INFINITE LOOP

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
An application using the JDBC/JCC driver will hang when calling 
the streaming methods: 
 
PreparedStatement.getCharacterStream(int, Reader) 
OR 
PreparedStatement.setCharacterStream(int, Reader, -1) 
 
A javacore from the hanging application may be similar to the 
function stack below: 
 
java.lang.Thread.State: RUNNABLE 
at 
java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:544) 
at com.ibm.db2.jcc.t4.ib.a(ib.java:257) 
at com.ibm.db2.jcc.t4.lb.a(lb.java:1635) 
at com.ibm.db2.jcc.t4.lb.a(lb.java:181) 
at com.ibm.db2.jcc.t4.vb.a(vb.java:175) 
 
 
This issue is not affected by CPU load and occurs when streaming 
is used for large CLOBs.  For example if MY_DATA was a string 
longer than 16,390 characters this issue can be easily 
reproduced. 
 
private static String MY_DATA; 
 
PreparedStatement.setCharacterStream(2, new 
StringReader(MY_DATA));
Problem-Zusammenfassung:
See ERROR DESCRIPTION.
Local-Fix:
Use PreparedStatement.setCharacterStream(int, Read, length) or 
PreparedStatement.getCharacterStream(int, Read, length) which 
specifies the length of the data.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed with JDBC driver included with v9.5 Fixpack 7.  This 
is a client side fix.
Workaround
See LOCAL FIX.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
24.06.2010
24.02.2012
24.02.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP7
Problem behoben lt. FixList in der Version