title: Are Clustered WebLogic JDBC DataSource settings per node or per cluster?
body: <p>I have a WebLogic 9.2 Cluster which runs 2 managed server nodes. I have created a JDBC Connection Pool which I have targeted at <em>All servers in the cluster</em>. I believe this will result in the physical creation of connection pools on each of the 2 managed servers (although please correct me if I'm wrong)?</p>
  
  <p>Working on this assumption I have also assumed that the configuration attributes of the Connection Pool e.g. Min/ Max Size etc are <em>per managed server</em> rather than <em>per cluster</em>. However I am unsure of this and can't find anything which confirms or denies it in the WebLogic documentation.</p>
  
  <p>Just to be clear here's an example:</p>
  
  <p>I create <em>connection-pool-a</em> with the following settings and target it at <em>All servers in the cluster</em>:</p>
  
  <pre><code>Initial Capacity: 30
  Maximum Capacity: 60
  </code></pre>
  
  <p>Are these settings applied:</p>
  
  <ol>
  <li>Per managed server - i.e. <strong>each</strong> node has an initial capacity of 30 and max of 60 connections.</li>
  <li>Across the cluster - i.e. the initial number of connections across <strong>all</strong> managed servers is 30 rising to a maximum of 60.  </li>
  <li>In some other way I haven't considered?  </li>
  </ol>
  
  <p>I ask as this will obviously have a significant effect on the total number of connections being made to the Database and I'm trying to figure out how best to size the connection pools given the constraints of our Database.</p>
  
  <p>Cheers,</p>
  
  <p>Edd</p>