Multiple DataSource using single Connection Pool

Previously using Weblogic 6.1 we had a configuration where multiple Datasources used a single connection pool. Now that we are in the process of upgrading to Weblogic 9.1, we are attempting to recreate the same configuration.
The Weblogic 9.1 upgrade wizard appears to have created the relevent datasource & connection pool configuration files but when attempting to use these I am receiving the following errors:
####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901758> <BEA-001508> <Destroying Connection Pool TestDSLegacyPool.>
####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901758> <BEA-001155> <The following exception has occurred:
weblogic.common.ResourceException: Unknown Data Source TestDSLegacyPool
     at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownAndDestroyPool(ConnectionPoolManager.java:419)
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:251)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>
####<30-Jan-2007 11:18:21 o'clock GMT> <Error> <Deployer> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901773> <BEA-149205> <Failed to initialize the application 'TestDSLegacyPool' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:257)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
weblogic.common.ResourceException: weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
     at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:239)
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
     at weblogic.jdbc.common.internal.DataSourceManager.verifyPoolDeployment(DataSourceManager.java:607)
     at weblogic.jdbc.common.internal.DataSourceManager.checkDSConfig(DataSourceManager.java:594)
     at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:236)
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
++++++++++++++++++++++++++++++++++++++++++++++++++
The configuration files content is :
TestDSLegacyPool-9290-jdbc.xml
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
<name>TestDSLegacyPool</name>
<internal-properties>
<property>
<name>LegacyType</name>
<value>3</value>
</property>
<property>
<name>LegacyPoolName</name>
<value>Beach Brochure Browse Pool</value>
</property>
</internal-properties>
<jdbc-data-source-params>
<jndi-name>beachBrochureBrowseDS</jndi-name>
<global-transactions-protocol>None</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>
CP-Beach_Brochure_Browse_Pool-1043-jdbc.xml
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
<name>Beach Brochure Browse Pool</name>
<internal-properties>
<property>
<name>LegacyType</name>
<value>1</value>
</property>
</internal-properties>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@aserver:1522:adb</url>
<driver-name>oracle.jdbc.driver.OracleDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>gf_user</value>
</property>
<property>
<name>dll</name>
<value>ocijdbc9</value>
</property>
<property>
<name>protocol</name>
<value>thin</value>
</property>
</properties>
<password-encrypted>{3DES}4UT5899x/Z4=</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>1</initial-capacity>
<max-capacity>3</max-capacity>
</jdbc-connection-pool-params>
</jdbc-data-source>
Would anyone be able to point me in the right direction with this? Configuring the Datasources through the Admin Console creates a single Datasource configuration file that contains its relevent connection pool configuration, but the Weblogic Upgrade wizard creates a Datasource config file and a separate connection pool config file. What would I need to do to use the config files generated by the Weblogic Upgrade wizard?
Any help appreciated
Thanks
Andrew

Andrew Harrison wrote:
Previously using Weblogic 6.1 we had a configuration where multiple Datasources used a single
connection pool. Now that we are in the process of upgrading to Weblogic 9.1, we are attempting
to recreate the same configuration.Hi, sorry to say, that is no longer possible:
http://e-docs.bea.com/wls/docs90/jdbc_admin/jdbc_intro.html#1044158
Simplified JDBC Resource Configuration
In WebLogic Server 9.0, the number of JDBC resource types was reduced to simplify JDBC configuration and to reduce the likelihood
of configuration errors. Instead of configuring a JDBC connection pool and then configuring a data source or tx data source to
point to the connection pool and bind to the JNDI tree, you configure a data source that encompasses a connection pool.
Note: Because of the new configuration design, you can no longer have multiple data sources that point to a single connection
pool. Instead, you can create additional data sources, each with its own pool of connections, or you can bind a single data source
to the JNDI tree with multiple names. See Binding a Data Source to the JNDI Tree with Multiple Names for more information.
Joe
>
The Weblogic 9.1 upgrade wizard appears to have created the relevent datasource & connection pool
configuration files but when attempting to use these I am receiving the following errors:
####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
<1170155901758> <BEA-001508> <Destroying Connection Pool TestDSLegacyPool.>
####<30-Jan-2007 11:18:21 o'clock GMT> <Info> <JDBC> <tu0991ws9004> <AdminServer> <[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
<1170155901758> <BEA-001155> <The following exception has occurred:
weblogic.common.ResourceException: Unknown Data Source TestDSLegacyPool
     at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownAndDestroyPool(ConnectionPoolManager.java:419)
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:251)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
####<30-Jan-2007 11:18:21 o'clock GMT> <Error> <Deployer> <tu0991ws9004> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1170155901773> <BEA-149205> <Failed to initialize the application 'TestDSLegacyPool' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:257)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
weblogic.common.ResourceException: weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
     at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:239)
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
weblogic.common.ResourceException: DataSource(TestDSLegacyPool) can't be created with non-existent Pool (connection or multi) (Beach Brochure Browse Pool)
     at weblogic.jdbc.common.internal.DataSourceManager.verifyPoolDeployment(DataSourceManager.java:607)
     at weblogic.jdbc.common.internal.DataSourceManager.checkDSConfig(DataSourceManager.java:594)
     at weblogic.jdbc.common.internal.DataSourceManager.checkDataSource(DataSourceManager.java:236)
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:247)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:65)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.prepare(DeploymentAdapter.java:37)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:164)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:121)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
++++++++++++++++++++++++++++++++++++++++++++++++++
The configuration files content is :
TestDSLegacyPool-9290-jdbc.xml
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
<name>TestDSLegacyPool</name>
<internal-properties>
<property>
<name>LegacyType</name>
<value>3</value>
</property>
<property>
<name>LegacyPoolName</name>
<value>Beach Brochure Browse Pool</value>
</property>
</internal-properties>
<jdbc-data-source-params>
<jndi-name>beachBrochureBrowseDS</jndi-name>
<global-transactions-protocol>None</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>
CP-Beach_Brochure_Browse_Pool-1043-jdbc.xml
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/910/domain.xsd">
<name>Beach Brochure Browse Pool</name>
<internal-properties>
<property>
<name>LegacyType</name>
<value>1</value>
</property>
</internal-properties>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@aserver:1522:adb</url>
<driver-name>oracle.jdbc.driver.OracleDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>gf_user</value>
</property>
<property>
<name>dll</name>
<value>ocijdbc9</value>
</property>
<property>
<name>protocol</name>
<value>thin</value>
</property>
</properties>
<password-encrypted>{3DES}4UT5899x/Z4=</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>1</initial-capacity>
<max-capacity>3</max-capacity>
</jdbc-connection-pool-params>
</jdbc-data-source>
Would anyone be able to point me in the right direction with this? Configuring the Datasources
through the Admin Console creates a single Datasource configuration file that contains its relevent
connection pool configuration, but the Weblogic Upgrade wizard creates a Datasource config file and
a separate connection pool config file. What would I need to do to use the config files generated
by the Weblogic Upgrade wizard?
Any help appreciated
Thanks
Andrew

Similar Messages

What's the difference between using a connection pool and a datasource

Howdy. I figure this is a newbie question, but I can't seem to find an
answer.
In the docs at bea, the datasource docs say
"DataSource objects provide a way for JDBC clients to obtain a DBMS
connection. A DataSource is an interface between the client program and the
connection pool. Each data source requires a separate DataSource object,
which may be implemented as a DataSource class that supports either
connection pooling or distributed transactions."
In there it says the datasource uses the connection pool, but other than
that, what is the difference between a connection pool and a datasource?

Thanks for the info. I think it makes some sense. But it's a bit greek.
I'm sure it'll make more sense the more I work with it. Thanks.
"Chuck Nelson" <[email protected]> wrote in message
news:3dcac1f5$[email protected]..
>
Peter,
Here is a more formal definition of a DataSource from the Sun site
"A factory for connections to the physical data source that thisDataSource object
represents. An alternative to the DriverManager facility, a DataSourceobject
is the preferred means of getting a connection. An object that implementsthe
DataSource interface will typically be registered with a naming servicebased
on the JavaTM Naming and Directory (JNDI) API.
The DataSource interface is implemented by a driver vendor. There arethree types
of implementations:
Basic implementation -- produces a standard Connection object
Connection pooling implementation -- produces a Connection object thatwill automatically
participate in connection pooling. This implementation works with amiddle-tier
connection pooling manager.
Distributed transaction implementation -- produces a Connection objectthat may
be used for distributed transactions and almost always participates inconnection
pooling. This implementation works with a middle-tier transaction managerand
almost always with a connection pooling manager.
Does that help clarify the distinction?
Chuck Nelson
DRE
BEA Technical Support

Multiple sources in a single Connection Pool

Hi Folks,
I have a requirement to import data from two diffrent data sources( for example : Two diffrent database of Oracle in two diffrent servers) using a single connection pool to the physical layers of OBIEE RPD. Can anyone please suggest whether this is possible or not? If yes please provide the steps.

DB Links is an Oracle feature, not an OBIEE. You have to create your DB link in one of the schemas in DB1 so you can connect from there to DB2. Then you can simply create a query that joins data from both DBs:
SELECT * FROM DUAL d1, DUAL@DB2 d2
WHERE d1.dummy = d2.dummy
Search on Google as this is a very popular and simple feature to use. It will allow you to use one connection pool that's connection to two DBs.

How to use JDBC Connection Pools in a standalone application?

Hi, there,
I have a question about how to use JDBC Connection Pools in an application. I know well about connection pool itself, but I am not quite sure how to keep the pool management object alive all the time to avoid being destroyed by garbage collection.
for example, at the website: http://www.developer.com/java/other/article.php/626291, there is a simple connection pool implementation. there are three classes:JDBCConnection, the application's gateway to the database; JDBCConnectionImpl, the real class/object to provide connection; and JDBCPool, the management class to manage connection pool composed by JDBCConnectionImpl. JDBCPool is designed by Singleton pattern to make sure only one instance. supposing there is only one client to use connection for many times, I guess it's ok because this client first needs instantiate JDBCPool and JDBCConnectionImpl and then will hold the reference to JDBCPool all the time. but how about many clients want to use this JDBCPool? supposing client1 finishes using JDBCPool and quits, then JDBCPool will be destroyed by garbage collection since there is no reference to it, also all the connections of JDBCConnectionImpl in this pool will be destroyed too. that means the next client needs recreate pool and connections! so my question is that if there is a way to keep pool management instance alive all the time to provide connection to any client at any time. I guess maybe I can set the pool management class as daemon thread to solve this problem, but I am not quite sure. besides, there is some other problems about daemon thread, for example, how to make sure there is only one daemon instance? how to quit it gracefully? because once the whole application quits, the daemon thread also quits by force. in that case, all the connections in the pool won't get chance to close.
I know there is another solution by JNDI if we develop servlet application. Tomcat provides an easy way to setup JNDI database pooling source that is available to JSP and Servlet. but how about a standalone application? I mean there is no JNDI service provider. it seems a good solution to combine Commons DBCP with JNID or Apache's Naming (http://jakarta.apache.org/commons/dbcp/index.html). but still, I don't know how to keep pool management instance alive all the time. once we create a JNDI enviroment or naming, if it will save in the memory automatically all the time? or we must implement it as a daemon thread?
any hint will be great apprieciated!
Sam

To my knoledge the pool management instance stays alive as long as the pool is alive. What you have to figure out is how to keep a reference to it if you need to later access it.

How to use single connection

Hello Gurus,
I am new in adf and using jdev 11.1.2.3.
I am developing application in which i am using dynamic shell UI. The structure of application is i have one main application modules with the UI shell. The other modules are developed in separate application and has its own data control and task flows and then i deployed them as adf library. Then i am consuming the task flow in the main application.
As i mention each module has its own data control, so when i open a module it makes new connection with database. It means if i have opened ten modules then it is opening ten connections with database.
Is is possible i can configure somewhere to use single connection for all modules and not to open the connection for each module.
And one more thing if i undeploy the application the connection is still with database as v$session view shows it. How i can close connection if i close the tab in ui shell.
Thanks,

Hi, You can explore the option of nesting your AM. Check below links to know more about them.
Decompiling ADF Binaries: What you may need to know about Nested Application Module
Nested application modules | ADF KickStart
Good luck !

How do I find out what is using a connection pool

This morning weblogic 8.1.5 complained it couldn't expand a connection pool because it had reached is max concurrent connects limit.
The issue I have is that I don't actually know what is using the connection pool. It should be defunct and redundent but obviously not.
This caused all the threads to be consumed and the managed server hung.
Does anyone know wether it's possible to interigate the pool to find out what it's doing ? I can't check the db as it's managed by another company and I have a v limited read only account.... I can't even select from v&session.
Cheers in advance for any help.

Dave Snaith wrote:
This morning weblogic 8.1.5 complained it couldn't expand a connection pool because it had reached is max concurrent connects limit.
The issue I have is that I don't actually know what is using the connection pool. It should be defunct and redundent but obviously not.
This caused all the threads to be consumed and the managed server hung.
Does anyone know wether it's possible to interigate the pool to find out what it's doing ? I can't check the db as it's managed by another company and I have a v limited read only account.... I can't even select from v&session.
Cheers in advance for any help.If the pool is not supposed to be used, disable it via the console,
and whatever applications are still trying to use it will get
quick exceptions.
Joe

Sending EDI To Multiple Partners Using Single Send Port in Orchestration

Hi Guys,
I am having a scenario where i am receiving a Xml(which can be in between 11-15). I am having 150 Trading Partners with whom these datsets have to be shared. Now every Trading partner is having there own character Sets and unique numbers so i have created 150
party agreements for all the Trading partners. I am interested to use a single port. I have created an orchestration to achieve this. Below are the steps i used to create orchestration :-
1) Receiving 11 XML from receive shape.
2) Extracting the value of Node TSP(this value is used to know the trading partners unique number on which i am deciding to which party agreement this Xml needs to go) using xpath.
3) I am constructing the message in construct.
3.1) Mapping from XML To EDI.
3.2) As all 11 datasets are having different version. So i am overidding the value ISA and GS in Message Assignment(SourceName).
4) Decide shape to decide on the value of TSP to which port it has to be send.
But according to me this is not an optimized solution. Below are reasons:-
1) I have to create 150 branch into decide shape. As i am receiving 11 different Xml messages i need to create decide shape for all the different Xml messages.
2) I have to create 150 different ports which are having 15 operation(depanding upon Xml we received).
Note:- I have to create 150 different Send Ports only because of Party Agreement. So is there any solution? i only want Single Send port and i can select the party Agreement in the orchestrations.

Duplicate thread. See:
http://social.msdn.microsoft.com/Forums/en-US/c12a377e-ccf6-4fbe-9986-14da63d72282/sending-edi-to-multiple-partners-using-single-send-port-in-orchestration?forum=biztalkgeneral

Error using mySQL connection Pool

I see the following error when my application uses the connection pool - can anyone explain this ?
INFO: CORE3282: stdout: =======================>ERROR :com.sun.enterprise.repository.J2EEResourceException
WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResourcePool.initPool(IASNonSharedResourcePool.java:416)
WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource(IASNonSharedResourcePool.java:625)
WARNING: CORE3283: stderr: at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:520)
INFO: CORE3282: stdout: java.lang.NoSuchMethodException: setdataSourceName

Hi,
You have used dataSourceName property while creating a connection pool.This property is not required to be set while creating a connection pool for MySql
Use the following properties:
<property name="serverName" value="<name of server>"
<property name="port" value="<port number>"
<property name="DatabaseName" value="<your db name>"
<property name="User" value="<user name>"
<property name="Password" value="<passwd>"
Get back in case of any issues

Problem in retriving varray when using weblogic connection pool

Hi,
I had similar problem when we I am using the weblogic connection pool. I had similar setup i.e weblogic 5.1 servicepack9 and oracle 8.1.7.
I cofigarud the weblogic connection pool using Oracle thin driver.
But if I am using with oracle thin driver directly I am able to retrive.
If any one know how to retrive varray from procedure using weblogic connection pool please send me it.
Thanx.
Bye,
Satya

http://docs.oracle.com/javase/6/docs/api/java/sql/Connection.html#setAutoCommit(boolean)

How to use my connection pool in multiple servlets?

I now have a functioning connection pool using these lines in a servlet:
private Connection getConnection(String lookup) throws NamingException, SQLException {
Context context = new InitialContext();
DataSource ds = (DataSource)context.lookup(lookup);
Connection ocon = ds.getConnection();
context.close();
return ocon;
} // private Connection getConnection(String lookup) throws NamingException, SQLException {
========================
If I want to create additional servlets in the same web app which query the same database,
do I need to repeat this block of code in every servlet, or can I just put it in one servlet
and have other servlets access it in some way to get a connection? Should I change the code
above from a "private" Connection to a "public" Connection?
An example servlet is shown below. To put my question another way: If I want to
create a second servlet with a different set of queries, would I just make a copy of the first
servlet and then change only the queries, or is there a more efficient way to have multiple
servlets get connections from the pool?
Any suggestions are greatly appreciated.
Thank you.
Logan
************************************servlet example**********************************
package CraigsClasses;
import javax.servlet.*;
import javax.servlet.jsp.*;
import java.net.*;
import java.util.*;
import java.io.*;
import javax.servlet.http.*;
import java.sql.*;
import java.util.Date;
import java.text.*;
import javax.naming.*;
import javax.sql.DataSource;
public class CraigsMain extends HttpServlet {
public void init(ServletConfig config) throws ServletException {
super.init(config);
private Connection getConnection(String lookup) throws NamingException, SQLException {
Context context = new InitialContext();
DataSource ds = (DataSource)context.lookup(lookup);
Connection ocon = ds.getConnection();
context.close();
return ocon;
} // private Connection getConnection(String lookup) throws NamingException, SQLException {
// Process the http Get request
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
try {
response.setContentType("text/html");
PrintWriter out = response.getWriter();
String sql = "select formtitle from checkboxforms where cbformid = 157";
// error occurs at this line
Connection ocon = getConnection("java:comp/env/jdbc/CraigsList");
PreparedStatement pStmt = ocon.prepareStatement(sql);
ResultSet rs1 = pStmt.executeQuery();
rs1.next();
out.println("<br>" + rs1.getString(1));
rs1.close();
pStmt.close();
ocon.close();
} catch(SQLException sqle) {
System.err.println("sql exception error: " + sqle);
} catch(NamingException ne) {
System.err.println("naming exception error: " + ne);
public void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
doGet(request, response);
=======================================================================

sjasja, Thank you for the reply. What you are suggesting is exactly what I have been looking for. But I'm pretty weak on how to make this separate con pool servlet work. My first attempt is shown below. It doesn't compile this line, which is obviously wrong:
public static Connection getConnection(String lookup) throws NamingException, SQLException {
Could you please help me with this servlet code? Thanks.
package CraigsClasses;
import javax.servlet.*;
import javax.servlet.jsp.*;
import java.net.*;
import java.io.*;
import javax.servlet.http.*;
import java.sql.*;
import javax.naming.*;
import javax.sql.DataSource;
public class ConPoolInit extends HttpServlet {
public void init(ServletConfig config) throws ServletException {
super.init(config);
try {
public static Connection getConnection(String lookup) throws NamingException, SQLException {
Context context = new InitialContext();
DataSource ds = (DataSource)context.lookup(lookup);
Connection ocon = ds.getConnection();
context.close();
return ocon;
} // private Connection getConnection(String lookup) throws NamingException, SQLException {
} catch(SQLException sqle) {
System.err.println("sql exception error: " + sqle);
} catch(NamingException ne) {
System.err.println("naming exception error: " + ne);
=======================================

Can I use same connection pool on multiple web app?

Hi,
I have several web applications on my domain, and they all share the same database.
I am using TOMCAT 4, and I've wrote my own pool, but the problem is that there are also some other domains on the server, so I can't put my connection pool in the tomcat's share or common directory.
Right now, I am thinking of switching to use tomcat's datasource implementation. How do I configure the datasource so that all my web apps will use the same connection pool?
Thanks!

There's no actual webapp configuration when using Datasources... your Java code accesses the Datasource through JNDI:
     Connection con = null;
     String dataSourceName = "someDataSource"
     try {
          Hashtable parms = new Hashtable();
          parms.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.ejs.ns.jndi.CNInitialContextFactory");
          Context ctx = new InitialContext(parms);
          javax.sql.DataSource ds = (javax.sql.DataSource)ctx.lookup(dataSourceName);
          con = ds.getConnection();
     } catch (NamingException e) {
          throw new SQLException("NamingException - " + e.toString());
     }If you want, you can keep the DataSource name in the application's ServletContext, so that you don't hard code it into your Java code.

Difference in use of connection pools from one server to another

Hi all
we are running wl5.1 with sp9 against SQLServer 2000
On our performance test server (2 CPU) which has weblogic & sqlserver runnig
on it we run out out of connection pools when running a specific method,
having looked at it we noticed that it contained nested sql, so that each
client would actually hang onto multiple connections until finished. The
total number of connections used seemed approximately the same as the number
of SQL statements.
However we then ran the weblogic server on a different machine against the
same database, so it was now running over a network and everything worked ok
and the total number of client connections was just 1.
Can anyone shed any light onto this, I have a few ideas but nothing to back
them up as follows:
Multi CPU versus single CPU
Local connection rather than network connection between WLServer and
DBServer
WL Configuration
DBServer configuration
Is nested SQL valid ?
Any help much appreciated Paul Taylor
(An example of what I mean by nested sql is shown below, method1() creates
instances of class2 and calls c2.method which contains sql before releasing
its connection.)
class c1
public void method1()
try
rs=executesql(sqlString)
while rs.next()
new c2();
c2.method2()
finally
closeConnection()
class c2
public void method2()
try
rs=executesql(sqlString)
finally
closeConnection()

because when you are dealing with a remote server, your calls will be
serialized over one socket. and the connection is assigned to that socket
probably...or something like that...or not...shouldn't be important :)
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[email protected]
www.filip.net
"Paul taylor" <[email protected]> wrote in message
news:[email protected]...
The code has now been changed, but the real point was why are two server
dealing with the same code in a different way
"Filip Hanik" <[email protected]> wrote in message
news:[email protected]...
Any help much appreciated Paul Taylor
(An example of what I mean by nested sql is shown below, method1()creates
instances of class2 and calls c2.method which contains sql beforereleasing
its connection.)well this is obviously not a good way of doing it. you know that you are
obtaining multiple connections so why not code your software in a
smarter
way.
pass the connection object into c1 and c2 that way they both use thesame
connection. Or release in between.
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[email protected]
www.filip.net
<l> wrote in message news:[email protected]...
Hi all
we are running wl5.1 with sp9 against SQLServer 2000
On our performance test server (2 CPU) which has weblogic & sqlserverrunnig
on it we run out out of connection pools when running a specific
method,
having looked at it we noticed that it contained nested sql, so thateach
client would actually hang onto multiple connections until finished.
The
total number of connections used seemed approximately the same as thenumber
of SQL statements.
However we then ran the weblogic server on a different machine against
the
same database, so it was now running over a network and everythingworked
ok
and the total number of client connections was just 1.
Can anyone shed any light onto this, I have a few ideas but nothing
to
back
them up as follows:
Multi CPU versus single CPU
Local connection rather than network connection between WLServer and
DBServer
WL Configuration
DBServer configuration
Is nested SQL valid ?
Any help much appreciated Paul Taylor
(An example of what I mean by nested sql is shown below, method1()
creates
instances of class2 and calls c2.method which contains sql beforereleasing
its connection.)
class c1
public void method1()
try
rs=executesql(sqlString)
while rs.next()
new c2();
c2.method2()
finally
closeConnection()
class c2
public void method2()
try
rs=executesql(sqlString)
finally
closeConnection()

How can I use the Connection Pool with DB2

Hi All,
I am facing the problem with the usage for the Connection Pool.
I want to use DB2 via JNDI lookup.
But when starting the Weblogic server, Error occured with the following message.
<Error> <JDBC> <Cannot startup connection pool "MyJDBCPool" Cannot load driver class : com.ibm.db2.jdbc.app.DB2Driver>
DB2 and Weblogic are on the same machine.
In case of the use of remote DB2 database, I also encountered the same error.
Configurations are as follows.
<JDBCConnectionPool DriverName="com.ibm.db2.jdbc.app.DB2Driver"
MaxCapacity="10" Name="MyJDBCPool"
Password="{3DES}gCGsOfD9M6iwOtgL2v/NpA==" Targets="myserver"
TestConnectionsOnReserve="false" TestTableName="test" URL="jdbc:db2://localhost:6789/yongjoo"/>
<SNMPAgent Name="mydomain"/>
<JDBCDataSource JNDIName="acsdb" Name="acsdb" PoolName="MyJDBCPool" Targets="myserver"/>
Could you please give some information about this problem? I will appreciate your kindness.

Hi Joe,
Thanks your help.
Perhaps It's my fault for Weblogic console's setting.
After I reset the target server in console, Error message disappeared.
But, when I call the TestCode, I encountered another error message. The error
is NameNotFoundException.
When lookingup the JNDI name, NameNotFoundException errer occured. I tried to
change my setting and JNDI name, but the results are the same.
Would you please give me some information about this one more time? I will be
appreciated for your help.
Follows are Config.xml
<JDBCConnectionPool DriverName="com.ibm.db2.jdbc.app.DB2Driver" MaxCapacity="10"
Name="MyJDBCPool" Password="{3DES}gCGsOfD9M6iwOtgL2v/NpA==" Targets="myserver"
TestConnectionsOnReserve="false" TestTableName="test"
URL="jdbc:db2://localhost:6789/yongjoo"/> <SNMPAgent Name="mydomain"/>
<JDBCDataSource JNDIName="acsdb" Name="acsdb" PoolName="MyJDBCPool"
Targets="myserver"/>
and follows are TestCode,
url = "t3://localhost:7001"; //default URL
datasource = "jdbc/acsdb";
Context ctx = null;
Hashtable p = new Hashtable();
p.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL, url);
try{
ctx = new InitialContext(p);
System.err.println("initialContext(p)"+ctx); <-- success
ds = (DataSource)ctx.lookup("java:comp/env/jdbc/acsdb");
}catch(NameNotFoundException ne){
throw new ConnectionException(); .
}catch(NamingException ne){
throw new ConnectionException();

Best use of connection pool

hi all,
i have some confusion if someone have good suggetions for me.
i make an connection pool class, and in that package and subpackages i have different class files which do interact with DB thus in whole class files i want to use that same connection pool.
would any one tell me which will be best method to do it.
or i have to pass the connection pool to every class object.
Thanks

InitialContext initialContext = new InitialContext();
DataSource dataSource = (DataSource)initialContext.lookup("connPool");
Connection connection = dataSource.getConnection();You need to do a JNDI lookup for the DataSource and getConnection() from that.
***Annie***

The use of connection pool

Dear all,
I had created a connection pool in Sun Java System Web Server.
But I don't know how to use it.
Would you please tell me how to use it via JSP ?
Thank you very much.
Jack.

InitialContext initialContext = new InitialContext();
DataSource dataSource = (DataSource)initialContext.lookup("connPool");
Connection connection = dataSource.getConnection();You need to do a JNDI lookup for the DataSource and getConnection() from that.
***Annie***

Multiple DataSource using single Connection Pool

Similar Messages

Maybe you are looking for