Connection pooling issue with compiling with jdk 1.5.0

A
javax.naming.NameNotFoundException: Name jdbc is not bound in this Context exception occurs when I run my web app in Tomcat 5 using jdk 1.5. However, I don't get this problem with I use jdk 1.6.0. The mysql connector version is 3.1.1.4 and my server.xml file has been configured correctly. Any suggestions as to why this exception is occurring - I'm assuming it's a version issue but not sure how to solve it!

Use "java:comp/env/jdbc/DbUser" instead of just "jdbc/DbUser" for datasource config
See http://www.tek-tips.com/viewthread.cfm?qid=431734
The mysql connector version is 3.1.1.4Use a more recent jdbc driver
http://dev.mysql.com/downloads/connector/j/5.0.html
http://dev.mysql.com/doc/refman/5.0/en/connector-j-versions.html
Message was edited by:
java_2006

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

  • 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

  • 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/

  • 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Connection pool issue with packaged application

    we are using 9.2 mp1 for a Oarcle packaged application which is talking to Oracle RAC. In production one
    of the RAC nodes went down and we see that the wbelogic connection pool is never able to reconnect
    This is a packaged application Bharosa which internally uses hibernate and in turn relies on weblogic connection pool
    See a few stuck threads in the logs indicating some prolem with the connection cleanup
    <Dec 16, 2008 12:11:03 PM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "626" seconds working on the request "Http Request: /fahost/econnect/IntegratedAuthRemoteServlet.svl;JSPSESSIONID=82W2JLLJ8vCB25G3jyc6cYdXVXLYc1G1GwTt91plpCpB9MY6yQP3!468271380!-864027599!1229457609639", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
         weblogic.common.resourcepool.ResourcePoolImpl.releaseResource(ResourcePoolImpl.java:521)
         weblogic.jdbc.common.internal.ConnectionPool.release(ConnectionPool.java:669)
         weblogic.jdbc.common.internal.ConnectionPoolManager.release(ConnectionPoolManager.java:113)
         weblogic.jdbc.wrapper.PoolConnection.doClose(PoolConnection.java:192)
         weblogic.jdbc.wrapper.PoolConnection.close(PoolConnection.java:117)
         org.hibernate.connection.DatasourceConnectionProvider.closeConnection(DatasourceConnectionProvider.java:74)
         org.hibernate.jdbc.ConnectionManager.closeConnection(ConnectionManager.java:388)
         org.hibernate.jdbc.ConnectionManager.aggressiveRelease(ConnectionManager.java:343)
         org.hibernate.jdbc.ConnectionManager.afterTransaction(ConnectionManager.java:230)
         org.hibernate.jdbc.JDBCContext.afterTransactionCompletion(JDBCContext.java:201)
         org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:127)
         com.bharosa.common.hibernate.HiberDBMgr.commitTransaction(HiberDBMgr.java:293)
         com.bharosa.common.db.BharosaDBMgr.endSession(BharosaDBMgr.java:243)
         com.bharosa.common.hibernate.HiberBaseDAO.executeQuery(HiberBaseDAO.java:596)
         com.bharosa.common.hibernate.HiberBaseDAO.executeDBQuery(HiberBaseDAO.java:543)
         com.bharosa.common.hibernate.HiberDBMgr.executeDBQuery(HiberDBMgr.java:351)
         com.bharosa.vcrypt.dataaccess.impl.VCryptUserDataAccessImpl.getVCryptUserByLoginId(VCryptUserDataAccessImpl.java:520)
         com.bharosa.vcrypt.auth.impl.VCryptAuthImpl.getUserByLoginId(VCryptAuthImpl.java:274)
         com.bharosa.client.BharosaHelper.getUser(BharosaHelper.java:116)
         com.bharosa.client.BharosaHelper.createPersonalizedAuthentiPad(BharosaHelper.java:308)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.getAuthpadHTML(IntegratedAuthDelegateSkeleton.java:672)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.createAuthPad(IntegratedAuthDelegateSkeleton.java:113)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.createAuthPad(IntegratedAuthDelegateSkeleton.java:103)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.invokeService(IntegratedAuthRemoteServlet.java:60)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.doPost(IntegratedAuthRemoteServlet.java:40)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
         weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
         weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
         weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
         weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
         weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    <Dec 16, 2008 12:11:03 PM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "616" seconds working on the request "weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl@ba063", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
         weblogic.common.resourcepool.ResourcePoolImpl.getCurrCapacity(ResourcePoolImpl.java:671)
         weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:1922)
         weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
         weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    <Dec 16, 2008 12:11:03 PM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "635" seconds working on the request "Http Request: /fahost/econnect/IntegratedAuthRemoteServlet.svl;JSPSESSIONID=Q3C6JLLV1lwjqmTWLQ4m5M02BqBKmQzcyt66wY925kykg2pQyB1t!1872529297!468271380!1229457621681", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
         java.net.SocketInputStream.socketRead0(Native Method)
         java.net.SocketInputStream.read(SocketInputStream.java:129)
         oracle.net.ns.Packet.receive(Unknown Source)
         oracle.net.ns.DataPacket.receive(Unknown Source)
         oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
         oracle.net.ns.NetInputStream.read(Unknown Source)
         oracle.net.ns.NetInputStream.read(Unknown Source)
         oracle.net.ns.NetInputStream.read(Unknown Source)
         oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1099)
         oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1070)
         oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:478)
         oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
         oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
         oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10622)
         weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:157)
         org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58)
         org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:195)
         org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:230)
         org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141)
         org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296)
         org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
         org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1009)
         org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:356)
         org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
         com.bharosa.common.hibernate.HiberDBMgr.commitTransaction(HiberDBMgr.java:293)
         com.bharosa.common.db.BharosaDBMgr.endSession(BharosaDBMgr.java:243)
         com.bharosa.common.dataaccess.DataAccessMgr.endSession(DataAccessMgr.java:132)
         com.bharosa.vcrypt.tracker.impl.VCryptTrackerImpl.updateLog(VCryptTrackerImpl.java:1048)
         com.bharosa.vcrypt.tracker.impl.VCryptTrackerImpl.updateLog(VCryptTrackerImpl.java:622)
         com.bharosa.client.BharosaHelper.fingerPrintFlash(BharosaHelper.java:203)
         com.bharosa.client.BharosaHelper.fingerPrintBrowser(BharosaHelper.java:155)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.runPreAuthRules(IntegratedAuthDelegateSkeleton.java:239)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.runPreAuthRules(IntegratedAuthDelegateSkeleton.java:214)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.invokeService(IntegratedAuthRemoteServlet.java:83)
         com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.doPost(IntegratedAuthRemoteServlet.java:40)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
         weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
         weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
         weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
         weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
         weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >

    Hi. Something is seriously ill there. I would ask that you post a full thread dump
    to see what's locking what. You may need an official support case...

  • Oracle connection pool problem (dbcp binded with  jtom)

    Hi,
    my webserver is Tomcat5.0.18, I want to offer the connection pool and transaction management
    in my currently system
    I know in Tomcat5.0 version, we can use the DBCP to offer the database connection pool
    service, to apply the transaction management in my system, I adapt the JTOM
    now, my problem is
    to use DBCP, I setup the datasource factory to be
    org.apache.commons.dbcp.BasicDataSourceFactory, the connection pool is ok, but
    the transaction management offerred by JTOM will failure
    to make the tranaction management of JTOM succeed, I have to setup the datasource factory to be
    org.objectweb.jndi.DataSourceFactory, but the connection pool offerred by Tomcat will failure now
    it seems that these two datasource factory has conflict
    How can I do?, I don't want to use the connection pool offerred in JTOM
    Anyone can help me??
    Thanks in advance

    Hi,
    I don't know the solution for JOTM, but you could try this JTA and its connection pools:
    http://www.atomikos.com ships a JTA that integrates with Tomcat and also provides JDBC connection pooling. There is a GUI control panel so that you don't have to know the XML details for Tomcat's config files.
    Best,
    Guy

  • Connection pooling problem in TopLink with JBoss4.0.3

    Hi All
    I am using JBoss4.0.3SP1 with TopLink-10g(9.0.4.5) and Sybase as database. I am implementing connection pooling of JBoss with Sybase. I have done all the changes in JBoss mapping files.
    Now to enable connection pooling in TopLink I have set the <uses-external-connection-pooling> attribute in sessions.xml file to true and I have added <datasource> attribute corresponding to the datasource defined in JBoss. It is working fine but when I delete the username, password...etc attribute from the sessions.xml then I am not able to get the session from datasource.
    Can anyone tell me what to do or where I am making mistake? Any help on this will be appreciated

    I tried that code also but the project object that I am getting is null which is in this line
    DatabaseLogin login = (DatabaseLogin)mySession.getProject().getLogin();
    mySession is an object of oracle.toplink.sessions.Session interface but when I call this method then it returns me a null object of Project class, so I am getting NullPointerException error. I tried to do this stuff by many ways but I am always getting the NullPointereException in setLogin() method of Session. This is the stackTrace of the error.....
    java.lang.NullPointerException
    at oracle.toplink.publicinterface.Session.setLogin(Session.java:2871)
    at com.test.TestCon.executeQurey(TestCon.java:91)
    at org.apache.jsp.Test_jsp._jspService(org.apache.jsp.Test_jsp:55)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
    at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
    at java.lang.Thread.run(Unknown Source)
    Can you please tell me where I am wrong or any other way to do fix this problem.

  • Two Connection Pools In One Database With Two Phisical Schema

    I have a database with 2 physical schemas. Each physical schema has a different username and password. So i must create a second connection pool. But i have the problem that physical schemas don't understand which connection pool to use. How can i coincide each physical schema to its connection pool automatically.
    Regards

    You need two Physical databases each with its own Connection Pool, within that database will be a single Physical Schema.
    Or you could have a single Database/Connection Pool if it has read access to both schemas.

  • Creagting connection pools dynamically and bind with TxDataSource

              Hi!
              Is there a way I can create a dynamic connection pool and associate it to a DataSource
              using weblogic. I know I can't create a datasource dynamically, so are there
              any work arounds to bind the dynamically created connection pool to configured
              datasource.
              thanks,
              Srinivas
              

    Ken Yeung wrote:
    My application is required to support many different connections to different databases. I'll need to setup potentially hundreds of connection pools (and associated datasources). I was thinking of creating them dynamically through the app as needed.. but, wondering if I can get a way with creating all of them upfront (and setting the initial connections to 0). This way I can set all the database properties via WL console instead of hardcoding in the appl. I would like to know if there's a significant cost to creating datasources and connections pools upfront (even though they're initially not used). Please let me know how you would approach this. thanks.You can certainly create them ahead of time. No significant overhead from simply having
    the pools. However, if you set them up to do periodic refresh they will involve some cycles.

  • 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

  • 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 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

  • Connection pooling issue, urgent

    Hi,
    Our asp.net web application use sAP .net connector to make RFC call to sap CRM system. recently, I am trying to utilizing connection pooling, but assigning connection obtained from pool to proxy class , I did exactly the online help docs says, but, i got some very disappointment result, it cause iis worker process memory write proctection error. and very time, I reboot my machine, the problem does not go away, my O.S tells me that "Data Execution proctection" warning comes up and afterwords, iis worker process and etc, I am not sure what I did wrong, any body experience similar problem,
    after I uninstall .net connection, and I reboot my machine
    , this error went away. Please help.
    following is my configuration settings:
    <SAP>
           <Connector>
                 <ConnectionPool              
                   MaxOpenConnections="20"  
                                 MaxCapacity="20"
                           MaxIdleTime="10"
                           CleanupInterval="10" />                   
                          <Destinations Default="cd1">
                              <Entry
                                DestinationName="cd1"
                                AppServerHost="ASHOST=sapcrd01.bentley.com"
                                SystemNumber="00"
                                Username="ASPRFC"
                                Password="bentley"
                                Client="100"/>                        
                           </Destinations>
              </Connector>
         </SAP>
    following line of code is from myproxy constructor
         this.oCommonProxy.Connection=SAP.Connector.Connection.GetConnectionFromPool(GetConnectStringForUser(this.sRfcUser,this.sRfcPass));
    public void CloseConnection()
                                       SAP.Connector.Connection.ReturnConnection(this.oCommonProxy.Connection);
    Message was edited by: Yuwen Li
    Message was edited by: Yuwen Li

    Hm, sounds strange. Can you try to attach a debugger with both, managed and unmanged mode, turn on "first chance exception handling" for all exception types and check the call stack when the exception happens?

  • 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.

Maybe you are looking for