SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-27-2008, 01:50 AM
| ||||
| ||||
 DB2 Connection Pooling I know that DB2 LUW version 8 has "connection pooling" that provides a connection concentrator (limits the number of simultaneous connections that can occur). But does it really provide connection reuse in the same manner provided by DB2 Connect or Websphere (or some 3rd party connection interfaces)? If DB2 V8 does have connection reuse, does the built-in DB2 connection pooling require extra jdbc coding, and is it as robust as DB2 Connect? I assume the DB2 V8 connection reuse would only run on the DB2 server, and not on the application server (this is an issue if there are multiple application servers). I have a customer that is using a type 4 driver with a 3rd party tool that provides connection pooling at the application server tier (there are at least 4 different app servers), but it is not working well (it maybe a jdbc type 4 driver problem, maybe a DB2 problem, or maybe a problem with the 3rd party connection tool). It seems to me that maybe DB2 Connect might provide a more compatible interface (at least they can blame IBM if it does not work). Any thoughts?      |
|
02-27-2008, 01:51 AM
| ||||
| ||||
| Re: DB2 Connection Pooling "Mark" <m0002a@yahoo.com> wrote in message news:a5ebcc65.0410021929.2de3d65c@posting.google.c om... > I know that DB2 LUW version 8 has "connection pooling" that provides a > connection concentrator (limits the number of simultaneous connections > that can occur). But does it really provide connection reuse in the > same manner provided by DB2 Connect or Websphere (or some 3rd party > connection interfaces)? =================== Not exactly the same, but a lot of similiar properties. > > If DB2 V8 does have connection reuse, does the built-in DB2 connection > pooling require extra jdbc coding, and is it as robust as DB2 Connect? ===================== It doesn't need any extra jdbc coding. It is part of db2 engine and it is transparent to the db2 client. It has no requirement that you can only run JDBC applications. If you use CLI, ESQL/C, Shell scripts, ..., they are all OK with connection concentrator. > I assume the DB2 V8 connection reuse would only run on the DB2 server, > and not on the application server (this is an issue if there are > multiple application servers). ===================== Yes, It would run on the db2 server, and it is not a separate server. This means you can still use connection pool which built by the application server. I really don't think why we need to this, I mean double pooling, but it is a do-able solution. They can work with each other without any problems. > > I have a customer that is using a type 4 driver with a 3rd party tool > that provides connection pooling at the application server tier (there > are at least 4 different app servers), but it is not working well (it > maybe a jdbc type 4 driver problem, maybe a DB2 problem, or maybe a > problem with the 3rd party connection tool). ====================== It is not hard to isolate which part cause the problem. Turn on DB2 UDB connection concentrator, run the same type4 java application but bypass the connection pool which defined by the 3rd party. > It seems to me that maybe > DB2 Connect might provide a more compatible interface (at least they > can blame IBM if it does not work). > > Any thoughts? > |
Linear Mode
