title: How to properly monitor the actual number of database connections from WebSphere 6.1?
body: <p>I need to monitor the actual number of connections from Websphere to the database. I've tried to do this in three different ways, but each way gives me a different outcome.
  I'm working on Webpshere 6.1 with several nodes, each containing three servers. All servers are in the same cluster.</p>
  
  <ol>
  <li><p><strong>Tivoli Performance Viewer.</strong> In TPV, I can choose a particular server, then Performance Modules, JDBC Connection Pools, Oracle RAC JDBC Provider. From there I can see the total number of connections created, closed and the size of the connection pool. Fine, but this gives me an average value of 1 or 2 for PoolSize.</p></li>
  <li><p><strong>Accessing MBeans using Jolokia.</strong>
  I've deployed Jolokia application on the cluster so it should be distributed to every server. The application works, however when I do the "list" command, which should list all possible MBeans on Websphere, it gives me hundreds of them, but all of them are related to the first instance on the node. For example, when accessing Jolokia using 192.168.1.1/jolokia/list, it gives a list of MBeans, all related to the first instance (server1) configured on 192.168.1.1. Shouldn't it show MBeans related to all three servers on that node? Nevertheles, the value from there is also 1 or 2 as in TPV.</p></li>
  <li><p><strong>Using netstat in Linux shell.</strong>
  Another problem here. When listing the established connections to the particular database using netstat, it shows about 30 connections from each server process, which gives around 90 connections to the database from the node. I don't understand where that connections came from.</p></li>
  </ol>
  
  <p>Which information is most relevant here? Am I missing something?</p>