my dog learned polymorphism*
The moose likes Websphere and the fly likes WebSphere 4 connection pooling. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WebSphere 4 connection pooling." Watch "WebSphere 4 connection pooling." New topic
Author

WebSphere 4 connection pooling.

Dave Coombes
Greenhorn

Joined: Nov 06, 2001
Posts: 19
Hi,

I have a question regarding datasources and connection pooling in WebSphere v4.0.7. We have multiple instances of the same application each deployed on its own application server instance under the same admin server. We have created a datasources for Oracle and specified a minimum and maximum connection pool size. My questions are

1) Is the connection pool shared across all application server instances or is a pool created for each app server instance. The reason I ask is that in the Resource Analyzer, there is a set of counters for each defined datasource, scoped by the application server instance, each with different values in. I am not sure what conclusion to draw from this. Does this imply a pool per application server instance or a shared pool and the counters are just reflecting the fraction of the pool being used by the particular app servers?

2) Is there any way to purge or refresh the connections in the pool? We have had a problem with some Oracle connections becoming 'dead' as far as Oracle is concerned but WebSphere has not detected this (i.e. no database errors have been mapped to StaleConnectionException) and then the number of effective connections in the pool becomes reduced. It would be useful if there was some to signal to WAS that it should refresh its connections without restarting the app server instance in this case.

Any help on either of these would be gratefully received.

Cheers
Dave
 
 
subject: WebSphere 4 connection pooling.