It is possible to create configuration using the
Administrative Console, wsadmin scripts, or using an editor. The latter of
these is highly discouraged since it is very prone to error. The cause of
this problem is that the xmi:id for two different connection pools was set
to be the same. When the Administrative Console was used to update the
connection pool configuration, the xmi:id was used as the key to locate
the connection pool to update, the wrong connection pool configuration
data was found.
The incorrect configuration that caused this problem is similar to
this. Note the xmi:id is the same for each connectionPool.
<resources.jdbc:JDBCProvider xmi:id="SabaOracleProvider" name="IBM
Oracle Provider" description="Oracle JDBC Driver"
implementationClassName="com.ibm.oracle.SabaOracleConnectionPoolDataSource"
xa="false">
<factories xmi:type="resources.jdbc:DataSource"
xmi:id="SabaOracleDataSource-SabaSite" name="Saba Oracle
DataSource-SabaSite" jndiName="SabaSite" description="JDBC Datasource"
authMechanismPreference="BASIC_PASSWORD" authDataAlias="RSQ02LMSA/tp2"
statementCacheSize="15"
datasourceHelperClassname="com.ibm.websphere.rsadapter.OracleDataStoreHelper"
relationalResourceAdapter="builtin_rra">
<connectionPool xmi:id="SabaOracleDataSourceConnectionPool"
connectionTimeout="1800" maxConnections="200" minConnections="10"
reapTime="180" unusedTimeout="1800" agedTimeout="0"
purgePolicy="EntirePool"/>
<factories xmi:type="resources.jdbc:DataSource"
xmi:id="SabaOracleDataSource-DemoSite" name="Saba Oracle
DataSource-DemoSite" jndiName="DemoSite" description="JDBC Datasource"
authMechanismPreference="BASIC_PASSWORD" authDataAlias="RSQ02LMSA/tp2"
statementCacheSize="15"
datasourceHelperClassname="com.ibm.websphere.rsadapter.OracleDataStoreHelper"
relationalResourceAdapter="builtin_rra">
<connectionPool xmi:id="SabaOracleDataSourceConnectionPool"
connectionTimeout connectionTimeout="180" maxConnections="200"
minConnections="10" reapTime="180" unusedTimeout="180" agedTimeout="0"
purgePolicy="EntirePool"/>
|