ResourceLimitException

Hello,
I'm getting the ResourceLimitException during load testing an application, and I hope to find out why I'm getting it here.
Platform:
WL81SP5, Oracle 10g (non-XA driver v10.2.0.1.0), Spring 1.2.8, Hibernate 3.1.3.
Data Source Settings:
Honor Global Transactions=true
Emulate Two Phase Commit=true
Connection Pool Settings:
min=max=50
Connection Reserver Timeout=10sec
JTA Transaction Timeout=300
In my load test script I create 100 user threads all trying to execute a db intensive operation on the server. I have noticed that sometimes I get the ResourceLimitException even before I hit 300 secs (JTA Transaction Timeout). I want to set the Connection Reserver Timeout to a greater value, but BEA website says that if you're using global transactions then conn. reserver timeout is ignored - "If you use global transactions, the Connection Reserve Timeout value is ignored. In this situation, a connection request automatically waits for a connection if one is not available. The amount of time available for an application to wait for a connection (if necessary), connect, and complete the transaction is determined by the transaction time out value."
Based on this, I am wondering why the threads are not waiting for at least 300 seconds to get a new connection from the pool?
Below is the nohup output from my server -
[blah] 2007-Aug-23 12:35:15 ERROR [ExecuteThread: '9' for queue: 'weblogic.kernel.Default'] JDBCExceptionReporter.logExceptions(72) | weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool marketplacePool to allocate to applications, please increase the size of the pool and retry..
[blah] 2007-Aug-23 12:35:15 ERROR [ExecuteThread: '9' for queue: 'weblogic.kernel.Default'] JDBCExceptionReporter.logExceptions(72) | Cannot obtain connection: driverURL = jdbc:weblogic:pool:marketplacePool, props = {enableTwoPhaseCommit=true, connectionPoolID=marketplacePool, jdbcTxDataSource=true, dataSourceName=marketplaceDataSourceTx}
Ref - http://e-docs.bea.com/wls/docs81/jdbc/programming.html

Sledge Hammer wrote:
Hello,
I'm getting the ResourceLimitException during load testing an application, and I hope to find out why I'm getting it here.
Platform:
WL81SP5, Oracle 10g (non-XA driver v10.2.0.1.0), Spring 1.2.8, Hibernate 3.1.3.
Data Source Settings:
Honor Global Transactions=true
Emulate Two Phase Commit=true
Connection Pool Settings:
min=max=50
Connection Reserver Timeout=10secShow me the whole pool configuration. Also,
is your JDBC usage coded to get, use, and close
a JDBC connection all within a given invocation,
and to close the connection without fail, regardless
of any exception, failure or exit path?
Joe
>
JTA Transaction Timeout=300
In my load test script I create 100 user threads all trying to execute a db intensive operation on the server. I have noticed that sometimes I get the ResourceLimitException even before I hit 300 secs (JTA Transaction Timeout). I want to set the Connection Reserver Timeout to a greater value, but BEA website says that if you're using global transactions then conn. reserver timeout is ignored - "If you use global transactions, the Connection Reserve Timeout value is ignored. In this situation, a connection request automatically waits for a connection if one is not available. The amount of time available for an application to wait for a connection (if necessary), connect, and complete the transaction is determined by the transaction time out value."
Based on this, I am wondering why the threads are not waiting for at least 300 seconds to get a new connection from the pool?
Below is the nohup output from my server -
[blah] 2007-Aug-23 12:35:15 ERROR [ExecuteThread: '9' for queue: 'weblogic.kernel.Default'] JDBCExceptionReporter.logExceptions(72) | weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool marketplacePool to allocate to applications, please increase the size of the pool and retry..
[blah] 2007-Aug-23 12:35:15 ERROR [ExecuteThread: '9' for queue: 'weblogic.kernel.Default'] JDBCExceptionReporter.logExceptions(72) | Cannot obtain connection: driverURL = jdbc:weblogic:pool:marketplacePool, props = {enableTwoPhaseCommit=true, connectionPoolID=marketplacePool, jdbcTxDataSource=true, dataSourceName=marketplaceDataSourceTx}
Ref - http://e-docs.bea.com/wls/docs81/jdbc/programming.html

Similar Messages

  • Got ResourceLimitException having 0 connection in JDBC Pool monitoring

    We use Weblogic 8.1 SP5 (8.1.5).
    The Error is:
    weblogic.jdbc.extensions.PoolLimitSQLException:
    weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool STMECO-WWW-DATABASE-P to allocate to applications, please increase the size of the pool and retry..
    The config.xml is:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.driver.OracleDriver"
    InitialCapacity="25" Name="STMECO-WWW-DATABASE-P"
    PasswordEncrypted="secret"
    Properties="user=dsc;dll=ocijdbc9;protocol=thin"
    Targets="dscapplsrv" TestConnectionsOnCreate="true"
    TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
    TestTableName="[email protected]@STMECO" URL="jdbc:oracle:thin:@cicp02:1521:P10PA50"
    />
    Using the console:
    Initial Capacity:                    25
    Maximum Capacity:                    25
    Capacity Increment:                    1
    Seconds to trust an idle pool connection:     0
    Remove Infected Connections Enabled:          True
    Allow Shrinking:                    True
    Shrink Frequency:                    900
    Enable Connection Leak Profiling:          False
    Enable Connection Profiling:               False
    Test Frequency:                         0 seconds
    Test Reserved Connections:               True
    Test Created Connections:               True
    Connection Reserve Timeout:               10 seconds
    Connection Creation Retry Frequency:          0 second
    Inactive Connection Timeout:               0 second
    Maximum Waiting for Connection:               2147483647
    Maximum Connections Made Unavailable:          0
    Test Table Name:          [email protected]@STMECO
    The solution to the problem after the error was to restart the managed and admin servers. The states before and after the restart was:
                   Before Restart     After restart
    = After Errors = No more Error
    Connection delay time:     87          81
    Connections          0          0
    Connection high:     9          3
    Connection total:     100          25
    Wait seconds high:     10          0
    Waiters:          4          0
    Waiters high:          20          0
    My questions are:
    1) How is it possible to have this errors with 0 connection?
    2) How is it possible to have "Connection total: 100" with a maximum capacity of 25?
    3) I see 4 Waiters and 0 connection. Why?
    4) Only a restart solved the problem. No action under Control (reset, suspend ...) was possible. Why?
    Thank's a lot for your help
    Jean-Michel

    houmard wrote:
    We use Weblogic 8.1 SP5 (8.1.5).
    The Error is:
    weblogic.jdbc.extensions.PoolLimitSQLException:
    weblogic.common.resourcepool.ResourceLimitException: No resources
    currently available in pool STMECO-WWW-DATABASE-P to allocate to
    applications, please increase the size of the pool and retry..
    The config.xml is:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.driver.OracleDriver"
    InitialCapacity="25" Name="STMECO-WWW-DATABASE-P"
    PasswordEncrypted="secret"
    Properties="user=dsc;dll=ocijdbc9;protocol=thin"
    Targets="dscapplsrv" TestConnectionsOnCreate="true"
    TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
    TestTableName="[email protected]@STMECO" URL="jdbc:oracle:thin:@cicp02:1521:P10PA50"
    />
    Using the console:
    Initial Capacity:                    25
    Maximum Capacity:                    25
    Capacity Increment:                    1
    Seconds to trust an idle pool connection:     0
    Remove Infected Connections Enabled:          True
    Allow Shrinking:                    True
    Shrink Frequency:                    900
    Enable Connection Leak Profiling:          False
    Enable Connection Profiling:               False
    Test Frequency:                         0 seconds
    Test Reserved Connections:               True
    Test Created Connections:               True
    Connection Reserve Timeout:               10 seconds
    Connection Creation Retry Frequency:          0 second
    Inactive Connection Timeout:               0 second
    Maximum Waiting for Connection:               2147483647
    Maximum Connections Made Unavailable:          0
    Test Table Name:          [email protected]@STMECO
    The solution to the problem after the error was to restart the managed and admin servers. The states before and after the restart was:
                   Before Restart     After restart
    = After Errors = No more Error
    Connection delay time:     87          81
    Connections          0          0
    Connection high:     9          3
    Connection total:     100          25
    Wait seconds high:     10          0
    Waiters:          4          0
    Waiters high:          20          0
    My questions are:
    1) How is it possible to have this errors with 0 connection?0 connections means the pool may have gotten rid of all the
    connections it had, because they failed, and it was unable
    to get the DBMS to give it replacements. The error counts
    accrued before, while using any previously held connections.
    2) How is it possible to have "Connection total: 100" with a maximum capacity of 25?That means that for the life of the pool it started with 25 connections, and
    had to close and replace them each three times on average, having created 100
    connections in total so far, though never having more than 25 at a time.
    3) I see 4 Waiters and 0 connection. Why?A thread dump would probably show each waiter thread waiting for the Oracle
    driver to give the pool a new connection.
    4) Only a restart solved the problem. No action under Control (reset, suspend ...) was possible. Why?It sounds like a serious oracle problem. If I can see a full server thread dump
    it would tell me much. I recommend turning off test-on-create, and test-on-release.
    Those two are usually a waste of time. Test-on-reserve gives all the guarantee
    you need. Also, why is your test table defined that way? Isn't 'DUAL' enough?
    If you are testing access to a remote DBMS, if that is failing, it may be causing
    your symptoms.
    Joe
    Thank's a lot for your help
    Jean-Michel

  • ADF_FACES-60098  ShowPopupBehaviorTag _toClientAlign invalid align ??

    Hi All ,
    Me getting below error when am calling a taskflow thru tabcontext .I know it is not tab context error . Am not getting , how to handle dis issue . where i searched the project for showpopupBehaviour and removed align = center , but still the error is coming .
    Any suggestion , how to debug when dis kind of error arise ..
    thanks in advance.
    <ShowPopupBehaviorTag> <_toClientAlign> invalid align value: center
    <LifecycleImpl> <_handleException> ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RENDER_RESPONSE 6
    javax.faces.FacesException: javax.servlet.ServletException: OracleJSP error:
    oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
         at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:415)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at oracle.adfinternal.view.faces.config.rich.RecordRequestAttributesDuringDispatch.dispatch(RecordRequestAttributesDuringDispatch.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$OverrideDispatch.dispatch(FacesContextFactoryImpl.java:267)
         at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:469)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:140)
         at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
         at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:800)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:294)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:214)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: javax.servlet.ServletException: OracleJSP error:
    oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
         at oracle.jsp.runtimev2.JspReportUtil.reportException(JspReportUtil.java:181)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:737)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:524)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:444)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:163)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:184)
         at oracle.adfinternal.view.faces.taglib.region.IncludeTag.__include(IncludeTag.java:442)
         at oracle.adfinternal.view.faces.taglib.region.RegionTag$1.call(RegionTag.java:153)
         at oracle.adfinternal.view.faces.taglib.region.RegionTag$1.call(RegionTag.java:128)
         at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:503)
         at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:50)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspNode.execute(OracleJspNode.java:89)
         at oracle.jsp.runtimev2.ShortCutServlet._jspService(ShortCutServlet.java:89)
         at oracle.jsp.runtime.OracleJspBase.service(OracleJspBase.java:29)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:422)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:802)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:726)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:524)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:444)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:163)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:184)
         at oracle.adfinternal.view.faces.taglib.region.IncludeTag.__include(IncludeTag.java:442)
         at oracle.adfinternal.view.faces.taglib.region.IncludeTag.doEndTag(IncludeTag.java:232)
         at oracle.adfinternal.view.faces.taglib.region.PageTemplateTag.doEndTag(PageTemplateTag.java:162)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:62)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspNode.execute(OracleJspNode.java:89)
         at oracle.jsp.runtimev2.ShortCutServlet._jspService(ShortCutServlet.java:89)
         at oracle.jsp.runtime.OracleJspBase.service(OracleJspBase.java:29)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:422)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:802)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:726)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:524)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
         at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)
         ... 53 more

    thanks Frank ,
    i have figured it , there are invalid params in the map .After removing them the error is not replicated .
    Now i got another issue . which mentioned below ,
    If am opening the particular commandlink which i have launch activity method where am calling another task flow . In which i got pervious error , it has been solved by removing the unwanted params in Map. Now am getting the below errror .
    if am using rest of the pages or navigation the application is running fine . but i click dis particular link , me getting the jdbc error.
    how can i debug this isssue when it is coming for dis particular scenario.
    <LifecycleImpl> <_handleException> ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RENDER_RESPONSE 6
    javax.faces.FacesException: javax.servlet.ServletException: OracleJSP error:
    oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
         at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:415)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at oracle.adfinternal.view.faces.config.rich.RecordRequestAttributesDuringDispatch.dispatch(RecordRequestAttributesDuringDispatch.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)
         at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$OverrideDispatch.dispatch(FacesContextFactoryImpl.java:267)
         at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:469)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:140)
         at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
         at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:800)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:294)
         at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:214)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: javax.servlet.ServletException: OracleJSP error:
    oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
         at oracle.jsp.runtimev2.JspReportUtil.reportException(JspReportUtil.java:181)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:737)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:524)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:444)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:163)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:184)
         at oracle.adfinternal.view.faces.taglib.region.IncludeTag.__include(IncludeTag.java:442)
         at oracle.adfinternal.view.faces.taglib.region.RegionTag$1.call(RegionTag.java:153)
         at oracle.adfinternal.view.faces.taglib.region.RegionTag$1.call(RegionTag.java:128)
         at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:503)
         at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:50)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspNode.execute(OracleJspNode.java:89)
         at oracle.jsp.runtimev2.ShortCutServlet._jspService(ShortCutServlet.java:89)
         at oracle.jsp.runtime.OracleJspBase.service(OracleJspBase.java:29)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:422)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:802)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:726)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:524)
         at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:444)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:163)
         at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:184)
         at oracle.adfinternal.view.faces.taglib.region.IncludeTag.__include(IncludeTag.java:442)
         at oracle.adfinternal.view.faces.taglib.region.IncludeTag.doEndTag(IncludeTag.java:232)
         at oracle.adfinternal.view.faces.taglib.region.PageTemplateTag.doEndTag(PageTemplateTag.java:162)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:62)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspNode.execute(OracleJspNode.java:89)
         at oracle.jsp.runtimev2.ShortCutServlet._jspService(ShortCutServlet.java:89)
         at oracle.jsp.runtime.OracleJspBase.service(OracleJspBase.java:29)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:422)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:802)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:726)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:524)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
         at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)
         ... 53 more
    Caused by: oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
         at oracle.jbo.server.DBTransactionImpl.establishNewConnection(DBTransactionImpl.java:1030)
         at oracle.jbo.server.DBTransactionImpl.initTransaction(DBTransactionImpl.java:1170)
         at oracle.jbo.server.DBTransactionImpl.initTxn(DBTransactionImpl.java:6823)
         at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:301)
         at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:332)
         at oracle.jbo.common.ampool.DefaultConnectionStrategy.connect(DefaultConnectionStrategy.java:203)
         at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolConnect(ApplicationPoolMessageHandler.java:592)
         at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolMessage(ApplicationPoolMessageHandler.java:422)
         at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:8995)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:4603)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.prepareApplicationModule(ApplicationPoolImpl.java:2533)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:2343)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:3242)
         at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:572)
         at oracle.jbo.http.HttpSessionCookieImpl.useApplicationModule(HttpSessionCookieImpl.java:234)
         at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:505)
         at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:500)
         at oracle.adf.model.bc4j.DCJboDataControl.initializeApplicationModule(DCJboDataControl.java:516)
         at oracle.adf.model.bc4j.DCJboDataControl.getApplicationModule(DCJboDataControl.java:862)
         at oracle.adf.model.binding.DCDataControl.setErrorHandler(DCDataControl.java:483)
         at oracle.jbo.uicli.binding.JUApplication.setErrorHandler(JUApplication.java:261)
         at oracle.adf.model.BindingContext.put(BindingContext.java:1326)
         at oracle.adf.model.binding.DCDataControlReference.getDataControl(DCDataControlReference.java:174)
         at oracle.adf.model.BindingContext.instantiateDataControl(BindingContext.java:1045)
         at oracle.adf.model.dcframe.DataControlFrameImpl.doFindDataControl(DataControlFrameImpl.java:1565)
         at oracle.adf.model.dcframe.DataControlFrameImpl.internalFindDataControl(DataControlFrameImpl.java:1437)
         at oracle.adf.model.dcframe.DataControlFrameImpl.findDataControl(DataControlFrameImpl.java:1397)
         at oracle.adf.model.BindingContext.internalFindDataControl(BindingContext.java:1175)
         at oracle.adf.model.BindingContext.get(BindingContext.java:1128)
         at oracle.adf.model.binding.DCUtil.findSpelObject(DCUtil.java:328)
         at oracle.adf.model.binding.DCBindingContainer.evaluateParameterWithElCheck(DCBindingContainer.java:1490)
         at oracle.adf.model.binding.DCBindingContainer.findDataControl(DCBindingContainer.java:1590)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.getDataControl(JUCtrlActionBinding.java:566)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.internalCheckPermission(JUCtrlActionBinding.java:2038)
         at oracle.jbo.uicli.binding.JUCtrlActionBinding.invoke(JUCtrlActionBinding.java:736)
         at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.executeEvent(PageLifecycleImpl.java:402)
         at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding._execute(FacesCtrlActionBinding.java:252)
         at oracle.adfinternal.view.faces.model.binding.FacesCtrlActionBinding.execute(FacesCtrlActionBinding.java:210)
         at sun.reflect.GeneratedMethodAccessor571.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.el.parser.AstValue.invoke(Unknown Source)
         at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
         at oracle.adf.controller.internal.util.ELInterfaceImpl.invokeMethod(ELInterfaceImpl.java:173)
         at oracle.adfinternal.controller.activity.MethodCallActivityLogic.execute(MethodCallActivityLogic.java:162)
         at oracle.adfinternal.controller.engine.ControlFlowEngine.executeActivity(ControlFlowEngine.java:993)
         at oracle.adfinternal.controller.engine.ControlFlowEngine.doRouting(ControlFlowEngine.java:879)
         at oracle.adfinternal.controller.engine.ControlFlowEngine.doRouting(ControlFlowEngine.java:778)
         at oracle.adfinternal.controller.engine.ControlFlowEngine.invokeTaskFlow(ControlFlowEngine.java:243)
         at oracle.adfinternal.controller.state.ChildViewPortContextImpl.invokeTaskFlow(ChildViewPortContextImpl.java:104)
         at oracle.adfinternal.controller.state.ControllerState.createChildViewPort(ControllerState.java:1380)
         at oracle.adfinternal.controller.ControllerContextImpl.createChildViewPort(ControllerContextImpl.java:78)
         at oracle.adf.controller.internal.binding.DCTaskFlowBinding.createRegionViewPortContext(DCTaskFlowBinding.java:440)
         at oracle.adf.controller.internal.binding.DCTaskFlowBinding.getViewPort(DCTaskFlowBinding.java:358)
         at oracle.adf.controller.internal.binding.TaskFlowRegionModel.doProcessBeginRegion(TaskFlowRegionModel.java:164)
         at oracle.adf.controller.internal.binding.TaskFlowRegionModel.processBeginRegion(TaskFlowRegionModel.java:112)
         at oracle.adf.view.rich.component.fragment.UIXRegion$RegionContextChange.doChangeImpl(UIXRegion.java:1199)
         at oracle.adf.view.rich.context.DoableContextChange.doChange(DoableContextChange.java:91)
         at oracle.adf.view.rich.component.fragment.UIXRegion._beginInterruptibleRegion(UIXRegion.java:693)
         at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:498)
         at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:50)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspIterationTagNode.executeHandler(OracleJspIterationTagNode.java:45)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87)
         at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58)
         at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:261)
         at oracle.jsp.runtime.tree.OracleJspNode.execute(OracleJspNode.java:89)
         at oracle.jsp.runtimev2.ShortCutServlet._jspService(ShortCutServlet.java:89)
         at oracle.jsp.runtime.OracleJspBase.service(OracleJspBase.java:29)
         at oracle.jsp.runtimev2.JspPageTable.compileAndServe(JspPageTable.java:665)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:385)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:802)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:726)
         ... 175 more
    Caused by: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool prismdb to allocate to applications, please increase the size of the pool and retry..
         at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:252)
         at weblogic.jdbc.pool.Driver.connect(Driver.java:161)
         at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:651)
         at weblogic.jdbc.jts.Driver.connect(Driver.java:127)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:364)
         at oracle.jbo.server.DBTransactionImpl.establishNewConnection(DBTransactionImpl.java:990)
         ... 277 more
    <RegistrationConfigurator> <handleError> ADF_FACES-60096:Server Exception during PPR, #1
    javax.servlet.ServletException: OracleJSP error:
    oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
         at oracle.jsp.runtimev2.JspReportUtil.reportException(JspReportUtil.java:181)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:737)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    Edited by: user9010551 on Apr 22, 2013 5:14 AM

  • [原创] 有关Weblogic Connection Pool 连接恢复的问题

    这是一个古老的问题,一直困扰我,这里既然碰到了,就看看能不能解决。
    环境描述:
    WEBLOGIC版本是8.1 SP2,数据库是SQL SERVER 2000,分别部署在两个服务器上。
    第一步:
    问题描述:
    数据库服务器重新启动,导致WEBLOGIC 的CONNECTION POOL中的连接中断,EJB无法获得连接,导致应用出错。
    解决方法:
    进入WEBLOGIC ADMIN CONSOLE,
    Services->JDBC->Connection Pools->Config->Connections, 点开Advanced Options.
    打开 Test Reserved Connections ,Test Created Connections,Test Released Connections这三个选项。
    将Test Table Name属性设置为:sysproperties(SQL Server系统表,即使自己的应用不存在,这个表也存在,而且默认的内部没有数据)
    根据如下解释:
    Connections that fail the test are closed and reopened to re-establish a valid physical database connection.
    (You must specify a Test Table Name below.)
    每次调用首先进行测试连接,如果测试失败连接将重新建立。
    测试结果:
    WEBLOGIC启动后,关闭数据库SQL SERVER,应用服务器前端调用此时失败。
    重新启动SQL SERVER后,WEBLOGIC端略做等待,前端应用恢复正常。
    第二步:
    问题描述:
    进一步测试,如果WEBLOGIC先启动,启动完成后再启动数据库。
    在WEBLOGIC CONSOLE得到如下输出:
    <2006-3-22 上午11时50分08秒 GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for p
    ool "MyJDBC Connection Pool": [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.>
    <2006-3-22 上午11时50分10秒 GMT+08:00> <Error> <JDBC> <BEA-001150> <Connection Pool "MyJDBC Connection Pool" deployment
    failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: [Microsoft][SQLServe
    r 2000 Driver for JDBC]Error establishing socket..>
    <2006-3-22 上午11时50分10秒 GMT+08:00> <Error> <JDBC> <BEA-001151> <Data Source "MyJDBC Data Source" deployment failed w
    ith the following error: DataSource(jdbc/OMSEIITxDS) can't be created with non-existent Pool (connection or multi) (MyJD
    BC Connection Pool).>
    Unable to deploy EJB: XXXXXXX from XXXXXXX.jar:
    [EJB:011028]The DataSource with the JNDI name: jdbc/XXXXXX could not be located. Please ensure that the DataSource h
    as been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
    1、在默认初始化打开的连接一一失败以后,连接池发现可用的连接为0,郁闷的宣布自己部署失败。
    2、接着数据源发现没有可用的连接池,自己也宣布部署失败。
    3、下面所有的EJB发现不了数据源的JNDI名,部署也全部失败。
    应用启动完成后,大部分EJB的状态为INACTIVE。前端应用无法使用,此时启动数据库,前端应用无法使用。
    手动重新部署 EJB失败,错误还是找不到JNDI,前端应用无法使用。
    手动重新部署 连接池,数据源后,部署EJB 依然失败。前端应用无法使用。
    解决方法:
    进入WEBLOGIC ADMIN CONSOLE,
    Services->JDBC->Connection Pools->Config->Connections, 点开Advanced Options.

    Connection Creation Retry Frequency 参数设置为 60。
    ConnectionCreationRetryFrequencySeconds含义:
    当创建数据库连接时,如果数据库不可用(如数据库没启动),隔多长时间试着重新创建该连接,
    WLS8.1会每隔ConnectionCreationRetryFrequencySeconds秒重试一次.直到JDBC POOL创建成功
    参考:http://dev2dev.bea.com.cn/techdoc/20030469.html,‘JDBC Connect Pool’部分。
    英文解释可以直接控制台上看到,或者edocs查。
    测试结果:
    将数据库关闭,WEBLOGIC重新启动。
    在WEBLOGIC CONSOLE得到如下输出:
    打开Connection Creation Retry Frequency 参数后,连接池在第一轮尝试失败以后,就成功部署了,数据源也成功部署。
    EJB部署会失败,但是提示也与先前的不同:
    Unable to deploy EJB: XXXXXXX from XXXXXXX.jar:
    weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool MyJDBC Connection Pool to
    allocate to applications, please increase the size of the pool and retry..
    每隔一段时间会看到,CONNECTION POOL不断的重新进行连接:
    <2006-3-22 下午12时17分56秒 GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for p
    ool "MyJDBC Connection Pool": [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.>
    在WEBLOGIC启动完成后,所有EJB为INACTIVE状态。
    启动数据库服务器,稍后,手动重新部署所有的EJB,EJB可以部署成功,前端应用可以正常使用。
    此时,此问题已经基本解决,仍需要手动部署EJB。
    第三步:
    问题描述:
    解决方法:
    有关部署次序的问题,首先查阅WEBLOGIC文档,http://edocs.bea.com/wls/docs81/faq/deploy.html#744900,得到
    WebLogic Server deploys server-level resources (first JDBC and then JMS) before deploying applications.
    Applications are deployed in this order: connectors, then EJBs, then Web Applications.
    If the application is an EAR, the individual components are loaded in the order in which they are declared
    in the application.xml deployment descriptor.
    WEBLOGIC先部署服务器端资源,JDBC -> JMS....,然后部署我们的应用,EJB->WEB APPLICATION。
    实际从WEBLOGIC启动日志来看,即使打开了Connection Creation Retry Frequency,如果当时数据库不是可用的,CONNECTION POOL
    会不断的调度CONNECTION进行重新连接。但是此时,EJB的部署也同时在进行。个人猜测这应该是两个不同的线程(组)分别调度的任务。
    现在考虑的是能不能用StartupClass截住EJB的部署过程,粗略的说是如果DATASOURCE没有连接好,或者没有可用的连接池,
    就不往下进行EJB部署的过程。
    参考:http://edocs.bea.com/wls/docs81/config_xml/EJBComponent.html#DeploymentOrder
    DeploymentOrder:
    A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable
    items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and
    deploys startup classes.Items with the lowest Deployment Order value are deployed first.
    There is no guarantee on the order of deployments with equal Deployment Order values.
    There is no guarantee of ordering across clusters. Default: 1000 Minimum: 0 Maximum: 2N31-1
    在部署同一类应用时,按照 DEPLOYMENT LOADER的数值决定,数值越小越先。(EJB的参数在ADMIN CONSOLE界面上叫做LOAD ORDER)
    而且上面看来服务器是先部署EJB,再部署STARTUP CLASS,遗憾了。
    好在STARTUP CLASS上有两个选项,
    Run Before Application Deployments
    Run Before Application Activations
    这两个选项分别可以设置StartupClass分别在系统资源部署之前,以及在系统资源部署和用户应用部署之间启动。
    选上Run Before Application Activations。
    现在可以了,我写了一个STARTUP CLASS,思路见下:
    主代码:
    private void testConnection(){
    while (!isTimeout() && !getConnection()){
    try{
    Thread.sleep(testInterval*1000);
    }catch(Exception ignor){}
    log("DBConnectHolder job finished with following status:");
    log("Timeout:"+isTimeout +",Connection OK:"+isConnected);
    测试结果:
    只要配置的等待时间足够长,应用服务器先行启动的情况下,等待数据库启动后才进行EJB等等的部署。
    (主要考虑如果数据库连接不OK,EJB启动了也没有太大用,还得手工重新部署。)算是比较完满的解决了问题。
    另外一个思路是是否可行? 通过MBean, 在CONNECTION 建立起来以后通知一把,进行EJB的重新部署。
    没来得及研究,请有经验的同学帮我补充完善。
    结论:
    其实也没什么结论,只是把自己遇到问题,解决问题的思路写了一下。短时间内阅读的文献有限,可能采用了一些苯方法
    ,或者走了弯路,也请大家拍砖。
    在WL8版本上,数据库连接进行恢复和重新连接的时候,上面提出的几个参数应该是比较重要的,我再次强调一下。
    Services->JDBC->Connection Pools->Config->Connections, 点开Advanced Options.
    Test Reserved Connections
    Test Created Connections
    Test Released Connections
    Test Table Name
    Connection Creation Retry Frequency

    在第一个情景中应该只需要打开Test Reserved Connections 就可以了。
    Test Created Connections表示创建连接后放到pool之前进行测试看连接是否可用
    Test Released Connections表示释放连接回到pool之前进行测试看连接是否可用
    I think so!

  • Internal error: Cannot obtain XAConnection

    I am porting my application from WL8.1-SQl2000 to Sql Server2005. I went in for the Microsoft’s <i><b>MS SQL Server Driver(Type 4 XA) Versions:2000</b></i> and the corresponding one for non-XA also. Then in the next step where we usually give the other DB properties like DB name, server name etc, there is a field called “Properties” which defines the basic properties which we have configured. In that field, there is a new property having name-value pair : dataSourceName=SQL2000JDBC. I am not sure what this would do, so I just left it to remain & continued with the other things.
    This, in no way affected the proper execution of my application.
    I have 1 XA datasource & 3 non-XA datasources configured for my application.
    When I start my server, in the comman prompt, a resource limit exception appears & then the server proceeds to start successfully. I am also abe to save things into the DB & do all other tests properly. But this keeps hindering me. Our DB server is configured to accept infinite connections, so its absurd to get a connection not available exception.
    I doubt whether the initial datasource property that I have mentioned can have anything to do with this exception during startup. Please help me.
    Exception trace:
    <Nov 15, 2006 12:29:34 PM EST> <Warning> <JDBC> <BEA-001064> <Ignoring property
    'enableTwoPhaseCommit' for JDBCTxDataSource "TweDS". This property is used only
    for those drivers that do not natively support XA.>
    java.sql.SQLException: Internal error: Cannot obtain XAConnection weblogic.commo
    n.resourcepool.ResourceLimitException: No resources currently available in pool
    ITestPool to allocate to applications, please increase the size of the pool and
    retry..
    at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
    315)
    at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
    at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
    ce.java:305)
    at com.taxware.twe.util.SQLConnection.getConnection(SQLConnection.java:1
    68)
    at com.taxware.twe.audit.AuditStartUp.main(AuditStartUp.java:333)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.j
    ava:229)
    at
    weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.
    java:160)
    at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.j
    ava:36)

    charu s wrote:
    I am porting my application from WL8.1-SQl2000 to Sql Server2005. I went in for the Microsoft???
    s <i><b>MS SQL Server Driver(Type 4 XA) Versions:2000</b></i> and the corresponding one for non-XA also. Then in the next step where we usually give the other DB properties like DB name, server name etc, there is a field called ???Properties??? which defines the basic properties which we have configured. In that field, there is a new property having name-value pair : dataSourceName=SQL2000JDBC. I am not sure w
    hat this would do, so I just left it to remain & continued with the other things.
    This, in no way affected the proper execution of my application.
    I have 1 XA datasource & 3 non-XA datasources configured for my application.
    When I start my server, in the comman prompt, a resource limit exception appears & then the server proceeds to start successfully. I am also abe to save things into the DB & do all other tests properly. But this keeps hindering me. Our DB server is configured to accept infinite connections, so its absurd to get a connection not available exception.
    I doubt whether the initial datasource property that I have mentioned can have anything to do with this exception during startup. Please help me.
    The pool's max capacity is defined as lower than the need at
    the time. Please show me the full pool definition from the
    config.xml. It may also have something to do with the fact
    that your code is a startup class, and are you sure the
    pool is ready at this time?
    Joe
    Exception trace:
    <Nov 15, 2006 12:29:34 PM EST> <Warning> <JDBC> <BEA-001064> <Ignoring property
    'enableTwoPhaseCommit' for JDBCTxDataSource "TweDS". This property is used only
    for those drivers that do not natively support XA.>
    java.sql.SQLException: Internal error: Cannot obtain XAConnection weblogic.commo
    n.resourcepool.ResourceLimitException: No resources currently available in pool
    ITestPool to allocate to applications, please increase the size of the pool and
    retry..
    at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
    315)
    at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
    at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
    ce.java:305)
    at com.taxware.twe.util.SQLConnection.getConnection(SQLConnection.java:1
    68)
    at com.taxware.twe.audit.AuditStartUp.main(AuditStartUp.java:333)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.j
    ava:229)
    at
    weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.
    java:160)
    at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.j
    ava:36)

  • Weblogic.jdbc.extensions.PoolLimitSQLException:No resources avail.  in pool

    Hi,
    We are getting the following exceptions. I am also appending the JDBC settings we are using. This is a high volume transaction application.
    weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool <DataSourceName> to allocate to applications, please increase the size of the pool and retry..
    ERROR;- Error creating a transaction for database default
    org.hibernate.exception.GenericJDBCException: Cannot open connection
    ERROR;- Session not found in endSession for database default. This is not okay. refCount=0
    FATAL;- Found lingering open database session. referenceCount=-1
    <?xml version='1.0' encoding='UTF-8'?>
    <jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi=
    "http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="ht
    tp://www.bea.com/ns/weblogic/910/domain.xsd">
    <name>DataSource</name>
    <jdbc-driver-params>
    <url>jdbc:oracle:thin:@serverName:1521:braz2prd</url>
    <driver-name>oracle.jdbc.OracleDriver</driver-name>
    <properties>
    <property>
    <name>user</name>
    <value>brsadmin</value>
    </property>
    </properties>
    <password-encrypted>{3DES}RWHcVDJQGsEUeR3LGNjB9A==</password-encrypted>
    </jdbc-driver-params>
    <jdbc-connection-pool-params>
    <initial-capacity>10</initial-capacity>
    <max-capacity>30</max-capacity>
    <capacity-increment>10</capacity-increment>
    <test-connections-on-reserve>true</test-connections-on-reserve>
    <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
    </jdbc-connection-pool-params>
    <jdbc-data-source-params>
    <jndi-name>bharosaDataSource</jndi-name>
    <global-transactions-protocol>OnePhaseCommit</global-transactions-protocol>
    </jdbc-data-source-params>
    </jdbc-data-source>
    Thanks in advance. Please suggest..
    Thanks,
    Shashi.

    Shashi Yarlagadaa wrote:
    Hi,
    We are getting the following exceptions. I am also appending the JDBC settings we are using. This is a high volume transaction application.
    weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool <DataSourceName> to allocate to applications, please increase the size of the pool and retry..
    ERROR;- Error creating a transaction for database default
    org.hibernate.exception.GenericJDBCException: Cannot open connection
    ERROR;- Session not found in endSession for database default. This is not okay. refCount=0
    FATAL;- Found lingering open database session. referenceCount=-1
    <?xml version='1.0' encoding='UTF-8'?>
    <jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi=
    "http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="ht
    tp://www.bea.com/ns/weblogic/910/domain.xsd">
    <name>DataSource</name>
    <jdbc-driver-params>
    <url>jdbc:oracle:thin:@serverName:1521:braz2prd</url>
    <driver-name>oracle.jdbc.OracleDriver</driver-name>
    <properties>
    <property>
    <name>user</name>
    <value>brsadmin</value>
    </property>
    </properties>
    <password-encrypted>{3DES}RWHcVDJQGsEUeR3LGNjB9A==</password-encrypted>
    </jdbc-driver-params>
    <jdbc-connection-pool-params>
    <initial-capacity>10</initial-capacity>
    <max-capacity>30</max-capacity>
    <capacity-increment>10</capacity-increment>
    <test-connections-on-reserve>true</test-connections-on-reserve>
    <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
    </jdbc-connection-pool-params>
    <jdbc-data-source-params>
    <jndi-name>bharosaDataSource</jndi-name>
    <global-transactions-protocol>OnePhaseCommit</global-transactions-protocol>
    </jdbc-data-source-params>
    </jdbc-data-source>
    Thanks in advance. Please suggest..
    Thanks,
    Shashi.Hi. I suggest turning on the pool's idle connection timeout to
    something slightly longer than you'd expect your longest invocation
    to take, and see if the problem goes away. Also, it is better to
    make your init capacity = 30 rather than ask the pool to grow
    at runtime. Also, keep the capacityIncrement = 1.
    Joe

  • Weblogic 10.3 JNDI with SQL Server

    Hi Friends, I am working on a project which requires connection with MS SQL Server.
    I created a data source using weblogic admin console, and used "BEA's MS SQL Server Driver(Type 4) Version:7.0,2000,2005",( I selected one phase commit),and I am able to connect to the data base server with out having any problem , and getting the data. I was doing some couple of operations which are required for my application, after completion of 5 to 6 calls to database, it was showing the error that
    *"SQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool "testJDBCDataSource" to allocate to applications, please increase the size of the pool and retry..*
    Though my pool size "Initial Capacity:" 3 , "Maximum Capacity: 25" , "Capacity Increment:" 1
    I didn't find any problem in code. We are properly closing the connection where ever necessary.
    Before creating this datasource , we used to connect to the database using normal JDBC connection (class.forName(...) kind of code).
    When I started creating this , it was working fine for couple of transactions but after some time it is showing the above error message.
    Please help
    Thanks a lot
    Peter

    Hi thanks a lot for your reply.
    You mean to say,you want me to make the connection as parameter to a method.
    in my case I am doing like this
    public Connection getConnection() {
              try {
                   // Put the connection properties into hash table.
                   Hashtable<String, String> vibeHash = new Hashtable<String, String>();
                   vibeHash.put(Context.INITIAL_CONTEXT_FACTORY,
                             "weblogic.jndi.WLInitialContextFactory");
                   vibeHash.put(Context.PROVIDER_URL, "t3://localhost:7001");
    in this case this method is returning a connection object , so that people are using this method and getting the connection.
    Can you suggest me , this kind of calls give any problem.
    Thanks a lot
    Peter

  • How to Troubleshoot the Connection Pool Exception?

    Dear Oracle Gurus, very good afternoon to you.
    I'm looking forward for some tips/troubleshoting guide to escape from the below exception, that occres very frequently to one of application that 100+ users will login from different locations & work on and update the data and save their work, where all in sudden they can't acces the application and it gets down.
    Most of the times in the server log I observed below.
    weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool RemoteDesktop.main to allocate to applications, please increase the size of the pool and retry..
    Please help me on, how to overcome this kind of exception.
    In Weblogi c server I see below kind of Warnings.
    If you set the buffer size to zero in a servlet, it would fail to respond and would initiate an infinite loop in the server. WebLogic Server would ultimately display a Errors:
    ExecuteThread: '157' for queue: 'weblogic.kernel.Default' has been busy for "633" seconds working on the request "Http Request: : ../updates/process_manager.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.
    I searched over google for this kind of error, See otherusers posted the same kind of errors but didn't have any positive replies to troubleshoot this issue.
    I also got Oracle Dev link on Weblogic version upgrade product where they fixed similar kind of error it seems. Which is shown below.
    http://docs.oracle.com/cd/E13222_01/wls/docs61/notes/bugfixes2.html -- BUG # CR106186
    details:
    "Suspend Checker Thread" prio=10 tid=0x23eb90 nid=0xfec runnable
    <May 14, 2003 10:53:34 AM PDT> <Warning> <WebLogicServer> <000337>
    <ExecuteThread: '10' for queue: 'default' has been busy for "1,181" seconds working on the request "Http Request: servlet_uri", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
    This problem was solved with a code fix.
    Looking forward for some help, Thank you inadvance.
    FYI..
    I'm using oracle thin driver JDBC connection/Weblogic 8.1
    Edited by: user1072948 on Apr 26, 2012 11:55 AM

    I agree that looking into the number of connections that you have open when you see
    weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool RemoteDesktop.main to allocate to applications, please increase the size of the pool and retry..
    would be a good idea; but I would suggest that you don't increase without thinking about the consequences. I would look more closely at what the connections to the database are doing, for instance, how long are the connection being left open for? What are the queries that are being run? Should you expect to see all the connections in the connection pool being used? What is the current connection pool limit? Are you simply going to increase the number of connections to find that they are also waiting? What is the load on the database at the time?
    It's the other error that you say you see
    ExecuteThread: '157' for queue: 'weblogic.kernel.Default' has been busy for "633" seconds working on the request "Http Request: : ../updates/process_manager.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.
    What does this JSP do? Why would this be busy for so long? Is it related to the previous exception that you have? I'd ask you delevelopment team to look into this.
    In short, it sounds like you have load issues on your server(s) and a careful tuning of the system after a full analysis (thread dumps, heap profiling, connection pool monitoring and code review) would probably be beneficial. It may be that restricting the thread pool may help, it may be that increasing the connection pool would help. I'd not plump for a quick fix here.

  • GetConnection from Oracle Database Cloud Service

    I created a table at the internal JCS instance, and tried to create a web service to insert the data into the table. It's a simple insert operation, so I prefer to coding it without JPA or ADF business component.
    So far, the web service works, but it can't connect to database service.
    Here is my code snippet of the web service method which deployed on JCS, and the jndi name is database,
            try {
                Context ctx = new InitialContext();
                DataSource ds = (DataSource)ctx.lookup("database");
                conn = ds.getConnection();
                String sql = "insert into bvrequest(user_id,activity) values(?,?)";
                pstmt = conn.prepareStatement(sql);
                pstmt.setString(1, userid);
                pstmt.setString(2, activity);
                pstmt.executeUpdate();
                return "OK";
    The thrown exception is,
    weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool database to allocate to applications, please increase the size of the pool and retry..
    Is it a correct way to use Database Cloud Service? Any suggestion/comment is welcome.
    -Paula

    Hi Paula -
    I think you need to ask this question in the Java Cloud Service forum.  If you are trying to make a connection to a Database Cloud Service from Java outside the Oracle Public Cloud, you cannot do it with JDBC.  You can only use RESTful Web Services from outside the Oracle Public Cloud to access the Oracle Database Cloud.
    Hope this helps.
    - Rick Greenwald

  • OSB Managed Servers Overloaded

    Hi All,
    We have a clustered environment in production. We have one Admin and four managed server. We have mostly DB calls. The initial and final capacity of the data source connecting to the DB are 0 and 15. The legacy DB are controlled by another company. So we have some restrictions to access the DB.
    In the managed server logs, we have seen many stuck threads. There are many different exceptions which we have seen in our logs.
    Exception 1:
    WLS_SOA1.log:####<Dec 30, 2011 9:40:50 AM CST> <Info> <Common> <mxwsoa01.nextel.com.mx> <WLS_SOA1> <[ACTIVE] ExecuteThread: '33' for queue: 'weblogic.kernel.Default (se
    lf-tuning)'> <<anonymous>> <BEA1-6D7C081F160117E7989D> <> <1325259650738> <BEA-000627> <Reached maximum capacity of pool "wp_prod_bgn", making "0" new resource instance
    s instead of "1".>
    Exception 2:
    USTOMER_NETWORK API. Cause: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool wp_prod_bgn to allocate to applications, please increase the size of the pool and retry..
    Error Code: 0
    ; nested exception is:
         BINDING.JCA-11812
    Interaction processing error.
    Error while processing the execution of the MIT.KMIT_CUST_NET_STORE_SERVICE.PMIT_CUSTOMER_NETWORK API interaction.
    An error occurred while processing the interaction for invoking the MIT.KMIT_CUST_NET_STORE_SERVICE.PMIT_CUSTOMER_NETWORK API. Cause: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool wp_prod_bgn to allocate to applications, please increase the size of the pool and retry..
    Error Code: 0
    Check to ensure that the XML containing parameter data matches the parameter definitions in the XSD. This exception is considered retriable, likely due to a communication failure. Because the global transaction is rolling back the invoke must be retried in a new transaction, restarting from the place of the last transaction commit. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).
         at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:667)
         at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:357)
    ***After this the servers went to oveloaded state. Then I restarted the server. After this I got the Below exception.***
    Exception 3:
    ####<Dec 31, 2011 1:24:28 AM CST> <Warning> <RMI> <mxwsoa02.nextel.com.mx> <WLS_OSB2> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1325316269000> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.jdbc.common.internal.RmiDataSource.getConnection()
    java.lang.UnsupportedOperationException: Remote JDBC disabled.
    java.lang.UnsupportedOperationException: Remote JDBC disabled
    at weblogic.jdbc.common.internal.JDBCServerHelperImpl.<clinit>(JDBCServerHelperImpl.java:36)
    at weblogic.jdbc.common.internal.JDBCService.initialize(JDBCService.java:91)
    at weblogic.jdbc.common.internal.JDBCService.start(JDBCService.java:134)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    Kindly explain when the servers go to overloaded state??
    When this state recovers automatically?? Else what is the solution to resolve when servers are overloaded??
    If server restart is the solution then when I have to restart the server?? ie., what is the wait time before we take a decision that the overloaded status is not going to recover and must be restarted ?
    How to optimize the connection to avoid max connections used problems?
    Kindly help me in resolving this issue.
    Regards,
    Prabhu

    Internal Exception: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool wp_prod_bgn to allocate to applications, please increase the size of the pool and retry..I think error itself has indicated resolution. The data source maximum capacity needs to be increased. I would also suggest to have initial and maximum capacities equal with Shrink Frequency as 15 mins.
    Kindly explain when the servers go to overloaded state?? There may be various reasons like heavy load, scarcity of resources etc. As an example, in your case, DS connection pool reached to it's maximum capacity and requests were getting refused for new connection which resulted in overload situation.
    When this state recovers automatically?? Else what is the solution to resolve when servers are overloaded?? Once the load decreases, server will come back to normal automatically. I don't prefer server bounce. Even if server gets crashed, node manager should be able to automatically recover the server.
    If server restart is the solution then when I have to restart the server?? ie., what is the wait time before we take a decision that the overloaded status is not going to recover and must be restarted ?I don't think at all that server restart should be performed in case of overload situation. Let the server process the pending requests and handle the situation. If it fails, make sure that node manager is able to recover the servers.
    How to optimize the connection to avoid max connections used problems?Suggested above.
    Make sure to scrutinize your application as well. See if there are areas of improvement in terms of performance.
    Regards,
    Anuj

  • JMS Exception - unable to connect to the JMS destination

    Hi,
    I've configured WebLogic10R3 Cluster with one Admin Server and 2 Managed Servers.
    I deployed the application to the Cluster. (Ie. both Managed 1 and Managed Server 2.)
    I am geeting the following JMS destination not found exception while starting the Second Managed Server.
    There are no errors occurred in the First Managed Server.
    {color:#ff0000}&lt;Warning&gt; &lt;EJB&gt; &lt;BEA-010061&gt;
    &lt;The Message-Driven EJB: SysAuditLogger is unable to connect to the JMS destination: topic/efpAuditTopic.
    The Error was: weblogic.jms.common.JMSException: could not find Server efpserver_man2
    Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
    Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
    Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server efpserver_man2
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:efpserver_man2.
    Resolved 'weblogic .messaging.dispatcher'; remaining name 'S:efpserver_man2&gt;{color}
    Configuration Details:
    ##config.xml:
    &lt;?xml version='1.0' encoding='UTF-8'?&gt;
    &lt;domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/wls [http://www.bea.com/ns/weblogic/90/security/wls.xsd] [http://www.bea.com/ns/weblogic/920/domain] [http://www.bea.com/ns/weblogic/920/domain.xsd] [http://www.bea.com/ns/weblogic/90/security/xacml] [http://www.bea.com/ns/weblogic/90/security/xacml.xsd] [http://www.bea.com/ns/weblogic/90/security] [http://www.bea.com/ns/weblogic/90/security.xsd]"&gt;
    &lt;name&gt;efpdomain&lt;/name&gt;
    &lt;domain-version&gt;10.3.0.0&lt;/domain-version&gt;
    &lt;security-configuration&gt;
    &lt;name&gt;efpdomain&lt;/name&gt;
    &lt;realm&gt;
    &lt;sec:authentication-provider xsi:type="wls:default-authenticatorType"&gt;&lt;/sec:authentication-provider&gt;
    &lt;sec:authentication-provider xsi:type="wls:default-identity-asserterType"&gt;
    &lt;sec:active-type&gt;AuthenticatedUser&lt;/sec:active-type&gt;
    &lt;/sec:authentication-provider&gt;
    &lt;sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"&gt;&lt;/sec:role-mapper&gt;
    &lt;sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-authorizerType"&gt;&lt;/sec:authorizer&gt;
    &lt;sec:adjudicator xsi:type="wls:default-adjudicatorType"&gt;&lt;/sec:adjudicator&gt;
    &lt;sec:credential-mapper xsi:type="wls:default-credential-mapperType"&gt;&lt;/sec:credential-mapper&gt;
    &lt;sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"&gt;&lt;/sec:cert-path-provider&gt;
    &lt;sec:cert-path-builder&gt;WebLogicCertPathProvider&lt;/sec:cert-path-builder&gt;
    &lt;sec:name&gt;myrealm&lt;/sec:name&gt;
    &lt;/realm&gt;
    &lt;default-realm&gt;myrealm&lt;/default-realm&gt;
    &lt;credential-encrypted&gt;{3DES}hcdd+yZGXk5DHgRKqCM7E86l4+VxPcZ9Ut7rB6WaXqMyvbtDjDUKNCKbMQdCN/BEYCv5E0N4Hms9kntfqhaduDO1WGMtbmJL&lt;/credential-encrypted&gt;
    &lt;node-manager-username&gt;weblogic&lt;/node-manager-username&gt;
    &lt;node-manager-password-encrypted&gt;{3DES}Q2xO0EiChbay/HkRiorTjg==&lt;/node-manager-password-encrypted&gt;
    &lt;/security-configuration&gt;
    &lt;server&gt;
    &lt;name&gt;AdminServer&lt;/name&gt;
    &lt;listen-address&gt;192.168.12.240&lt;/listen-address&gt;
    &lt;/server&gt;
    &lt;server&gt;
    &lt;name&gt;efpserver_man1&lt;/name&gt;
    &lt;listen-port&gt;8011&lt;/listen-port&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;listen-address&gt;192.168.12.240&lt;/listen-address&gt;
    &lt;xml-registry&gt;XMLEFP&lt;/xml-registry&gt;
    &lt;jta-migratable-target&gt;
    &lt;user-preferred-server&gt;efpserver_man1&lt;/user-preferred-server&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;/jta-migratable-target&gt;
    &lt;/server&gt;
    &lt;server&gt;
    &lt;name&gt;efpserver_man2&lt;/name&gt;
    &lt;listen-port&gt;8012&lt;/listen-port&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;listen-address&gt;192.168.12.240&lt;/listen-address&gt;
    &lt;xml-registry&gt;XMLEFP&lt;/xml-registry&gt;
    &lt;jta-migratable-target&gt;
    &lt;user-preferred-server&gt;efpserver_man2&lt;/user-preferred-server&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;/jta-migratable-target&gt;
    &lt;/server&gt;
    &lt;cluster&gt;
    &lt;name&gt;efpcluster&lt;/name&gt;
    &lt;cluster-address&gt;192.168.12.240:8011,192.168.12.240:8012&lt;/cluster-address&gt;
    &lt;multicast-address&gt;239.192.0.0&lt;/multicast-address&gt;
    &lt;/cluster&gt;
    &lt;embedded-ldap&gt;
    &lt;name&gt;efpdomain&lt;/name&gt;
    &lt;credential-encrypted&gt;{3DES}q/XQGirHcAcgi4iwPiXIkRHP8xte4xVBgJwjM+qMwbk=&lt;/credential-encrypted&gt;
    &lt;/embedded-ldap&gt;
    &lt;configuration-version&gt;10.3.0.0&lt;/configuration-version&gt;
    &lt;app-deployment&gt;
    &lt;name&gt;efp&lt;/name&gt;
    &lt;target&gt;efpcluster&lt;/target&gt;
    &lt;module-type&gt;ear&lt;/module-type&gt;
    &lt;source-path&gt;applications\efp.ear&lt;/source-path&gt;
    &lt;security-dd-model&gt;DDOnly&lt;/security-dd-model&gt;
    &lt;/app-deployment&gt;
    &lt;xml-registry&gt;
    &lt;name&gt;XMLEFP&lt;/name&gt;
    &lt;document-builder-factory&gt;weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl&lt;/document-builder-factory&gt;
    &lt;sax-parser-factory&gt;weblogic.apache.xerces.jaxp.SAXParserFactoryImpl&lt;/sax-parser-factory&gt;
    &lt;transformer-factory&gt;weblogic.apache.xalan.processor.TransformerFactoryImpl&lt;/transformer-factory&gt;
    &lt;/xml-registry&gt;
    &lt;jms-server&gt;
    &lt;name&gt;eFpJMSServer&lt;/name&gt;
    &lt;target&gt;efpserver_man1 (migratable)&lt;/target&gt;
    &lt;persistent-store&gt;eFpJMSJDBCStore&lt;/persistent-store&gt;
    &lt;/jms-server&gt;
    &lt;jms-server&gt;
    &lt;name&gt;eFpJMSServer2&lt;/name&gt;
    &lt;target&gt;efpserver_man2 (migratable)&lt;/target&gt;
    &lt;persistent-store&gt;eFpJMSJDBCStore2&lt;/persistent-store&gt;
    &lt;/jms-server&gt;
    &lt;migratable-target&gt;
    &lt;name&gt;efpserver_man1 (migratable)&lt;/name&gt;
    &lt;notes&gt;繧キ繧ケ繝・&Beta;逕滓・縺ォ繧医k繝・ヵ繧ゥ繝ォ繝医・繧オ繝シ繝千畑遘サ陦悟庄閭ス蟇セ雎。縺ァ縺吶€よ焔蜍輔〒蜑企勁縺励&uarr;縺・〒縺上□縺輔>縲・/notes&gt;
    &lt;user-preferred-server&gt;efpserver_man1&lt;/user-preferred-server&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;/migratable-target&gt;
    &lt;migratable-target&gt;
    &lt;name&gt;efpserver_man2 (migratable)&lt;/name&gt;
    &lt;notes&gt;繧キ繧ケ繝・&Beta;逕滓・縺ォ繧医k繝・ヵ繧ゥ繝ォ繝医・繧オ繝シ繝千畑遘サ陦悟庄閭ス蟇セ雎。縺ァ縺吶€よ焔蜍輔〒蜑企勁縺励&uarr;縺・〒縺上□縺輔>縲・/notes&gt;
    &lt;user-preferred-server&gt;efpserver_man2&lt;/user-preferred-server&gt;
    &lt;cluster&gt;efpcluster&lt;/cluster&gt;
    &lt;/migratable-target&gt;
    &lt;jdbc-store&gt;
    &lt;name&gt;eFpJMSJDBCStore&lt;/name&gt;
    &lt;prefix-name&gt;WLJMS_&lt;/prefix-name&gt;
    &lt;data-source&gt;eFpNonXADataSource&lt;/data-source&gt;
    &lt;target&gt;efpserver_man1 (migratable)&lt;/target&gt;
    &lt;/jdbc-store&gt;
    &lt;jdbc-store&gt;
    &lt;name&gt;eFpJMSJDBCStore2&lt;/name&gt;
    &lt;prefix-name&gt;WLJMS2_&lt;/prefix-name&gt;
    &lt;data-source&gt;eFpNonXADataSource&lt;/data-source&gt;
    &lt;target&gt;efpserver_man2 (migratable)&lt;/target&gt;
    &lt;/jdbc-store&gt;
    &lt;jms-system-resource&gt;
    &lt;name&gt;eFPJMS&lt;/name&gt;
    &lt;target&gt;efpcluster&lt;/target&gt;
    &lt;sub-deployment&gt;
    &lt;name&gt;eFPServer&lt;/name&gt;
    &lt;target&gt;eFpJMSServer&lt;/target&gt;
    &lt;/sub-deployment&gt;
    &lt;sub-deployment&gt;
    &lt;name&gt;eFPServer2&lt;/name&gt;
    &lt;target&gt;eFpJMSServer2&lt;/target&gt;
    &lt;/sub-deployment&gt;
    &lt;descriptor-file-name&gt;jms/efpjms-jms.xml\JMS Description-jms.xml&lt;/descriptor-file-name&gt;
    &lt;/jms-system-resource&gt;
    &lt;admin-server-name&gt;AdminServer&lt;/admin-server-name&gt;
    &lt;jdbc-system-resource&gt;
    &lt;name&gt;eFpDataSource&lt;/name&gt;
    &lt;target&gt;efpcluster&lt;/target&gt;
    &lt;descriptor-file-name&gt;jdbc/eFpDataSource-2004-jdbc.xml&lt;/descriptor-file-name&gt;
    &lt;/jdbc-system-resource&gt;
    &lt;jdbc-system-resource&gt;
    &lt;name&gt;eFpNonXADataSource&lt;/name&gt;
    &lt;target&gt;efpcluster&lt;/target&gt;
    &lt;descriptor-file-name&gt;jdbc/eFpNonXADataSource-6172-jdbc.xml&lt;/descriptor-file-name&gt;
    &lt;/jdbc-system-resource&gt;
    &lt;/domain&gt;
    ##JMS Description-jms.xml
    &lt;?xml version='1.0' encoding='UTF-8'?&gt;
    &lt;weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms [http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd]"&gt;
    &lt;connection-factory name="ConnectionFactory"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;jms/ConnectionFactory&lt;/jndi-name&gt;
    &lt;security-params&gt;
    &lt;attach-jmsx-user-id&gt;false&lt;/attach-jmsx-user-id&gt;
    &lt;/security-params&gt;
    &lt;/connection-factory&gt;
    &lt;connection-factory name="XAConnectionFactory"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;jms/XAConnectionFactory&lt;/jndi-name&gt;
    &lt;transaction-params&gt;
    &lt;transaction-timeout&gt;3600&lt;/transaction-timeout&gt;
    &lt;xa-connection-factory-enabled&gt;true&lt;/xa-connection-factory-enabled&gt;
    &lt;/transaction-params&gt;
    &lt;security-params&gt;
    &lt;attach-jmsx-user-id&gt;false&lt;/attach-jmsx-user-id&gt;
    &lt;/security-params&gt;
    &lt;/connection-factory&gt;
    &lt;uniform-distributed-queue name="ActiveActivityQueue"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;queue/efpActiveActivityQueue&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;forward-delay&gt;-1&lt;/forward-delay&gt;
    &lt;reset-delivery-count-on-forward&gt;true&lt;/reset-delivery-count-on-forward&gt;
    &lt;/uniform-distributed-queue&gt;
    &lt;uniform-distributed-topic name="AdminTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpAdminTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;uniform-distributed-topic name="AuditTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpAuditTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;uniform-distributed-topic name="ErrorTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpErrorTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;uniform-distributed-topic name="FreeTextTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpFreeTextTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;uniform-distributed-topic name="ReportingTopic"&gt;
    &lt;default-targeting-enabled&gt;true&lt;/default-targeting-enabled&gt;
    &lt;jndi-name&gt;topic/efpReportingTopic&lt;/jndi-name&gt;
    &lt;load-balancing-policy&gt;Round-Robin&lt;/load-balancing-policy&gt;
    &lt;/uniform-distributed-topic&gt;
    &lt;/weblogic-jms&gt;
    -----

    Getting the following exception while trying to connect the JMS destination I am using weblogic 10.3.3 connecting to oracle AQ. The config has been done as per the 'Interoperating with Oracle AQ JMS' document from oracle. I could see that while deploying the application the number of connections in the database increasing to 15 and getting the following error message.
    <Jun 15, 2011 4:14:29 PM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: SampleEJBBean is unable to connect to the JMS destination: jms/propQueue. Th
    e Error was:
    oracle.jms.AQjmsException: Internal error: Cannot obtain XAConnection weblogic.c
    ommon.resourcepool.ResourceLimitException: No resources currently available in p
    ool TestDataSource to allocate to applications, please increase the size of the
    pool and retry..
    at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal
    (ResourcePoolImpl.java:555)
    at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
    ePoolImpl.java:332)
    at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
    ePoolImpl.java:322)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
    ava:438)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
    ava:317)
    at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
    nPoolManager.java:93)
    at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
    nPoolManager.java:61)
    at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:
    1670)
    at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
    468)
    at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
    at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
    ce.java:355)
    at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
    at oracle.jms.AQjmsXAConnection.createXAQueueSession(AQjmsXAConnection.j
    ava:214)
    at weblogic.ejb.container.internal.JMSConnectionPoller.setUpQueueSession
    s(JMSConnectionPoller.java:1545)
    at weblogic.ejb.container.internal.JMSConnectionPoller.createJMSConnecti
    on(JMSConnectionPoller.java:2047)
    at weblogic.ejb.container.internal.JMSConnectionPoller.connect(JMSConnec
    tionPoller.java:787)
    at weblogic.ejb.container.internal.MDConnectionManager.startConnectionPo
    lling(MDConnectionManager.java:244)
    at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDriv
    enManager.java:584)
    at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.mdManagerSt
    art(MessageDrivenBeanInfoImpl.java:1334)
    at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessa
    geDrivenBeans(MessageDrivenBeanInfoImpl.java:1314)
    at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDrivenBeans(
    EJBDeployer.java:1669)
    at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:14
    93)
    at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:614)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(Module
    ListenerInvoker.java:249)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
    teDriver.java:427)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
    river.java:43)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
    eDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartMod
    ulesFlow.java:28)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.ja
    va:1269)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
    river.java:43)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.
    java:409)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleM
    oduleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.activate(Deploym
    entStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(Ap
    pContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.ac
    tivate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.ac
    tivateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
    Commit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.co
    mmit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
    entCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeplo
    ymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(
    DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.com
    mit(DeploymentServiceDispatcher.java:164)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
    ackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
    ackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
    ackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
    gWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

  • Getting "weblogic.jdbc.extensions.PoolLimitSQLException:" error oracle databse cloud

    I build a servlet applocation which access the data on cloud. But when i ran it it gave me the following error
    weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool javatrial5196db to allocate to applications, please increase the size of the pool and retry..
    How to overcome it???????????

    I think this could be caused by connection leaks, are you closing your connections correctly in your code i.e. do you have try / catch / finally to handle graceful release of connections ? If that is not the issue then you will likely need to contact the JCS operations to debug further.
    Jani Rautiainen
    Fusion Applications Developer Relations
    https://blogs.oracle.com/fadevrel/

  • Weblogic.jdbc.extensions.PoolLimitSQLException

    Hi,
    I am using JDeveloper 11.1.2.4 in this case. Basically I am testing my application by deleting part of the URL of my application for example, if I have:
    http://localhost:7103/myApp/faces/pages/myPage.jsf?_afrLoop=714583137314224…
    I will delete everything after the question mark;
    http://localhost:7103/myApp/faces/pages/myPage.jsf
    So I can restart the application. The issue is that after several attempts, I get
    weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool myDB to allocate to applications, please increase the size of the pool and retry..
    I know I could rise the pool size but is there anything I can do to get rid of this problem in a best practice way?
    Regards

    If you wait long enough the problem will solve itself. The problem is that if you start a new session without to close (invalidate) the old one, the resources remain active until they get collected during the session timeout in conjunction with the pooling parameters set for your application module.
    You can tweak the framework to minimize the effect. For this you minimize the time the resource are hold, by tweaking the pooling parameters in correlation with the session timeout.
    One thing you can do it to configure the application module to return the jdbc connection to the pool directly after the request is finished. This means the connection has to be set up for each request when it's checked out from the pool. On the other side the connection isn't attached to the application module until the application module is 'garbage collected' (which takes some time). For this you can set the 'Release Application Module upon release' to true (set the mark in the checkbox in the configuration of the application module. Then you should read the docs about the other pooling parameters and set them to values which suit your application (sorry there is no set of values which works for all applications).
    Use the controlling dashboard (http://server:port/console/dashboard) from the admin console and check the connection and application modules.
    Some links for more info: http://www.jobinesh.com/2013/06/did-you-notice-new-am-configuration.html
    http://andrejusb.blogspot.de/2011/10/experimenting-with-adf-bc-application.html
    Timo

  • Re:The database conectivity

    Hi,
    We are running out of database connections even though we have configured 150 as max connectivity in the connection pool and we have 65 sessions in the database where the limit is 500 sessions. Even though we restarted the weblogic server, the sessions were hanging out in the database
    But we should not get the max capacity of connection pool as we have another 85 connections available. When we killed the session in the database and restarted the weblogic servers that cleared the problem. I am getting the following errors before we killed the sessions
    nstances instead of "5".>
    !!! WeblogicContext.getConnetion() Exception: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool kdbDS to allocate to applications, please increase the size of the pool and retry..
    <Sep 1, 2010 6:56:33 PM EDT> <Info> <Common> <BEA-000627> <Reached maximum capacity of pool "kdbDS", making "0" new resource instances instead of "5".>
    <Sep 1, 2010 6:56:33 PM EDT> <Info> <Common> <BEA-000627> <Reached maximum capacity of pool "kdbDS", making "0" new resource instances instead of "5".>
    !!! WeblogicContext.getConnetion() Exception: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool kdbDS to allocate to applications, please increase the size of the pool and retry..
    !!! WeblogicContext.getConnetion() Exception: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool kdbDS to allocate to applications, please increase the size of the pool and retry..
    !!! WeblogicContext.getConnetion() Exception: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool kdbDS to allocate to applications, please increase the size of the pool and retry..
    !!! WeblogicContext.getConnetion() Exception: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool kdbDS to allocate to applications, please increase the size of the pool and retry..

    We use weblogic server 9.2,
    <name>kdbDS</name>
    <jdbc-driver-params>
    <url>jdbc:oracle:thin:@kdbdbp:1589:bhjakg</url>
    <driver-name>oracle.jdbc.driver.OracleDriver</driver-name>
    <properties>
    <property>
    <name>user</name>
    <value>kdbusr</value>
    </property>
    </properties>
    <password-encrypted>{3DES}mJTVRAnenHo=</password-encrypted>
    </jdbc-driver-params>
    <jdbc-connection-pool-params>
    <initial-capacity>10</initial-capacity>
    <max-capacity>150</max-capacity>
    <capacity-increment>5</capacity-increment>
    <shrink-frequency-seconds>300</shrink-frequency-seconds>
    <connection-creation-retry-frequency-seconds>300</connection-creation-retry-frequency-seconds>
    <test-connections-on-reserve>true</test-connections-on-reserve>
    <inactive-connection-timeout-seconds>86400</inactive-connection-timeout-seconds>
    <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
    <remove-infected-connections>false</remove-infected-connections>
    <profile-type>5</profile-type>
    </jdbc-connection-pool-params>
    <jdbc-data-source-params>
    <row-prefetch>true</row-prefetch>
    <global-transactions-protocol>OnePhaseCommit</global-transactions-protocol>
    </jdbc-data-source-params>
    </jdbc-data-source>
    <Sep 1, 2010 6:34:13 PM EDT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '45' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "314" seconds working on the request "Http Request: /KDB/jsp/appointment/AppointmentList.jsp", which is more than the configured time (StuckThreadMaxTime) of "300" seconds. Stack trace:
    java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:99)
    java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:393)
    java.lang.StringBuilder.append(StringBuilder.java:120)
    java.lang.StackTraceElement.toString(StackTraceElement.java:157)
    java.lang.String.valueOf(String.java:2615)
    java.lang.StringBuilder.append(StringBuilder.java:116)
    java.lang.Throwable.printStackTrace(Throwable.java:465)
    weblogic.utils.StackTraceUtilsClient.throwable2StackTrace(StackTraceUtilsClient.java:27)
    weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:293)
    weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:306)
    weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:284)
    weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:466)
    weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:357)
    weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:83)
    weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:96)
    weblogic.jdbc.pool.Driver.connect(Driver.java:150)
    weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:647)
    weblogic.jdbc.jts.Driver.connect(Driver.java:137)
    weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
    com.cvc.kdb.appcontext.WeblogicContext.getConnection(WeblogicContext.java:340)
    com.cvc.kdb.appcontext.AppContext.getConnection(AppContext.java:287)
    com.cvc.kdb.model.user.UserManager.isUserInDB(UserManager.java:43)
    com.cvc.kdb.model.user.UserManager.getTimeUpdatedMD(UserManager.java:287)
    com.cvc.kdb.model.user.UserManagerWrapper.getTimeUpdatedMD(UserManagerWrapper.java:32)
    sun.reflect.GeneratedMethodAccessor187.invoke(Unknown Source)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    java.lang.reflect.Method.invoke(Method.java:585)
    org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:267)
    org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:197)
    org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
    org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
    org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55)
    org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:70)
    org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
    org.apache.velocity.app.Velocity.evaluate(Velocity.java:316)
    org.apache.velocity.app.Velocity.evaluate(Velocity.java:210)
    com.cvc.kdb.servlet.dynamiccontent.GenericDynamicContentManager.proceedWithVelocityContext(GenericDynamicContentManager.java:209)
    com.cvc.kdb.servlet.dynamiccontent.MDRightSectionTemplateManager.getDynamicContent(MDRightSectionTemplateManager.java:52)
    com.cvc.kdb.model.user.UserManager.displayRightSideMD(UserManager.java:403)
    jsp_servlet._jsp._cda._includes.__rightsideincludecc._jspService(__rightsideincludecc.java:265)
    weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    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.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:530)
    weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:459)
    weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:159)
    jsp_servlet._jsp._cda._includes.__rightsideinclude._jspService(__rightsideinclude.java:138)
    weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    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.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:530)
    weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:459)
    weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:159)
    jsp_servlet._jsp._appointment.__appointmentlist._jspService(__appointmentlist.java:682)
    weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    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.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:530)
    weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
    com.cvc.kdb.servlet.appointment.AppointmentsController.doPost(AppointmentsController.java:112)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    com.cvc.kdb.filter.CookieFilter.doFilter(CookieFilter.java:73)
    weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3242)
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
    weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
    weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
    weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

  • Pool limit Exception

    Hi All,
    I am facing the below issue:
    Caused by: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool EMRepos to allocate to applications, please increase the size of the pool and retry..
    In the AM I have doAmPooling = false.
    Due to above I need to Shutdown the weblogic everytime and start and deploy the application again.
    Any other settings that might help.

    Abhilash,
    Your question isn't very clear, but perhaps reading [url http://download.oracle.com/docs/cd/E17904_01/web.1111/b31974/bcampool.htm#sm0299]this part of the documentation will be useful for you.
    John

Maybe you are looking for

  • MBAM web site configuration failure

    I've set up MBAM 2.5 on my ConfigMgr 2012 server. Its integrated with Configuration Manager and created the two data bases on the same box with Windows Server 2012 R2 and SQL 2012 with reporting services. (I've configured a working OSD windows 7 task

  • Unable to export from the node.

    I need to export from a node in directory server. This node contain more than 1 million user. I am unable to export the node. I have tried running ldap search on the node but i only git the node ldif and then ldapserach hangs. From start console also

  • Upgraded to SL - can't print to PDF

    2 weeks ago, I upgraded from Leopard to SL. I have Acrobat Pro 9 installed. Prior to the upgrade, I could print a Keynote presentation to the Acrobat printer with several nice features over the the Keynote "Share" option. Since upgrading to SL, I can

  • Add Field - Configuration Manager

    Hi all, I add a field to the checkin menu with Configuration Manager. My name field is Local. Then I tried to override this field but instead of it the Content Server add a new field to the checkin menu with the same name: <@dynamichtml std_document_

  • Need expert help - iPod Classics will not play recently downloaded songs

    Sparknotes version of this question, so you don't need waste your time if you aren't interested: -iPod Classic skipping over songs -problem with iTunes transferring the files -need help ASAP, we DJ with these iPods most weekends Multiple iPod Classic