2 Replies Latest reply: Jan 5, 2013 9:09 PM by Sahasra RSS

    Weblogic DB connection pool load balancing problem

    Sahasra
      hi all,

      here is a strange issue. We have a clustered weblogic environment with2 servers. And the application is deployed to cluster. But strangely when we check the active connections for the connection pool that is being used by the application, we see that 2nd server has more connections when compared to 1st server, lets say 1st server has 4 active connections, 2nd server has 50 connections, What might be the problem.

      <?xml version='1.0' encoding='UTF-8'?>
      <jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/jdbc-data-source" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/jdbc-data-source http://www.bea.com/ns/weblogic/jdbc-data-source/1.0/jdbc-data-source.xsd">
      <name>##########</name>
      <jdbc-driver-params>
      <url>jdbc:oracle:thin:@hostname:portnumber:Schema</url>
      <driver-name>oracle.jdbc.OracleDriver</driver-name>
      <properties>
      <property>
      <name>user</name>
      <value>#####</value>
      </property>
      <property>
      <name>portNumber</name>
      <value>#####</value>
      </property>
      <property>
      <name>SID</name>
      <value>######</value>
      </property>
      <property>
      <name>serverName</name>
      <value>hostname</value>
      </property>
      </properties>
      <password-encrypted>##########</password-encrypted>
      <use-xa-data-source-interface>false</use-xa-data-source-interface>
      </jdbc-driver-params>
      <jdbc-connection-pool-params>
      <initial-capacity>0</initial-capacity>
      <max-capacity>75</max-capacity>
      <capacity-increment>5</capacity-increment>
      <shrink-frequency-seconds>900</shrink-frequency-seconds>
      <highest-num-waiters>2147483647</highest-num-waiters>
      <connection-creation-retry-frequency-seconds>0</connection-creation-retry-frequency-seconds>
      <connection-reserve-timeout-seconds>10</connection-reserve-timeout-seconds>
      <test-frequency-seconds>60</test-frequency-seconds>
      <test-connections-on-reserve>true</test-connections-on-reserve>
      <profile-harvest-frequency-seconds>300</profile-harvest-frequency-seconds>
      <ignore-in-use-connections-enabled>true</ignore-in-use-connections-enabled>
      <inactive-connection-timeout-seconds>0</inactive-connection-timeout-seconds>
      <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
      <login-delay-seconds>0</login-delay-seconds>
      <statement-cache-size>10</statement-cache-size>
      <statement-cache-type>LRU</statement-cache-type>
      <remove-infected-connections>true</remove-infected-connections>
      <seconds-to-trust-an-idle-pool-connection>10</seconds-to-trust-an-idle-pool-connection>
      <statement-timeout>-1</statement-timeout>
      <profile-type>0</profile-type>
      <pinned-to-thread>false</pinned-to-thread>
      </jdbc-connection-pool-params>
      <jdbc-data-source-params>
      <jndi-name>##########</jndi-name>
      </jdbc-data-source-params>
      </jdbc-data-source>