|
Home > Archive > WebLogic installation support > January 2005 > connection pool fails on 6.1
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
connection pool fails on 6.1
|
|
| Chakri Kommana 2004-11-11, 5:50 pm |
| 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.
<Error> <COMM_SERVER_FRAMEWORK> <NEWY123> <NEWY123S1> <ExecuteThread: '44' for queue: 'default'> <> <> <000000> <FlowManager.service ERROR: >
FlowException: com.beasys.comm.foundation.flow.FlowException: com.beasys.comm.portal.PortalException: PortalException - java.sql.SQLException: Error accessing jdbc driver: driverURL = jdbc:weblogic:pool:commPool, props = {connectionPoolID=commPool, enable
TwoPhaseCommit=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(OciConnection.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.makeResources(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.reserveWaitSecs(ResourceAllocator.java:395)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(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.getConnection(RmiDataSource.java:235)
at com.beasys.comm.util.JdbcHelper.getConnection(JdbcHelper.java:182)
at com.beasys.comm.axiom.util.weblogic.helper.WebLogicHelper.getJtsConnection(WebLogicHelper.java:503)
at com.beasys.comm.axiom.util.weblogic.helper.WebLogicHelper.getConnection(WebLogicHelper.java:422)
at com.beasys.comm.portal.ejb.FastPortalManager.getConnection(FastPortalManager.java:596)
at com.beasys.comm.portal.ejb.FastPortalManager.getPortalFor(FastPortalManager.java:715)
at com.beasys.comm.portal.ejb.PortalManagerBean.fastGetPortalFor(PortalManagerBean.java:3490)
at com.beasys.comm.portal.ejb.PortalManagerBean_utvypc_EOImpl. fastGetPortalFor(PortalManagerBean_utvyp
c_EOImpl.java:2109)
at com.beasys.comm.portal.flow.PortalDestinationDeterminer. getPortalDefinition(PortalDestinationDet
erminer.java:196)
at com.beasys.comm.portal.flow.PortalDestinationDeterminer.init(PortalDestinationDeterminer.java:112)
at com.beasys.comm.foundation.flow.jsp.DefaultDestinationDeterminer. determineDestination(DefaultDestinationD
eterminer.java:960)
at com.beasys.comm.foundation.flow.FlowManager.service(FlowManager.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:284)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:119)
at jsp_compiled.__index._jspService(__index.java:97)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:321)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2678)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2412)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:140)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:121)
| |
| Akilah McIntyre 2005-01-10, 5:55 pm |
| 1) [url=http://commerce.bea.com/showproduct.jsp?family=WLP&major=8.1&minor=4]http://commerce.bea.com/showproduct.jsp?family=WLP&major=8.1&minor=4[/url]
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.
[url=http://dev2dev.bea.com/codelibrary/code/examples_jdbc.jsp]http://dev2dev.bea.com/codelibrary/code/examples_jdbc.jsp[/url]
| |
| Anders Mathisen 2005-01-11, 7:50 am |
| 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.
|
|
|
|
|