Tomcat connection pooling to DB2 problem

[evgeniosc]

I am using tomcat on Linux RedHat 7.2.

I use connection pooling to connect to IBM DB2 database on an AIX system.

Intermittently occurs the following problem:
the DataSource.getConnection method waits for a long time (e.g 10-15 seconds).

The database seems to have no problem at all.

 

[sedj]

This is probably not what you want to hear, but its been my experience that the tomcat pooling suffers from intermittent performance/stability problems.

We couldn't put up with it, and wrote our own custom connection pool.

 

[siberian]

sedj, you should release your pooling for the public

I havent had problems with standard JNDI db resources but I am not putting a ton of load on them either.

Proxcool never worked for me (well, I probably did not set it up correctly) and even at that it has the same limitations as JNDI pooling..



Who would have thunk that pooling in tomcat would be such a pain.

 

[sedj]

siberian, I'd love to release my pool to the public, but I wrote some of it at work (though most of it at home) so my contract says its property of work ... but it'd be great to put it public and get some other developers working on it also !

I'm working on a distributed connection pool extension at the moment so that the client does not need to have any db drivers on the client at all.