Pointbase Server, Connection Pool Issue

Hi All,
          I have set up a cluster containing two nodes - one local and other
          remote machine.
          I have extended my domain to include the Integration and Workshop
          extensions, as my application needs them. I have also configured the
          Node Manager to start the remote server and also setup the workshop
          database on my machine.
          I have set the classpath in the Node Manager to contain the jars -
          E:\bea_sp5\weblogic81\server\lib\weblogic.jar;E:\bea_sp5\weblogic81\common\eval\pointbase\lib\pbserver44.jar;
          E:\bea_sp5\weblogic81\common\eval\pointbase\lib\pbtools44.jar;
          E:\bea_sp5\weblogic81\server\lib\wli.jar;E:\bea_sp5\weblogic81\server\lib\knex.jar;
          <Jun 15, 2006 2:52:59 PM GMT+05:30> <Info>
          <[email protected]:5557> <Starting Server
          VSDClusterDomain2::MngdServer2 ...>
          <Jun 15, 2006 2:53:00 PM GMT+05:30> <Info>
          <[email protected]:5557> <Server VSDClusterDomain2::MngdServer2
          started, process id = 2,364>
          <Jun 15, 2006 2:53:02 PM GMT+05:30> <Info> <WebLogicServer>
          <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM
          Version 1.4.2_08-b03 from Sun Microsystems Inc.>
          <Jun 15, 2006 2:53:02 PM GMT+05:30> <Info> <Management> <BEA-141140>
          <The managed server is going to contact the admin server at
          http://15.76.223.63:7001 to check if there exists a running admin
          server at this URL.>
          <Jun 15, 2006 2:53:04 PM GMT+05:30> <Info> <Configuration Management>
          <BEA-150017> <This server is being started as a dependent managed
          server.>
          <Jun 15, 2006 2:53:04 PM GMT+05:30> <Info> <Management> <BEA-141107>
          <Version: WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
          WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
          WebLogic Integration 8.1 SP5 Wed Sep 21 21:56:54 PDT 2005 643163>
          <Jun 15, 2006 2:53:04 PM GMT+05:30> <Info> <Configuration Management>
          <BEA-150015> <Connecting to the administration server
          http://15.76.223.63:7001 to retrieve the initial configuration.>
          <Jun 15, 2006 2:53:13 PM GMT+05:30> <Notice> <Log Management>
          <BEA-170019> <The server log file
          E:\bea_sp5\weblogic81\common\nodemanager\MngdServer2\MngdServer2.log is
          opened. All server side log events will be written to this file.>
          <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090082>
          <Security initializing using security realm myrealm.>
          <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090170>
          <Loading the private key stored under the alias DemoIdentity from the
          jks keystore file E:\bea_sp5\weblogic81\server\lib\DemoIdentity.jks.>
          <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090171>
          <Loading the identity certificate stored under the alias DemoIdentity
          from the jks keystore file
          E:\bea_sp5\weblogic81\server\lib\DemoIdentity.jks.>
          <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090169>
          <Loading trusted certificates from the jks keystore file
          E:\bea_sp5\weblogic81\server\lib\DemoTrust.jks.>
          <Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090169>
          <Loading trusted certificates from the jks keystore file
          E:\bea_sp5\jdk142_08\jre\lib\security\cacerts.>
          <Jun 15, 2006 2:53:17 PM GMT+05:30> <Notice> <WebLogicServer>
          <BEA-000328> <Starting WebLogic Managed Server "MngdServer2" for domain
          "VSDClusterDomain2">
          <Jun 15, 2006 2:53:21 PM GMT+05:30> <Warning> <HTTP> <BEA-101296>
          <Unable to load the default compiler class "com.sun.tools.javac.Main".
          Using the default javac compiler to compile JSPs.>
          <Jun 15, 2006 2:53:22 PM GMT+05:30> <Notice> <Cluster> <BEA-000138>
          <Listening for announcements from cluster Cluster1 on 237.0.0.1:7001.>
          <Jun 15, 2006 2:53:22 PM GMT+05:30> <Notice> <Cluster> <BEA-000133>
          <Waiting to synchronize with other running members of Cluster1.>
          <Jun 15, 2006 2:53:53 PM GMT+05:30> <Error> <JDBC> <BEA-001150>
          <Connection Pool "cgJMSPool-nonXA" deployment failed with the following
          error: No registered driver accepts URL:
          jdbc:pointbase:server://15.76.223.63:9093/workshop.>
          <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001150>
          <Connection Pool "bpmArchPool" deployment failed with the following
          error: No registered driver accepts URL:
          jdbc:pointbase:server://15.76.223.63:9093/workshop.>
          <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001150>
          <Connection Pool "cgPool" deployment failed with the following error:
          No registered driver accepts URL:
          jdbc:pointbase:server://15.76.223.63:9093/workshop.>
          <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001151> <Data
          Source "cgDataSource-nonXA" deployment failed with the following error:
          DataSource(cgDataSource-nonXA;weblogic.jdbc.jts.ebusinessPool) can't be
          created with non-existent Pool (connection or multi)
          (cgJMSPool-nonXA).>
          <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001151> <Data
          Source "cgDataSource" deployment failed with the following error:
          DataSource(cgDataSource;cgSampleDataSource) can't be created with
          non-existent Pool (connection or multi) (cgPool).>
          <Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001151> <Data
          Source "bpmArchDataSource" deployment failed with the following error:
          DataSource(bpmArchDataSource) can't be created with non-existent Pool
          (connection or multi) (bpmArchPool).>
          <Jun 15, 2006 2:54:07 PM GMT+05:30> <Alert> <JMS> <BEA-040052>
          <JMSServer "cgJMSServer_auto_2" store failed to open
          java.io.IOException: JMS JDBC store, connection pool =
          <cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool does not exist.
          java.io.IOException: JMS JDBC store, connection pool =
          <cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool does not exist
          at
          weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
          at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
          at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
          at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
          at weblogic.jms.backend.BEStore.open(BEStore.java:262)
          at weblogic.jms.backend.BEStore.start(BEStore.java:151)
          at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
          at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
          at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2939)
          at
          weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
          at
          weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
          at
          weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at
          sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at
          sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at
          weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
          at
          weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
          at
          weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
          at
          weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
          at
          weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          <Jun 15, 2006 2:54:07 PM GMT+05:30> <Error> <JMS> <BEA-040368> <The
          following exception has occurred:
          weblogic.jms.common.JMSException: JMS can not open store
          cgJMSStore_auto_2
          at weblogic.jms.backend.BEStore.start(BEStore.java:163)
          at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
          at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
          at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2939)
          at
          weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
          at
          weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
          at
          weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at
          sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at
          sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at
          weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
          at
          weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
          at
          weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
          at
          weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
          at
          weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          Caused by: java.io.IOException: JMS JDBC store, connection pool =
          <cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool does not exist
          at
          weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
          at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
          at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
          at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
          at weblogic.jms.backend.BEStore.open(BEStore.java:262)
          at weblogic.jms.backend.BEStore.start(BEStore.java:151)
          ... 33 more
          weblogic.jms.common.JMSException: JMS can not open store
          cgJMSStore_auto_2
          at weblogic.jms.backend.BEStore.start(BEStore.java:163)
          at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
          at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
          at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2939)
          at
          weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
          at
          weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
          at
          weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at
          sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at
          sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at
          weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
          at
          weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
          at
          weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
          at
          weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
          at
          weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          Caused by: java.io.IOException: JMS JDBC store, connection pool =
          <cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool does not exist
          at
          weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
          at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
          at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
          at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
          at weblogic.jms.backend.BEStore.open(BEStore.java:262)
          at weblogic.jms.backend.BEStore.start(BEStore.java:151)
          ... 33 more
          --------------- nested within: ------------------
          weblogic.cluster.migration.MigrationException: Failed to activate
          JMSServer cgJMSServer_auto_2 - with nested exception:
          [weblogic.jms.common.JMSException: JMS can not open store
          cgJMSStore_auto_2]
          at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2946)
          at
          weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
          at
          weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
          at
          weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at
          sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at
          sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:324)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at
          weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
          at
          weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
          at
          weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
          at
          weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
          at
          weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          Why do you think this error is occuring? Any other setting needs to be
          done to overcome this problem ?
          Thanks in advance,
          Sandeep

Please verify following
1) have you defined jndi name for database correctly ??
2) Have you added sqljdbc jar file in soa suite server?
3) How much time it takes when you execute same query in JDev ?
4) If you think configuration is issue, please verify the Jdev conn details @ http://soasphere.blogspot.com/2008/11/connecting-sql-server-from-jdeveloper.html and soa suite server side required settings @ Deploy error because of  sql server database adapter

Similar Messages

  • Connection pool issues with Mysql

    Hi,
    I have defined sufficient read connections (50) in the toplink configuration, I am finding toplink is not releasing the connections in Mysql, this is when run from Jboss App server.
    Is anyone aware of toplink connection pool issues with MySql?
    thanks

    TopLink always closes connections, I cannot see how this could occur.
    Please include your persistence.xml or sessions.xml. Also ensure you are closing your EntityManager or ClientSession, especially if using exclusive connections.
    Also include the exception you are getting.
    James : http://www.eclipselink.org

  • Difference between using app server connection pooling and using the driver

    Hi all,
    How to get connection pooling with out application server and tomcat also?
    What is the difference between using app server connection pooling and using the driver supported connection pooling?
    Regards,
    Murali

    maybe the performance of App server pool is better than the JDBC pool,
    for you don't know wether the implementation of the JDBC interface is good or bad.

  • Oracle Application server connection pool and database links

    I am using Oracle application server 10g with connection pools, the db used by the application connects to another oracle db using a database link. My question is when the application starts it creates 10 connections, does it also create x amount of database links as well?

    Hi,
    Is there any way to use the connection pool or Datasource while connecting to database?If I am using a stateless sesssion bean and using a Data Access layer which just creates a database session to write the persistence toplink objects how I can make use of application server connection pool?Hi Vinod,
    Yes, TopLink allows you to use the app server's connection pooling and transaction services. Chapter 2 of the Oracle9iAS TopLink Foundation Library Guide provides details as do the TopLink examples. The easiest way to set this up is by using the sessions.xml file. The sample XML below is from the file <toplink903>\examples\ias\examples\ejb\sessionbean\sessions.xml. Here we are adding the datasource defined in OC4J and specifying that we are using the OC4J transaction controller also.
    <login>
    <user-name>sa</user-name>
    <password></password>
    <datasource>java:comp/env/jdbc/ejbJTSDataSource</datasource>
    <uses-external-transaction-controller>true</uses-external-transaction-controller>
    <uses-external-connection-pool>true</uses-external-connection-pool>
    </login>
    <external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
    When using this approach you need to change your TopLink code slightly in the EJB methods:
    a. Acquire the ACTIVE unit of work from the server
    session (again, see the EmployeeSessionEJB code
    example) with something like:
    UnitOfWork uow = clientSession.getActiveUnitOfWork();
    b. Calls to uow.commit() can be ommitted or commented out
    because the EJB will handle this. Note that of course
    the methods you create in the EJB that are using this
    approach must have TX Required (default).
    Hope this helps.
    Pete

  • WLS 10.3.0.0 Solaris SPARC and DBMS Oracle 10gR2 connection pooling issue

    Hi all,
    we are currently testing Weblogic Server 10.3.0.0 in order to migrate our production system from WLS 8.1 to it.
    While testing the new setup, we encountered some strange behaviour of the connection pooling within WLS.
    We configured a XA-Connection pool to our DB (Oracle 10gR2) by using
    a) the Oracle XA-thin-driver delivered within WLS 10.3.0.0
    and alternatively
    b) the Oracle 11.2.0.2 OCI-driver of the Oracle 11g database client.
    We´ve got the same issue with both variants. We defined an initial capacity of 5 connections and a maximum capacity of 30 connections.
    Our application is running flawlessly using the connection pool, but the amount of active sessions between the application server and the database server is increasing rapidly and the maximum capacity is exceeded. We are seeing up to multiple hundreds of sessions from the application server to our database server. Obviously the connections aren´t cleaned up.
    We are using the following settings for the JDBC-Connection:
    initial capacity = 5
    max. capacity = 30
    Capacity increment = 1
    Statement cache type = LRU
    Statement cache size = 10
    Test connections on reserve = true
    Test frequency = 120
    Test table name = "sql select 1 from dual"
    seconds to trust an idle pool connection = 10
    shrink frequency = 0
    connecttion creation retry frequency = 120
    login delay = 0
    incative connection timeout = 10
    max. waiting for connection = 2147483647
    connection reserve timeout= = -1
    Ignare in-use connections = true
    pinned-to-thread = false
    remoce infected connections enabled = true
    Does anyone have an idea how to track/solve this issue?
    Kind regards
    Marc

    Hi Joe,
    we´ve tested with the thin driver using an initial capacity of 5 and a maximum capacity of 15. During our tests (in a very short time period) the maximum capacity has not been exceeded. But we saw some exceptions in the managed server logfile which made us curious.
    When these exceptions are occuring, a new connection to the database server is established. We are seeing for a short time a total count of 6 connections which is immediately decreasing to the initial capacity of 5. We will do some further testing over the next hours and monitor the connection usage.
    The connection we are dealing with is the one called "ZDB2".
    This is an excerpt of the logfile:
    ####<18.10.2010 19:45 Uhr MESZ> <Debug> <JDBCConn> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-02F7EA174F1D84653A69> <> <1287423940610> <BEA-000000> <java.lang.Exception: Pinned: autoCommit=true,enabled=true,isXA=true,isJTS=false,vendorID=0,connUsed=true,doInit=false,'null',destroyed=false,poolname=ZDB2,appname=null,moduleName=null,connectTime=177,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=true,lastSuccessfulConnectionUse=1287423940605,secondsToTrustAnIdlePoolConnection=10,currentUser=java.lang.Exception
         at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:308)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:314)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:427)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
         at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1473)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1272)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:425)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:382)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:338)
         at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
         at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
         at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
         at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
         at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1547)
         at org.hibernate.loader.Loader.doQuery(Loader.java:673)
         at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
         at org.hibernate.loader.Loader.doList(Loader.java:2220)
         at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104)
         at org.hibernate.loader.Loader.list(Loader.java:2099)
         at org.hibernate.hql.classic.QueryTranslatorImpl.list(QueryTranslatorImpl.java:912)
         at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172)
         at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121)
         at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
         at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:811)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderPersistenceGenerated.findByPrimaryKey(OrderPersistenceGenerated.java:45)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1356)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:830)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1276)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:19812)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1289)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:823)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1341)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:816)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1255)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:7332)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1266)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:809)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1636)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    ,currentThread=Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],lastUser=null,currentError=null,currentErrorTimestamp=null,JDBC4Runtime=true,supportStatementPoolable=true,needRestoreClientInfo=false,defaultClientInfo={} is set to be refreshed
         at weblogic.jdbc.common.internal.ConnectionEnv.setRefreshNeeded(ConnectionEnv.java:518)
         at weblogic.jdbc.wrapper.Connection.getVendorConnection(Connection.java:292)
         at de.dpcom.persistence.hibernate.BinaryBlobType.nullSafeSet(BinaryBlobType.java:109)
         at org.hibernate.type.CustomType.nullSafeSet(CustomType.java:146)
         at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:1997)
         at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2371)
         at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2307)
         at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2607)
         at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92)
         at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
         at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232)
         at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140)
         at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
         at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
         at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CertificatePersistenceGenerated.updateCertificate(CertificatePersistenceGenerated.java:116)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceImplStandard.updateCertificate(CustomerManagementServiceImplStandard.java:1282)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceTransactionHandler.updateCertificateTx(CustomerManagementServiceTransactionHandler.java:711)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceSessionBean.updateCertificate(CustomerManagementServiceSessionBean.java:1104)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementEJB_ap2i9a_ELOImpl.updateCertificate(CustomerManagementEJB_ap2i9a_ELOImpl.java:19199)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceApplicationProxy.updateCertificate(CustomerManagementServiceApplicationProxy.java:1101)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceImpl.publishCertificate(ProductionResultProcessingServiceImpl.java:1131)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceTransactionHandler.publishCertificateTx(ProductionResultProcessingServiceTransactionHandler.java:298)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean.publishCertificate(ProductionResultProcessingServiceSessionBean.java:517)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.publishCertificate(ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.java:1804)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceApplicationProxy.publishCertificate(ProductionResultProcessingServiceApplicationProxy.java:471)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishCertificate(OrderManagementServiceImpl.java:1825)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1664)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940797> <BEA-001072> <Connection for XA pool "ZDB2" created.>
    ####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-001132> <Initialized statement cache of size "10" for connection in pool "ZDB2".>
    ####<18.10.2010 19:45 Uhr MESZ> <Info> <Common> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-000628> <Created "1" resources for pool "ZDB2", out of which "1" are available and "0" are unavailable.>
    Any suggestions?
    Kind regards
    Marc

  • Form Server Connection pooling - Urgent

    how does form server maintains connection pooling. I have defined a single db user through which form server establishes connections with the db, and created application users at application level. The information I like to know if form server maintains certain connection pooling and allow users to get connected if user limit exceeds but responed to them with delay. if it does maintains connection pooling then please elaborate how.???

    Forms doesn't do connection pooling -- each user requires a separate database connection.
    > Allowing remote Internet user connect directly to the
    database appears to pose a serious security/denial-of-
    service risk.
    So this is one of the good reasons to move the web Forms architecture.
    > It doesn't seem appropriate to ask unaffiliated remote
    users to know about, let alone remember database
    credentials for an external database, just to enable
    them to use a simple web-enabled form. Embedding the
    database credentials into the form appears to pose a
    more obvious security risk.
    With Forms on the web, you can hide the username/password/database details from the user. That information can be stored centrally -- either with Forms itself, or with an LDAP server. The end user doesn't have to know any of the details.
    We have customers running their Forms applications on the internet, and the users have no idea of the connection details to the database.
    For extra security, you can use SSL. Forms on the web, though, by default uses 40 bit encryption.
    Why then does Oracle Forms use this client-server
    architecture? Are there any plans to migrate away from,
    or provide an alternative to, this architecture in
    the near future?
    We do have an architecture to resolve these issues. It's called the Forms Listener Servlet Architecture and it's been available for over 2 years.
    If you go to the Forms area on OTN, you can read all about it:
    http://otn.oracle.com/products/forms/content.html
    Regards,
    Robin Zimmermann
    Forms Product Management

  • Error: Creating a Connection Pool: issue with valid transaction levels

    Server: SunOS 5.8 Generic_117350-27 sun4u sparc SUNW,UltraAX-MP
    App Server: Sun Java System Application Server 8.2
    Jar: ojdbc14.jar
    Datasource Classname: oracle.jdbc.pool.OracleConnectionPoolDataSource
    Resource Type: javax.sql.ConnectionPoolDataSource
    [Issue]
    Using /SUNWappserver/lib/ojdbc14.jar, when I create my connection pool in Sun Java System Application Server 8.2, I return the following error each time I try to start the domain:
    [#|2006-07-28T14:53:56.169-0500|WARNING|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=11;|RAR5117 : Failed to obtain/create connection. Reason : The isolation level could not be set: READ_COMMITTED and SERIALIZABLE are the only valid transaction levels|#]
    When I change the value to "SERIALIZABLE" in my domain.xml file, I receive the following error in my server.log:
    Caused by: org.xml.sax.SAXParseException: Attribute "transaction-isolation-level" with value "SERIALIZABLE" must have a value from the list "read-uncommitted read-committed repeatable-read serializable ".
    So, I'm stuck!
    I can't use the values READ_COMMITTED or SERIALIZABLE since the valid values are "read-uncommitted read-committed repeatable-read serializable ".
    Case sensitivity matters.
    Any thoughts or help would be greatly appreciated.
    Thanks,
    --Todd                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    The Oracle JDBC accepts TRANSACTION_READ_COMMITTED and TRANSACTION_SERIALIZABLE isolation levels.
    Example:
    connAttr.setProperty(“TRANSACTION_ISOLATION”, “TRANSACTION_SERIALIZABLE”);
    I'd check with the Apps server folks.
    Kuassi - blog http://db360.blogspot.com/
    ------ book http://www.amazon.com/gp/product/1555583296/

  • Windows Service Enterprise Library Data Access Application Blocks Connection Pooling Issue

    Hello,
    We are developing a windows service using c# .net v 4.5.1 which communicates with SQL database (SQL 2008 R2 x64), communication with SQL server is done using Enterprise Library data access block v 6, The windows service does a file copy process in bulk &
    updates the database about the status of file copy, it is observed that as soon as we start the service the number of connections get max out & we start receiving a "Timeout expired.  The timeout period elapsed prior to obtaining a connection
    from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached."
    This issue is only observed when we run the code logic by deploying it as a windows service, When we run the exactly same code as a standalone exe (right click -> run as administrator) / non windows service, the connections on database are not exceeded
    & we do not receive the above mentioned error.
    The code block which makes calls to the database is under the c# "using" statement, hence connection pooling should be handled by default.
    Could you please recommend any suggestions on areas which I might have missed on to investigate this issue.
    Thanks in advance.

    Hi
    The issue got resolved after refresh the SCOM Data base access service  account in SQL 2012.
    Unable to launch the operations manager 2012 R2 console after extended the C drive of the SQl server ,getting error "The Data
    Access service is either not
    running or not yet initialized.
    Got to your SQL server -->databases-operationsmanager--security-users--locate the daa service account and refresh.issue fixed and am able to luanch.

  • Connection Pooling Issue

    Hi,
    We have a performance issue in one of our Web applications.
    Our environment is Servlets running on IPlanet server / calling stored procedures in Oracle 8.1.6 database.
    The problem we are having is when we have more than a 100 concurrent users accessing the web application,
    the performance is very (pathetically) slow and users get time-out errors.
    But, the same application runs just fine when we have lesser concurrent users (about 50) doing the
    exact same thing.
    We have the sessions param in the database set at 600 and the connection pool max connections as 400.
    Based on the monitoring we have done, we can see that some many connections are Inactive but not
    being re-used by the connection pool. We have checked the servlet code and we close the connection
    immediately after the stored procedure call is completed.
    Please let me know if you have faced similar problems and ideas how to fix this issue.
    Thanks
    Balaji

    The internal TopLink connection pool does not automatically reconnect dead connections.
    You can use an ExceptionHandler in TopLink to do this. Refer to the documentation for more information on TopLink ExceptionHandlers, I believe that there is an example of this. There are some old posts in the forums explaining how to do this if you try searching.
    You could also use a J2EE server's connection pool which may support this.

  • Java Connection Pooling issue with Oracle 10g Express Edition

    Hello
    I have a Java based web application that uses the Oracle 10g Express Edition database. I am using a connection pool to get connections to the database.
    I use the NetBeans IDE and run my web application on the bundled Tomcat server(5.5.7) that comes with the IDE. Though when I initially run the application from the IDE, the connection pool is set up fine, when I recompile my java code and try to run the application again, I get the following error each time:
    Listener refused the connection with the following error:
    ORA-12516, TNS:listener could not find available handler with the
    matching protocol stack.
    The logs before the error shows up, indicate that the connection pool object is fine and gives me the number of available connections and the number of active connections and so on, which I have printed from the constructor of the Connection Pool class:
    For e.g.:
    Cache size = 17
    Available Connections = 17
    Cache Limit = 1000
    Active size = 0
    However, if I kill my Tomcat server process and run the application again, it works fine with no error.
    I looked around for possible causes and solutions and all I could find
    was increasing the processes parameter value in the init.ora file. I have increased the parameter value to from 100 to 20000 now, in increments of 500/1000 each time but it hasnt worked so far.
    Someone else suggested that I increase the size of my connection pool; I initially had it set to a minimum limit of 5, an initial limit of 10 and a maximum limit of 1000. However if I set the Initial Limit to anything above 17 connections, I see the following log on the Bundled Tomcat log and my application doesn't run at all:
    Log: Loading JDBC Driver : class=oracle.jdbc.driver.OracleDriver ...
    Log: Loaded JDBC Driver
    Log: Connection with URL=jdbc:oracle:thin:@localhost:1521:xe as username/password
    Error code not handled : 0
    Exception Message :java.sql.SQLException: Listener refused the connection with the following error:
    ORA-12519, TNS: no appropriate service handler found
    The Connection descriptor used by the client was:
    localhost:1521:xe
    // End of log
    And the Bundled Tomcat server automatically shuts down.
    Again the System.out statements from the Connection Pool class constructor show that the cache has been initialized and that currently there are free connections available in the pool.
    E.g.
    Cache size = 18
    Available Connections = 18
    Cache Limit = 1000
    Active size = 0
    Has anyone faced anything similar? Could someone please suggest what I'm doing wrong here and what I should do to set right this problem?
    Swetha

    hello, please pardon me, my english is basic. i do of my best. i had the same problem until reading the pdf documentation 2 days for java devvelloper.it is simple, follow this way.
    try {OracleDataSource ds;
         Connection conn;
      ds = new OracleDataSource();
      ds.setURL("jdbc:oracle:thin:@localhost");
      conn = ds.getConnection("userid","password");
    Statement stmt = conn.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
    don't forget to Dowload the user client of oracle Express Edition. do the rest of your program and it will work. take a look to the documentation pdf for java develloper. all it is explained.  good look                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Best way to use Sun Web Server connection pooling with Web Application?

    I have a number of applications that run Oracle and MySQL queries via Sun Web Server 6.1. I use the Web Server's built-in connection pooling, which works fairly well.
    As an interface with the connections I receive from the Web Server, I use a class, which (1) accepts the SQL and database name from a tool, (2) Opens the connection, runs the SQL, closes the connection, (3) puts the content of the result set into a Vector of Hashtables, (4) returns that Vector to the tool.
    Why do I use this Vector? That way, in my applications, I don't have to deal with opening connections (or getting them from the pool) and I don't have to worry about closing connections, because that's done automatically by the interface class.
    Is this a dumb approach to use? I'm a bit paranoid about open DB connections, because we have had a number of problems where connections would not be closed, go stale in oracle, and clog up the database resources.
    Can you suggest a better way to (1) smartly control opening and closing connections, and (2) enabling fast database access?
    Sorry, but given this Java/Sun Web Server double topic, I'm going to post the same message on the Web Server board.
    Any tips?
    dailysun
    P.S. For instance, in my tool, I call the interface class in this manner:
    Vector results_v = Database.getSelect("SELECT * FROM TEST","database1");
    getSelect uses the first string as the SQL and the second string as the jndi name of the Web server's database resource. getSelect does all the context stuff to get a connection from the pool, runs the SQL, puts the resultset into a Vector of Hastables (where each row is one Hashtable), and returns the Vector.

    I have a number of applications that run Oracle and MySQL queries via Sun Web Server 6.1. I use the Web Server's built-in connection pooling, which works fairly well.
    As an interface with the connections I receive from the Web Server, I use a class, which (1) accepts the SQL and database name from a tool, (2) Opens the connection, runs the SQL, closes the connection, (3) puts the content of the result set into a Vector of Hashtables, (4) returns that Vector to the tool.
    Why do I use this Vector? That way, in my applications, I don't have to deal with opening connections (or getting them from the pool) and I don't have to worry about closing connections, because that's done automatically by the interface class.
    Is this a dumb approach to use? I'm a bit paranoid about open DB connections, because we have had a number of problems where connections would not be closed, go stale in oracle, and clog up the database resources.
    Can you suggest a better way to (1) smartly control opening and closing connections, and (2) enabling fast database access?
    Sorry, but given this Java/Sun Web Server double topic, I'm going to post the same message on the Web Server board.
    Any tips?
    dailysun
    P.S. For instance, in my tool, I call the interface class in this manner:
    Vector results_v = Database.getSelect("SELECT * FROM TEST","database1");
    getSelect uses the first string as the SQL and the second string as the jndi name of the Web server's database resource. getSelect does all the context stuff to get a connection from the pool, runs the SQL, puts the resultset into a Vector of Hastables (where each row is one Hashtable), and returns the Vector.

  • Sun One Web Server connection pool goes stale after some time

    Hi all,
    I have a few web applications running on Sun One Web Server 6.1 (SP4). I configured a connection pool via the web admin of the web server. I do not know why the connections in the connection pool are never released after some time (this happened for 3 times with a couple of months in between). I need to reboot the web server to solve this problem everytime the connection pool goes stale. I have verified that the resources are released (stream and connection are closed) with proper programming logic. Even so, I think that the connections will be timed out (the setting is 5 minutes) by the web server as a bulletproof even if the resource is not released properly as implemented in the code logic. Can anybody help on this? I have been troubled by this problem by weeks.
    Thank you in advance.

    Hi all,
    I have a few web applications running on Sun One Web Server 6.1 (SP4). I configured a connection pool via the web admin of the web server. I do not know why the connections in the connection pool are never released after some time (this happened for 3 times with a couple of months in between). I need to reboot the web server to solve this problem everytime the connection pool goes stale. I have verified that the resources are released (stream and connection are closed) with proper programming logic. Even so, I think that the connections will be timed out (the setting is 5 minutes) by the web server as a bulletproof even if the resource is not released properly as implemented in the code logic. Can anybody help on this? I have been troubled by this problem by weeks.
    Thank you in advance.

  • SecureWay Directory Server Connection Pool

    Hi!
    I'm trying to limit the number of connections to SecureWay Directory Server. I'm
    developing an application that uses JNDI technology and LDAP protocol to access
    to the SecureWay Directory Server. JNDI is an high-level API that hides the concept
    of connection to the programmers and there's not a relation 1 to 1 between Context
    (JNDI API) and connection. Is there one way to control the number of connections?
    Does SecureWay Directory Server implement a Connection Pool that allows to limit
    the number of connections? If so, how can I change the pool parameters?
    Many thanks.

    Hi,
    the problem exists only in the integration directory. In "Integration Builder: Design (Integration repository)"  there are no problems with viewing and changing objects. Also my user login is not locked due to invalid login attempts.

  • Connection Pool Issue

    Hi , i am new to OBIEE and unable to fix the error...
    In my physical layer , i import a schema (SH) from a data source , and now i am trying to import another schema (HR) using the same connection pool . On doing it , i have successfully imported required columns from two different sources but , when trying to view the data in SH schema using view the data option in physical layer i can view all the columns in the table and the data in it , but when i am trying to view the data of a table in HR schema than i encounter an error saying
    nQSError:17001 oracle error code : 904 , message: ORA-00904: table or view doesnot exist at OCI call OCISStmtExecute+
    Can you tell me the reason for error and solution as well plz ,, I have checked with connection pool , but i am unable to figure the problem

    Hi,
    Refer:Answers: ORA-00942: table or view does not exist at OCI call
    Thanks
    Deva

  • Toplink Mysql Connection pool issues

    I am frequently seeing threads in wait state on toplink connection pool, I have given the stack trace below, anyone has any ideas as to what is happening? is it
    related to connection timeout? or other causes...
    "http-0.0.0.0-8080-2" id=397 idx=0x620 tid=5344 prio=5 alive, in native, waiting
    , daemon
    -- Waiting for notification on: oracle/toplink/threetier/ConnectionPool@0x00
    F181D8[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Metho
    d)
    at java/lang/Object.wait(J)V(Native Method)[optimized]
    at java/lang/Object.wait(Object.java:474)
    at oracle/toplink/threetier/ConnectionPool.acquireConnection(ConnectionPool.
    java:65)
    ^-- Lock released while waiting: oracle/toplink/threetier/ConnectionPool@0x0
    0F181D8[fat lock]
    at oracle/toplink/threetier/ServerSession.allocateReadConnection(ServerSessi
    on.java:412)
    at oracle/toplink/threetier/ServerSession.executeCall(ServerSession.java:443
    at oracle/toplink/internal/queryframework/DatasourceCallQueryMechanism.execu
    teCall(DatasourceCallQueryMechanism.java:193)
    at oracle/toplink/internal/queryframework/DatasourceCallQueryMechanism.execu
    teCall(DatasourceCallQueryMechanism.java:179)
    at oracle/toplink/internal/queryframework/DatasourceCallQueryMechanism.execu
    teSelectCall(DatasourceCallQueryMechanism.java:250)
    at oracle/toplink/internal/queryframework/DatasourceCallQueryMechanism.selec
    tAllRows(DatasourceCallQueryMechanism.java:583)
    at oracle/toplink/internal/queryframework/ExpressionQueryMechanism.selectAll
    RowsFromTable(ExpressionQueryMechanism.java:2483)
    at oracle/toplink/internal/queryframework/ExpressionQueryMechanism.selectAll
    Rows(ExpressionQueryMechanism.java:2441)
    at oracle/toplink/queryframework/ReadAllQuery.executeObjectLevelReadQuery(Re
    adAllQuery.java:467)
    at oracle/toplink/queryframework/ObjectLevelReadQuery.executeDatabaseQuery(O
    bjectLevelReadQuery.java:874)
    at oracle/toplink/queryframework/DatabaseQuery.execute(DatabaseQuery.java:67
    4)
    at oracle/toplink/queryframework/ObjectLevelReadQuery.execute(ObjectLevelRea
    dQuery.java:835)
    at oracle/toplink/queryframework/ReadAllQuery.execute(ReadAllQuery.java:445)
    at oracle/toplink/internal/sessions/AbstractSession.internalExecuteQuery(Abs
    tractSession.java:2260)
    at oracle/toplink/internal/sessions/AbstractSession.executeQuery(AbstractSes
    sion.java:1074)
    at oracle/toplink/internal/sessions/AbstractSession.executeQuery(AbstractSes
    sion.java:1058)
    at oracle/toplink/internal/sessions/AbstractSession.executeQuery(AbstractSes
    sion.java:1017)
    at com/integral/query/QueryServiceC.executeQuery(QueryServiceC.java:1030)
    at com/integral/query/QueryServiceC._find(QueryServiceC.java:525)
    at com/integral/query/QueryServiceC._findAll(QueryServiceC.java:123)
    at com/integral/query/QueryServiceC.findAll(QueryServiceC.java:83)
    at com/integral/query/ejb/QueryServiceC.findAll(QueryServiceC.java:59)

    Hello,
    It looks like you are using a TopLink managed connection pool and do not have enough connections available for the number of threads needing to use one. This results in threads having to wait until one is released from another thread. In the thread shown, it is waiting to get a read connection from the read pool.
    TopLink connection pools are described in the docs at:
    http://www.oracle.com/technology/products/ias/toplink/doc/1013/main/_html/srvclius002.htm#CHDJAECD
    I'd recommend increasing the min/max number of connections to something that is appropriate to handle your peak load based on your applications usage paterns.
    Best Regards,
    Chris

Maybe you are looking for

  • Object not showing up in session after I set it.

    I'm running some code that goes through an array of possible forms that could exist in the session. It attempts to pull each form out of session. If the form does not exist then it declares the form and puts it in session. The problem is that after I

  • Transfer from iPhone 3G to iPhone 4 issues

    Hello everyone, I have an issue with the transfer of my data from one iPhone to another where one might know moe than I do... Situation: Transfer Data from ipgone 3g (4.2.1) to iPhone 4 (7.1.2) So here is what I did: 1) Create 3g Backup 2) Clean up i

  • Problems Seeing Faint Images in Reader XI

    I have not experienced the issue myself, but several of my customers have. They are unable to see faint or phantomed images in Reader XI. I had one customer uninstall the latest update and he was then able to see the images again. Has anyone else bee

  • During snoop. WARNING: received signal 11 from packet

    During snooping the local ip address on a V240. I saw this error: WARNING: received signal 11 from packet 780 What does it mean? Is the hardware faulty? Is snoop faulty? The packet 780 was going outward and has xxxx in place of some data: ETHER: ----

  • Imac 24" 3 gig screen flickering

    over the last few weeks, my imac screen is flickering, and tonight quite bad, i thought it was going to go off at any minute, but after a while it seems to calm down with just the odd flicker. Ive heard story's of the inverters going down on these mo