connection pool fails on 6.1 - Weblogic

This is a discussion on connection pool fails on 6.1 - Weblogic ; I have a connection pool set up with Initial Capacity : 5, increment by 5 and max 100. The application suddenly stops working as the connection reach 95+ connections and thows below exceptions in the logs of the managed node. ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: connection pool fails on 6.1

  1. connection pool fails on 6.1

    I have a connection pool set up with Initial Capacity : 5, increment by 5 and max 100.

    The application suddenly stops working as the connection reach 95+ connections and thows below exceptions in the logs of the managed node.

    when I restart the Manged node throws the same exception, BUT WHEN I RESET (take of the target and retarget) THE CONNECTION POOL FROM THE CONSOLE AND RESTART THE MANAGED NODE IT WORKS.

    <> <> <000000>
    FlowException: com.beasys.comm.foundation.flow.FlowException: com.beasys.comm.portal.PortalException: PortalException - java.sql.SQLException: Error accessing jdbc driver: driverURL = jdbc:weblogicool:commPool, props = {connectionPoolID=commPool, enableTwoPhaseCommit=false}.
    Nested Exception: java.sql.SQLException: Pool connect failed: weblogic.common.ConnectDeadException: failed to make new pool connection: java.sql.SQLException: ORA-24327: need explicit attach before authenticating a user - (zz1111/********@XYZPROD)
    at weblogic.db.oci.OciConnection.getLDAException(OciC onnection.java:164)
    at weblogic.jdbc.oci.Driver.connect(Driver.java:118)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory .makeConnection(ConnectionEnvFactory.java:208)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory .createResource(ConnectionEnvFactory.java:146)
    at weblogic.common.internal.ResourceAllocator.makeRes ources(ResourceAllocator.java:716)
    at weblogic.common.internal.ResourceAllocator.reserve (ResourceAllocator.java:523)
    at weblogic.common.internal.ResourceAllocator.reserve (ResourceAllocator.java:405)
    at weblogic.common.internal.ResourceAllocator.reserve WaitSecs(ResourceAllocator.java:395)
    at weblogic.jdbc.common.internal.ConnectionPool.reser ve(ConnectionPool.java:163)
    at weblogic.jdbc.common.internal.ConnectionPool.reser veWaitSecs(ConnectionPool.java:117)
    at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
    at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver .java:319)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
    at weblogic.jdbc.common.internal.RmiDataSource.getCon nection(RmiDataSource.java:235)
    at com.beasys.comm.util.JdbcHelper.getConnection(Jdbc Helper.java:182)
    at com.beasys.comm.axiom.util.weblogic.helper.WebLogi cHelper.getJtsConnection(WebLogicHelper.java:503)
    at com.beasys.comm.axiom.util.weblogic.helper.WebLogi cHelper.getConnection(WebLogicHelper.java:422)
    at com.beasys.comm.portal.ejb.FastPortalManager.getCo nnection(FastPortalManager.java:596)
    at com.beasys.comm.portal.ejb.FastPortalManager.getPo rtalFor(FastPortalManager.java:715)
    at com.beasys.comm.portal.ejb.PortalManagerBean.fastG etPortalFor(PortalManagerBean.java:3490)
    at com.beasys.comm.portal.ejb.PortalManagerBean_utvyp c_EOImpl.fastGetPortalFor(PortalManagerBean_utvypc _EOImpl.java:2109)
    at com.beasys.comm.portal.flow.PortalDestinationDeter miner.getPortalDefinition(PortalDestinationDetermi ner.java:196)
    at com.beasys.comm.portal.flow.PortalDestinationDeter miner.init(PortalDestinationDeterminer.java:112)
    at com.beasys.comm.foundation.flow.jsp.DefaultDestina tionDeterminer.determineDestination(DefaultDestina tionDeterminer.java:960)
    at com.beasys.comm.foundation.flow.FlowManager.servic e(FlowManager.java:641)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeSe rvlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeSe rvlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.RequestDispatcherImpl.fo rward(RequestDispatcherImpl.java:284)
    at weblogic.servlet.jsp.PageContextImpl.forward(PageC ontextImpl.java:119)
    at jsp_compiled.__index._jspService(__index.java:97)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java: 27)
    at weblogic.servlet.internal.ServletStubImpl.invokeSe rvlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeSe rvlet(ServletStubImpl.java:321)
    at weblogic.servlet.internal.ServletStubImpl.invokeSe rvlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.inv okeServlet(WebAppServletContext.java:2678)
    at weblogic.servlet.internal.ServletRequestImpl.execu te(ServletRequestImpl.java:2412)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThrea d.java:140)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.ja va:121)

  2. Re: connection pool fails on 6.1

    1) http://commerce.bea.com/showproduct....or=8.1&minor=4

    2)Make sure you add your JDBC drivers to the beginning of CLASSPATH in either setDomainenv.cmd or setEnv.cmd

    3)What really helped was BEA support and playing with BEA's JDBC example that shows how to create and deploy and use a data source.

    http://dev2dev.bea.com/codelibrary/c...mples_jdbc.jsp

  3. Re: connection pool fails on 6.1

    Hi,

    it would seem to me that your RDBMS is hitting some upper treshold of the number of users here.

    Try to figure out of wether there are some limitations like this.

    BTW : 100 connections are quite a lot.

    - Anders M.

+ Reply to Thread