2 Replies Latest reply on Sep 11, 2013 7:27 PM by 969955

    JDBC Pool Max Capacity not resetting after change - 10.3.5 on RedHat 5.8




      We created an ADF Web Application which is deployed on WebLogic 10.3.5


      .  After reaching 15 JDBC Connections the application fails with the following error:


      oracle.jbo.DMLException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-26061.


      The error code JBO-26061 points to the source of the problem being a limited number of JDBC connections. The default is 15 for Maximum Capacity for JDBC Connections. After increasing the Max Capacity to 60 and restarting WebLogic, our application still fails after 15 connections.  The pdev-jdbc.xml file is showing the correct updates to WebLogic


      . See below:  But still WebLogic still allows only 15 JDBC connections.


      Is there anything else that must be done to allow WebLogic to increase the JDBC connections?  What am I missing?


      Thanks for the help.







      <?xml version='1.0' encoding='UTF-8'?>

      <jdbc-data-source xmlns="http://xmlns.oracle.com/weblogic/jdbc-data-source" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/jdbc-data-source http://xmlns.oracle.com/weblogic/jdbc-data-source/1.0/jdbc-data-source.xsd">





















          <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>