CLI0601E
in [DB2]
|
Prev: [IBM][JDBC Driver] CLI0601E
Next: RESOLVED
From: Bernd Hohmann on 17 Jan 2007 14:57 Roger wrote: > I am not using connection pooling. Runs on a type 4 driver. It runs for > 1 hr and then gets the error 1hr without any traffic from or to the database? Bernd -- What do you get when you cross a mail pigeon with a parrot ? Voice mail
From: Knut Stolze on 17 Jan 2007 15:07 Roger wrote: > I am not using connection pooling. Runs on a type 4 driver. It runs for > 1 hr and then gets the error Activate a CLI trace and see what is going on with your statement handles. -- Knut Stolze DB2 z/OS Utilities Development IBM Germany
From: Roger on 21 Jan 2007 15:03 thanks a trace revealed bug in the app that had close statement. Knut Stolze wrote: > Roger wrote: > > > I am not using connection pooling. Runs on a type 4 driver. It runs for > > 1 hr and then gets the error > > Activate a CLI trace and see what is going on with your statement handles. > > -- > Knut Stolze > DB2 z/OS Utilities Development > IBM Germany
From: Jan Nelken on 21 Jan 2007 16:26
Roger wrote: > thanks a trace revealed bug in the app that had close statement. > > Knut Stolze wrote: >> Roger wrote: >> >>> I am not using connection pooling. Runs on a type 4 driver. It runs for >>> 1 hr and then gets the error Technically speaking you were using legacy App driver - since your CLI trace was captured. DB2 JCC Universal Driver in T2 (Type 2) connectivity does not use CLI layer - but uses DB2 Client code. DB2 JCC Universal Driver in T4 (Type 4) connectivity does not use CLI layer and does not need DB2 client code installed. Jan M. Nelken |