• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

WebSphere 4 connection pooling.

Posts: 19
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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.

    Bookmark Topic Watch Topic
  • New Topic