Running out of connections...

 

Hello,
I think I'm having the same problem ..
Did you solve it ? How ?
Thanks a lot.
Franco
Francesco Costa
BEA Systems Italia
[email protected]
Phone +39 02 3327 3000
Mobile + 39 335 1246931
Fax +39 02 3327 3001
"Gerhard Henning" <[email protected]> ha scritto nel messaggio
news:[email protected]...
>
Hi,
we seem to have a similar problem. Can you please tell me,
which service pack solves the problem.
We are using SP8 but the problem seems to be still there!
Thanks
Gerhard
Joseph Weinstein <[email protected]> wrote:
Gene Chuang wrote:
Hi Joe,
Good news; bug ISOLATED and FIXED! First off, I was able to determinethis bug only manifests if
we are running clustered apps. under a single app server, this bugdoes not appear, and under
clustered app this bug always appears.
Furthermore, I appologize if I may have lead you on a wild goosechasewith all the subsequent
patches you sent me. As it turns out, when I received each patch Ihanded it off to our tester, who
applied the patch and probably only bounced a node in our server
cluster
before testing, hence
getting negative results. Today I applied your latest patch,
clean-bounced
all the nodes, and the
bug disappeared! Thanks Joe!
Now the 2 questions of the day:
1) Is your latest patch production worthy? Can I apply it on ourlive site?
Yes.
2) If not, when's the next service pack coming out with this fix?It will be in future service packs.
Joe
Gene
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
>>>>
>>>>
Gene Chuang wrote:
Hi Joe,
We tried it and found the same exception raised, except for this
time it took a lot longer to
bug
out; the server hung for almost 2 minutes before dumping the
following.
However I was just
informed by another developer that we may have a recursive bugon our side, and that we are
doing a
non-terminating db search. Perhaps this is causing this
out-of-resource
allocation bug, i.e.
our
bug exposed your bug! I'm sure once we fix our recursion bug we
won't see this again, but maybe
something should also be done on your side that'll handle thismore gracefully...
I'll let you know what happens once we fix our bug; thanks forthe help!
DO let me know. In fact, please use the attached jar (in place ofall the others:-)
because the line ResourceAllocator.java:561 is not executable code.There may be a
JVM problem... I'm fairly sure there's no way our code can causean NPE in this
area...
Joe
javax.ejb.FinderException: Couldn't build CallableStatement from
JDBCCommandImpl:
java.sql.SQLException: Exception raised by connection pool
:java.lang.NullPointerException
atweblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:56
1)
atweblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:55
5)
atweblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:50
2)
atweblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:172
atweblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.
java:145)
atweblogic.jdbcbase.jts.Connection.openConnectionIfNecessary(Connection.java:5
87)
atweblogic.jdbcbase.jts.Connection.prepareCall(Connection.java:159)
atweblogic.jdbc20.rmi.internal.ConnectionImpl.prepareCall(ConnectionImpl.java:
89)
atweblogic.jdbc20.rmi.SerialConnection.prepareCall(SerialConnection.java:71)
atcom.kiko.db.JDBCConnection.getCallableStatement(JDBCConnection.java:158)
>>>>>
Gene Chuang
Join Kiko.com!
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
>>>>>>
>>>>>>
Gene Chuang wrote:
Hi Joe,
We were finally able to consistently replicate the
ResourceAllocator.reserve()
stacktrace,
although
from a slightly different route. I tried your jar, and now
have a slightly different
exception:
Hi Gene. Thank you for your patience. Here's one last jar file.
Ditch the previous one. I appreciate your energy and willingness
to help. Let me know,
Joe
javax.ejb.EJBException: Failed to select row 0: Exception
raised
by connection pool
:java.lang.NullPointerException
at
weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:56
1)
atweblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:55
5)
atweblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:50
2)
atweblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:172
atweblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.
java:145)
atweblogic.jdbcbase.jts.Connection.openConnectionIfNecessary(Connection.java:5
87)
atweblogic.jdbcbase.jts.Connection.prepareStatement(Connection.java:135)
atweblogic.jdbc20.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.
java:80)
atweblogic.jdbc20.rmi.SerialConnection.prepareStatement(SerialConnection.java:
55)
atcom.kiko.db.JDBCConnection.getPreparedStatement(JDBCConnection.java:141)
>>>>>>>
Gene Chuang
Join Kiko.com!
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
Hi Gene.
Would you put the attached jar to the head of your
weblogic.classpath,
and let me know if this fixes the problem? thanks,
Joe
Gene Chuang wrote:
WL 5.1 sp 6, running on Solaris 2.7 over Oracle 8i
Gene Chuang
Join Kiko.com!
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
Gene Chuang wrote:
Hi Joe,
Now I'm getting this slightly different stack trace...
do u think it's the same
"out of
connection"
error, or something else?It's something else. What version of the product is this?
Joe
Couldn't build PreparedStatement from JDBCCommandImpl:
java.sql.SQLException:
Exception
raised
by
connection pool :java.lang.NullPointerException
at
weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:56
1)
atweblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:55
5)
atweblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:50
2)
atweblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:172
atweblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.
java:145)
atweblogic.jdbcbase.jts.Connection.openConnectionIfNecessary(Connection.java:5
87)
atweblogic.jdbcbase.jts.Connection.prepareStatement(Connection.java:135)
atweblogic.jdbc20.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.
java:80)
atweblogic.jdbc20.rmi.SerialConnection.prepareStatement(SerialConnection.java:
55)
>>>>>>>>>>>
Gene Chuang
Join Kiko.com!
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
Hi.
The server won't let an EJB wait indefinitely for
a connection to become
available in a pool. All the while it waits, it iscommandeering one
of the fixed number of execute-threads, doing nothingwhile the thread
could possibly run another task which already hasit's pool connection,
and could release it if it ran. The default waitallowed is 5 seconds
the server decides to devote it's resources to thework it can do, and
not let overflow requests cause an unintentionalor malicious denial-
of-service attack. The fundamental solution is tosupply enough DBMS
connections to serve the load you have.
Joe
Gene Chuang wrote:
Hi,
Here's our pool init info:
weblogic.jdbc.connectionPool.oraclePool=\
driver=oracle.jdbc.driver.OracleDriver,\
url=jdbc:oracle:oci8:@xxx,\
loginDelaySecs=0,\
initialCapacity=4,\
maxCapacity=10,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=xxx;password=xxxx;server=xxx
I run a db-intensive data migration program on
my ejbs (hence JDBC connection
requests
are
made
on
the serverside). After a while, I run out of
connections,
and the exception
pasted
below is
thrown.
Why is this exception thrown? If the pool is at
maxCapacity and all connections
are
taken,
shouldn't weblogic place the connection-requestor
on wait until a connection is
available?
And
I'm
pretty sure I return the connections because I
wrap connection.close() on a
finally
block...
JDBCPoolConnection.connect: Problem connecting
Exception:
java.sql.SQLException: Pool connect failed: Noneavailable
java.sql.SQLException: Pool connect failed: Noneavailable
at
weblogic.jdbcbase.pool.Driver.connect(Driver.java:184)
atweblogic.jdbcbase.jts.Driver.connect(Driver.java:233)
at
weblogic.jdbc20.common.internal.RmiDataSource.getConnection(RmiDataSourc
e.java:55)
at
weblogic.jdbc20.common.internal.RmiDataSource_ServiceStub.getConnection(
RmiDataSource_ServiceStub.java:179)
at
com.kiko.db.JDBCPoolConnection.connect(JDBCPoolConnection.java:24)ABMEB.
ejbActivate: Getting bean out of pooled state.
Gene Chuang
Join Kiko.com!--
PS: Folks: BEA WebLogic is in S.F. with both entryand advanced positions for
people who want to work with Java and E-Commerceinfrastructure products. Send
resumes to [email protected]
The Weblogic Application Serverfrom BEA
JavaWorld Editor's Choice Award: Best WebApplication Server
Java Developer's Journal Editor's Choice Award:Best Web Application Server
Crossroads A-List Award: Rapid Application
Development
Tools for Java
Intelligent Enterprise RealWare: Best ApplicationUsing a Component Architecture
>
http://www.bea.com/press/awards_weblogic.html
>>>>>>>>>>
PS: Folks: BEA WebLogic is in S.F. with both entry andadvanced positions for
people who want to work with Java and E-Commerce
infrastructure
products. Send
resumes to [email protected]
The Weblogic Application Server fromBEA
JavaWorld Editor's Choice Award: Best Web
Application
Server
Java Developer's Journal Editor's Choice Award: BestWeb Application Server
Crossroads A-List Award: Rapid Application
Development
Tools for Java
Intelligent Enterprise RealWare: Best Application Usinga Component Architecture
>
http://www.bea.com/press/awards_weblogic.html
>>>>>>>>
PS: Folks: BEA WebLogic is in S.F. with both entry andadvanced
positions for
people who want to work with Java and E-Commerce
infrastructure
products. Send
resumes to [email protected]
The Weblogic Application Server fromBEA
JavaWorld Editor's Choice Award: Best Web
Application
Server
Java Developer's Journal Editor's Choice Award: Best WebApplication Server
Crossroads A-List Award: Rapid Application DevelopmentTools for Java
Intelligent Enterprise RealWare: Best Application Using aComponent Architecture
>
http://www.bea.com/press/awards_weblogic.html
>>>>>>
PS: Folks: BEA WebLogic is in S.F. with both entry and advancedpositions for
people who want to work with Java, XML, SOAP and E-Commerce
infrastructure
products. Send resumes to [email protected]
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web ApplicationServer
Java Developer's Journal Editor's Choice Award: Best Web
Application
Server
Crossroads A-List Award: Rapid Application Development Toolsfor Java
Intelligent Enterprise RealWare: Best Application Using a
Component
Architecture
http://www.bea.com/press/awards_weblogic.html--
PS: Folks: BEA WebLogic is in S.F. with both entry and advanced
positions
for
people who want to work with Java, XML, SOAP and E-Commerce
infrastructure
products. Send resumes to [email protected]
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best WebApplication
Server
Crossroads A-List Award: Rapid Application Development Toolsfor Java
Intelligent Enterprise RealWare: Best Application Using a ComponentArchitecture
http://www.bea.com/press/awards_weblogic.html--
PS: Folks: BEA WebLogic is in S.F. with both entry and advanced positions
for
people who want to work with Java, XML, SOAP and E-Commerceinfrastructure
products. Send resumes to [email protected]
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web Application
Server
Crossroads A-List Award: Rapid Application Development Tools for
Java
Intelligent Enterprise RealWare: Best Application Using a ComponentArchitecture
http://www.bea.com/press/awards_weblogic.html

Similar Messages

  • Connection leaks and application is running out of connection

    Hi All,
    We have configured the SQL Database external resource for OBPM specific connection pool. All the business processes are using the Fuego.Sql package for the data base transaction calls. I have no clue how this package is managing the database connections. If more than 25 users perform concurrent testing, the application is running out of connections. Connection pool configuration details as below.
    Maximum Pool Size : 500
    Maximum connections per user : 50
    Minimun Pool Size : 0
    Connection Idle Time (mins). : 5
    Maximum Opened Cursors : 1000
    Please share your thoughts on how I can track and fix this issue. Also please let me know the answers below.
    1. Is there any way to find out the stats about the connection pool
    2. If I configure the remote JDBC that points to J2EE datasource, would that fix this issue.
    I appreciate your help.
    Thanks,

    Can anyone please share your ideas?
    Thanks,

  • ConnectionPoolDataSource - running out of Connections..

    Hi
    I have a same problem as described in this thread
    http://forum.java.sun.com/thread.jsp?forum=136&thread=560645&tstart=0&trange=15
    I have Q42004 Beta J2EE SDK, and am using MS SQL 2000 databse server with jTDS 0.9 (jtds.sourceforge.net) JDBC driver...
    I have a very simple servlet that gets a DataSource from the JNDI, gets connection , does some stuff, closes connection....Pretty basic....After a while I get the following error
    [#|2004-10-08T19:19:08.053-0400|INFO|sun-appserver-pe8.1|javax.enterprise.system.stream.out|_ThreadID=28;|
    [2004-10-08 19:19:08,053] [ERROR] [org.nemours.webapps.coi.COIServlet]
    [MSG] java.sql.SQLException: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired  max-wait-time. Cannot allocate more connections.
            at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:74)
            at org.nemours.webapps.coi.COIServlet.getDBConnection(Unknown Source)
            at org.nemours.webapps.coi.COIServlet.doProcess(Unknown Source)
            at org.nemours.webapps.coi.COIServlet.doPost(Unknown Source)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
            at sun.reflect.GeneratedMethodAccessor248.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:324)
            at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
            at java.security.AccessController.doPrivileged(Native Method)
            at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
            at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:273)
            at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
            at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
            at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
            at java.security.AccessController.doPrivileged(Native Method)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:262)
            at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
            at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
            at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
            at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
            at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
            at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
            at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
            at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:618)
            at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:500)
            at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doTask(ProcessorTask.java:375)
            at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:55)
    Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot alloca
    te more connections.
    |#]the configuration of the pool in my domain.xml is as follwing...
    <jdbc-resource enabled="true" jndi-name="jdbc/coiDB" object-type="user" pool-name="coi_Pool"/>
        <jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="net.sourceforge.jtds.jdbcx.JtdsConnectionPoolDataSource" fail-all-connections="true" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="coi_Pool" pool-resize-quantity="2" res-type="javax.sql.ConnectionPoolDataSource" steady-pool-size="8">
          <description>jTDS 0.9 Type 4 JDBC Driver</description>
          <property name="DatabaseName" value="coi"/>
          <property name="Password" value="******"/>
          <property name="User" value="*******"/>
          <property name="ServerName" value="localhost"/>
        </jdbc-connection-pool>
    ...After few WAR redeployments I run out of connections....I have noticed also the following:
    1. On MS SQL Enterprise Manager - Management console there are no processes/locks associated with jTDS meaning there are no outstanding connection when I get an error...
    2. After a restart of MSSQL services i still get an error
    3. After an application redeployment I still get an error
    4. After a domain restart the error goes away untill i redeploy the app several times....
    Can someone PLEASE let me know if this is a bug in Q42004 or am I doing something bad...
    I spent hours debugging the code trying to figure this one out....
    Thanks
    Z

    Hi
    jTDS 0.9 does not have XADataSource implementation but it has DataSource implementation.
    If I use the DataSource imlementation I still get the "out of connections" problem....
    This same application did not exibit any problems on Updte 1.
    The code of my servlet is pretty big but here are the relevant snippets:
         private Connection getDBConnection() {
              DataSource ds = null;
              Connection conn = null;
              try {
                   Log.info(this.getClass(), "Attempting to use ServiceLocator to get DS from JNDI...");
                   ds = ServiceLocator.getInstance().getDataSource("jdbc/coiDB");
                   Log.info(this.getClass(), "Attempting to get connection...");
                  conn = ds.getConnection();
              } catch (Exception e) {
                   Log.error(this.getClass(),"failure...!");
                   Log.exception(this.getClass(), e);
              return conn;
         private Employee getEmployee(int empID) {
              Employee existingEmp = null;
              PreparedStatement pstmt = null;
              ResultSet rset = null;
              Connection conn = getDBConnection();
              try {               
                   pstmt = conn.prepareStatement("SELECT * FROM EMPLOYEE WHERE ID = ?");
                   pstmt.setInt(1, empID);
                   rset = pstmt.executeQuery();               
                   if (rset.next()) {
                        existingEmp = new Employee(rset.getInt("id"), rset.getString("fname"), rset.getString("lname"), rset.getString("location"), rset.getString("department"), rset.getString("phone"));
                        existingEmp.setCreateTS(rset.getTimestamp("create_ts"));
              } catch (SQLException e) {
                   Log.error(this.getClass(), "Failed DB operation while checking for existing employee");
                   Log.exception(this.getClass(), e);
              } finally {
                   DBUtils.closeResultSet(rset);
                   DBUtils.closeStatement(pstmt);
                   DBUtils.closeConnection(conn);
              return existingEmp;     
         }The DBUtils I use is just convenience static class that wraps regular JDBC calls into try catch block and ServiceLocator is a BluePrints pattern straight from AdventureBUilder 1.0.1. Employee is a my model/subject class.....
    Thanks
    Z...

  • The connection pool DIMT_DB is running out of connections

    I am facing an issue, the process instances created in activity are not getting routed to my work item. I found the following exception logged in engine DB at the time process instance was created,
    The connection pool DIMT_DB is running out of connections ( 100 % of the pool is in use).
    It is recommendable to expand the size through the Process Administrator.
    can anyone provide me a solution to this issue?
    the maximum pool size is 10. should it be increased?
    does this issue occur when database connection is not closed properly?

    Can anyone please share your ideas?
    Thanks,

  • Re:Running out of connection pools one server

    Hi,
    We are running out of connection pools on one weblogic server only everytime in a 2 node cluster.
    But the sessions are very less in the database when we faced the issue.
    But this doesn't happen all the time it happens once in a month.
    our configuration
    <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>
    <Sep 27, 2010 4:14:11 PM EDT> <Info> <JDBC> <BEA-001128> <Connection for pool "kdbDS" closed.>
    <Sep 27, 2010 4:14:11 PM EDT> <Info> <Common> <BEA-000627> <Reached maximum capacity of pool "kdbDS", making "0" new resource instances instead of "5".>
    2010-09-27 16:14:11,0722, SEVERE: kdb - com.cvc.kdb.appcontext.AppContext(logSevere)DynamicContent: SearchDynamicContentManager.getDynamicContent() evaluating template id=2005
    java.net.SocketException: Broken pipe
    2010-09-27 16:14:11,0724, INFO: kdb - com.cvc.kdb.appcontext.AppContext(logInfo)User session established: nkpLMg7TKQTz3vllmYKKdXyf7lFcLZBvtjnppnJdGQT97TssnLz2!1568862676!1563294179!1285618451720
    <Sep 27, 2010 4:14:11 PM EDT> <Info> <Common> <BEA-000627> <Reached maximum capacity of pool "kdbDS", making "0" new resource instances instead of "5".>
    <Sep 27, 2010 4:14:11 PM EDT> <Info> <Common> <BEA-000627> <Reached maximum capacity of pool "kdbDS", making "0" new resource instances instead of "5".>
    2010-09-27 16:14:11,0725, SEVERE: kdb - com.cvc.kdb.appcontext.AppContext(logSevere) ConceptGuidedSearch.jsp: java.net.SocketException: Broken pipe
    java.net.SocketException: Broken pipe
         at java.net.SocketOutputStream.socketWrite0(Native Method)
         at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
         at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
         at weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:525)
         at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:504)
         at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:382)
         at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:469)
         at weblogic.servlet.internal.ChunkOutput.print(ChunkOutput.java:344)
         at weblogic.servlet.internal.ChunkOutputWrapper.print(ChunkOutputWrapper.java:146)
         at weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:151)
         at weblogic.servlet.jsp.JspWriterImpl.println(JspWriterImpl.java:205)
         at jsp_servlet._jsp._search._cda.__conceptguidedsearch._jspService(__conceptguidedsearch.java:411)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         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:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at com.cvc.kdb.filter.CookieFilter.doFilter(CookieFilter.java:73)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3242)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    <Sep 27, 2010 4:14:11 PM EDT> <Info> <Common> <BEA-000627> <Reached maximum capacity of pool "kdbDS", making "0" new resource instances instead of "5".>
    <Sep 27, 2010 4:14:11 PM EDT> <Info> <JDBC> <BEA-001128> <Connection for pool "kdbDS" closed.>
    <Sep 27, 2010 4:14:11 PM EDT> <Info> <Common> <BEA-000627> <Reached maximum capacity of pool "kdbDS", making "0" new resource instances instead of "5".>
    <Sep 27, 2010 4:14:11 PM EDT> <Notice> <Stdout> <000000> <7808-515177-2>
    <Sep 27, 2010 4:14:11 PM EDT> <Notice> <Stdout> <000000> <1>
    2010-09-27 16:14:11,0732, SEVERE: kdb - com.cvc.kdb.appcontext.AppContext(logSevere)no cookie:

    notoriousdbp wrote:
    You'd still be renting the line too, which is handy because it means BT still own it.
    Well if I have to still pay the line rental, I will take the free number that comes with it.. Thankyou.
    toekneem
    http://www.no2nuisancecalls.net
    (EASBF)

  • Connection pool running out of connections

    Hi all,
    I am using Oracle's connection pool implementation:
    OracleConnectionPoolDataSource dbConnection;
    OracleConnectionCacheImpl connectionPool;
    and tomcat 3 and 4. Sometimes on Tomcat 4 (Linux) I see that the connections are not being reutilized and therefore I run out of free connections. The same application runs fine on NT and Tomcat 3 and 4. I checked all my methods and all have a close(connection) in my finally{} and besides this the problem only happens once in a while and the program is using the same methods all the time. Anybody has a clue about what could the issue be?
    Thanks,
    A.

    have u tried setCacheScheme?

  • Sybase ASE 12.5.4 EBF 14124 ESD#4 running out of connections

    I am working on a web application which works on SQL sever back end as well as Sybase ASE 12.5.4 EA server. Our project main focus was to move everything to sybase backend.
    Earlier there were 2 databases, the app was connecting to - db1 on sql server, and db2 on sybase. Now we have created a separate namespace within db2 in sybase. So application only connects with db2, but with different users and in separate schemas. 
    Application is in java and connecting to db server using jcon3 driver library.  It is using SybXADataSource driver class (provided by jcon3 jar) to connect to the server. Till last week application was able to connect to the server, everything was working fine (though I must say that code is still not optimized to use connection pools etc., I am opening  a connection, and closing it for every request).
    For sometime, I have been facing an issue from the server- login failed, try again. In the server error logs I found it was throwing an error- "Error 1601 Severity 17 state 3: no user connections available to run the process" I checked for available connections (using sp_configure), allowed connections are 900, and total active connection at the time this error shows up is typically between 30- 100 (using sp_monitorconfig). Seems like this is well within limits.
    Also yesterday, I did one more exercise, I restarted the server and logged in as sa from isql console only. Logged out and logged in again afimeter 20 minutes (no application connection was made), and isql login again gave this error. So I am inclined to think that something could be wrong with server configuration as well. Server is on linux red hat.
    I have searched all the db forums and SCN website as well, and all of these refer to one resolution of increasing the number of connections, but as from my observation regarding that, I do not think it is an issue.
    Any help would be greatly appreciated!!

    During your sa/isql test, how did you exit from your sessions?  Did you type 'exit + go', hit ^S, hit ^C, something else?
    Are you running your sa/isql test from the same linux host where the ASE is runing, or from another host on the network?
    Is your isql session connecting directly to the dataserver or are you going through an intermediary service?
    Are there any login triggers on your sa account? (See the output from sp_displaylogin sa)
    Could you run your sa/isql test again, but this time:
    session #1: log in as sa using isql; stay logged in
    session #2: perform your login/logout test using sa + isql
    session #1: periodically run 'sp_who' to see the active connections; does the list of connections grow over time?

  • (solved)MySQL running out of connections...

    Hi,
    Not really a _problem_ as such, but I may have to look into this in the (near?) future, if my project goes live...
    I have an Applet that shows data from a server (on my network) - if I turn off the applet (stop Firefox all the way) and re-connect and do that several times, the server has "too many connections" and (obviously) will refuse to serve any further.
    Is there a way to effectively kill a connection?
    There is (scetchy) what I do at "unload"
    try
    cn.close();
    cn = null;
    catch(exception e)
    // no need to handle this?
    Fair enuff, the Applet does release the connection, but something still "lingers" on in the server...how do I clean that up as well?
    Any thoughts are welcome...no pressure here...
    Coolness to all
    Thor
    Edit - not really solved, but more "timed out"...
    Last edited by Thor@Flanders (2010-12-10 12:43:21)

    Hi Skunktrader,
    Nope, the exception still happens. I'll set up the server to do a garbage collect. And redirect the closing page/applet to a close page where I'd run a PHP script to close mysql down...by means of cleaning up...
    The thing is, if/when I wait a while, the exception does not manifest itself and the applet does start up. As if the server needs time to clean up...something I want to force it doing...right away.
    More to follow
    Thor
    Edit1 : still no luck - of course, the server is a recycled PC (256Mb ram) and CentOS 5.2, still more than 20Gb disk left. But... I am the only one on this thing...
    Any (I really mean ANY) thoughts (no matter how funny or off-topic, I could use SOME feedback here) are more than welcome...
    Edit2 : is it normal that my local JVM just ... stops? I've set the thing to display the console, just to see anything locally getting lost in the fog, but the panel stops, after a "ps -A" there is no more JVM inthe shop...
    I have to restart the applet several times to get it working, of course, every attempt leaves its marks on the server in still-open connections...
    I still invite ANYONE for thoughts, inputs, off-topics, ...
    Last edited by Thor@Flanders (2010-12-05 17:59:40)

  • How do I add to my data plan on the iPad once I have run out of time and no longer have an internet connection?

    How do I add to my data plan on the iPad once I have run out  and no longer have an internet connection? I am working out of the country and got a message that I was running low,followed immediatly by a you're out message.

    Should you not be asking your carrier? They are the people supplying your data plan.

  • How do I find out my MBP's 'server name?' to run Remote Desktop Connection?

    How do I find out my MBP's 'server name?' to run Remote Desktop Connection?

    Hi Dave,
    You need to type the server name that was assigned by your mail administrator for the server running Exchange. So please ask your administrator for the Server name. Thanks for your understanding.
    For more information, here is an article for your reference.
    Add or remove an e-mail account
    https://support.office.com/en-ca/article/Add-or-remove-an-e-mail-account-ff7c7735-6117-4b0d-aef6-8aa8a072f60f
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Running out of data connections

    Problem Statement:
    Running out of data connections after some time and
    the following SQLException is thrown:
    "failed to create a data connection with any of the
    specified drivers"
    Problem Description:
    I have an application that is running under iPlanet
    6.0 on solaris using Oracle 8 and type 2 Oracle
    driver.
    The application is using a number of stateless
    session beans.
    Normally, my servlets instantiate the remote beans in
    order to make access to their interfaces. For
    example, I have a servlet that fetches all of
    the accounts for a given customer. First, The servlet
    does the fetch by calling JNDI to lookup the "home"
    interface, then does a "create" call on the home
    interface to get the "remote" interface
    (see snippets of code below, the ejbCreate()).
    Second, the servlet calls up a specific method that
    extracts the customer's accounts (see snippets of
    code below, the method getAccountList()).
    At first all seem to work well, however after some
    random time my beans start to throw the SQLException
    "failed to create a data connection with any of the
    specified drivers"
    At first I thought that I am not closing the
    connections, but all of of my connections,
    statements, and result sets, are closed
    and even set to null in a finally block as you can
    see in the snippets of code below.
    If I restart iAS, all of the connections get released
    and things look normal again till the problem
    re-occurs.
    Initially, we had this problem on SP2, so we upgraded
    to SP3 thinking that this may solve the problem,
    however the problem remained on SP3.
    Another thing, this same application works perfectly
    well on my laptop which has similar iPlanet
    configurations except that operating system is
    Windows 2000 Advanced Server, and Oracle 8.0.4.0.0.
    System Configuration:
    Following is my system configuration and related
    iPlanet 6.0 settings.
    -1- iPlanet 6.0 SP3
    -2- Type 2 Oracle driver
    -3- SunOs, sparc SUNW, Ultra-250, solaris 5.8
    -4- Oracle 8.1.6.0.0 64-bit Production
    -5- Following are the entry settings in the iPlanet
    registry under
    Software\iPlanet\Application Server\6.0\CCS0\DAE2\ORACLE_OCI
    - CacheCleanInterval = 120
    - CacheConnTimeOut = 120
    - CacheDebugMsgs = 0
    - CacheFreeSlots = 16
    - CacheInitSlots = 64
    - CacheMaxConn = 64
    - CachMaxGlobalConn = 128
    - ConnGiveUpTime = 60
    - RMThreadMax = 32
    - RMThreadMin = 0
    - RSBufferInitRows = 25
    - RSBufferMaxBufferSize = 6553600
    - RSBufferMaxRows = 100
    - RSBufferMaxSize = 32768
    - SQLDebugMsgs = 0
    Snippets of Code:
    The following snippets of code come from a stateless
    session bean and consist of a local data member, the
    ejbCreate() method, and a typical rmi method that
    does the database connection and extraction of
    related records.
    javax.sql.DataSource dataSourceObj = null;
    public void ejbCreate()
    throws java.rmi.RemoteException, javax.ejb.CreateException
    javax.naming.Context ctx = null;
    // Ensure first that the _props have been
    // successfully instantiated by the constructor.
    if (_props != null) {
    try{
    ctx = new javax.naming.InitialContext();
    }catch (Exception ex){           
         nbUtility.logError(ex,"Error while creating Initial Context !");
    try{
    // DEBUG:
    System.out.println("ejbCreate(): NB_DATASOURCE = " + props.getPropertyValue(props.NB_DATASOURCE));
    // DEBUG:
         dataSourceObj = (javax.sql.DataSource) ctx.lookup(_props.getPropertyValue(_props.NB_DATASOURCE));
    catch (Exception ex){
         ex.printStackTrace();
    if (dataSourceObj == null)
    throw new javax.ejb.CreateException("Couldn't get DataSource object from environment");
    } else {
    throw new javax.ejb.CreateException("Couldn't create the property manager: NB_CONFIG_FILE is null, empty, not set, or the file doesn't exist.");
    * Given a customer number, this method
    * returns the list of accounts that belongs to
    * this customers.
    public nbAccountList getAccountList(String CustomerNo)
    throws java.rmi.RemoteException {
    nbAccountList accountList = null;
    if ((CustomerNo != null) && (!CustomerNo.equals(""))) {
    java.sql.Connection conn = null;
    java.sql.Statement stmt = null;
    java.sql.ResultSet rset = null;
    try {
    accountList = new nbAccountList();
    String sql = "SELECT * FROM " +
    props.getPropertyValue(props.NB_DBTABLE_ACCOUNT) +
    " WHERE " +
    "(" + props.getPropertyValue(props.NB_DBFIELD_ACCOUNT_CUSTOMERNO) +
    "='" + CustomerNo + "')";
    // DEBUG:
    nbDebug.write("accounts list SQL= " + sql);
    // DEBUG:
    // Let's get the connection, the statement, and the record set.
    conn = dataSourceObj.getConnection();
    stmt = conn.createStatement();
    rset = stmt.executeQuery(sql);
    // Let's loop for each single account
    int index = 0;
    nbAccount account = null;
    while (rset.next()) {
         String AccountNo = rset.getString(_props.getPropertyValue(_props.NB_DBFIELD_ACCTPERMIS_ACCOUNTNO));
    // Instantiate an account object
    account = new nbAccount(AccountNo);
    index++;
    } catch (SQLException e) {
         nbUtility.logError(e, "SQLException while trying to get accounts data.");
    } finally {
    try {
    if (rset != null) { rset.close(); rset = null; }      
    if (stmt != null) { stmt.close(); stmt = null; }
    if (conn != null) { conn.close(); conn = null; }
    } catch (SQLException e) {
         nbUtility.logError(e, "SQLException while trying to close connection.");
    return (accountList);      
    }

    I've experienced similar problems. Unfortunately, all efforts by iPlanet
    technical support to resolve the issue have failed. (They do keep calling
    and asking if they can close the ticket for some reason)
    One thing that's totally anoying is the ksvradmin monitory crashes when I
    try to have it report any connection pool information. They verified it's a
    bug in SP3 but won't say if it's fixed in SP4 or provide an estimate.
    To date here's what I've tried (by tech support's recomendation):
    1) Configure for global transactions. (even thow I'm not using them)
    (Failed)
    2) Switch to using 3rd party driver (We were previously using native)
    (Failed)
    3) Ran report on oracle showing number of connections used during iplanet's
    failed attempt. Report from Oracle shows 2 connections open, but iPlanet is
    configured for 120.
    4) Increased the connection pool size. (I didn't know why based on the
    above info) (Increased to 300) (Failed)
    Well there's my history. We crash after about 3 days of heavy usage. I'm
    about to give up and just reset my servers each night. Will help me with
    logfile rotation of the kjs files as well.
    Rodger Ball
    Sr. Engineer
    Business Wire
    "Bilal Chouman" <[email protected]> wrote in message
    news:[email protected]...
    Problem Statement:
    Running out of data connections after some time and
    the following SQLException is thrown:
    "failed to create a data connection with any of the
    specified drivers"
    Problem Description:
    I have an application that is running under iPlanet
    6.0 on solaris using Oracle 8 and type 2 Oracle
    driver.
    The application is using a number of stateless
    session beans.
    Normally, my servlets instantiate the remote beans in
    order to make access to their interfaces. For
    example, I have a servlet that fetches all of
    the accounts for a given customer. First, The servlet
    does the fetch by calling JNDI to lookup the "home"
    interface, then does a "create" call on the home
    interface to get the "remote" interface
    (see snippets of code below, the ejbCreate()).
    Second, the servlet calls up a specific method that
    extracts the customer's accounts (see snippets of
    code below, the method getAccountList()).
    At first all seem to work well, however after some
    random time my beans start to throw the SQLException
    "failed to create a data connection with any of the
    specified drivers"
    At first I thought that I am not closing the
    connections, but all of of my connections,
    statements, and result sets, are closed
    and even set to null in a finally block as you can
    see in the snippets of code below.
    If I restart iAS, all of the connections get released
    and things look normal again till the problem
    re-occurs.
    Initially, we had this problem on SP2, so we upgraded
    to SP3 thinking that this may solve the problem,
    however the problem remained on SP3.
    Another thing, this same application works perfectly
    well on my laptop which has similar iPlanet
    configurations except that operating system is
    Windows 2000 Advanced Server, and Oracle 8.0.4.0.0.
    System Configuration:
    Following is my system configuration and related
    iPlanet 6.0 settings.
    -1- iPlanet 6.0 SP3
    -2- Type 2 Oracle driver
    -3- SunOs, sparc SUNW, Ultra-250, solaris 5.8
    -4- Oracle 8.1.6.0.0 64-bit Production
    -5- Following are the entry settings in the iPlanet
    registry under
    Software\iPlanet\Application Server\6.0\CCS0\DAE2\ORACLE_OCI
    - CacheCleanInterval = 120
    - CacheConnTimeOut = 120
    - CacheDebugMsgs = 0
    - CacheFreeSlots = 16
    - CacheInitSlots = 64
    - CacheMaxConn = 64
    - CachMaxGlobalConn = 128
    - ConnGiveUpTime = 60
    - RMThreadMax = 32
    - RMThreadMin = 0
    - RSBufferInitRows = 25
    - RSBufferMaxBufferSize = 6553600
    - RSBufferMaxRows = 100
    - RSBufferMaxSize = 32768
    - SQLDebugMsgs = 0
    Snippets of Code:
    The following snippets of code come from a stateless
    session bean and consist of a local data member, the
    ejbCreate() method, and a typical rmi method that
    does the database connection and extraction of
    related records.
    javax.sql.DataSource dataSourceObj = null;
    public void ejbCreate()
    throws java.rmi.RemoteException, javax.ejb.CreateException
    javax.naming.Context ctx = null;
    // Ensure first that the _props have been
    // successfully instantiated by the constructor.
    if (_props != null) {
    try{
    ctx = new javax.naming.InitialContext();
    }catch (Exception ex){
    nbUtility.logError(ex,"Error while creating Initial Context
    try{
    // DEBUG:
    System.out.println("ejbCreate(): NB_DATASOURCE = " +
    props.getPropertyValue(props.NB_DATASOURCE));
    // DEBUG:
    dataSourceObj = (javax.sql.DataSource)
    ctx.lookup(_props.getPropertyValue(_props.NB_DATASOURCE));
    catch (Exception ex){
    ex.printStackTrace();
    if (dataSourceObj == null)
    throw new javax.ejb.CreateException("Couldn't get DataSource
    object from environment");
    } else {
    throw new javax.ejb.CreateException("Couldn't create the
    property manager: NB_CONFIG_FILE is null, empty, not set, or thefile
    doesn't exist.");
    * Given a customer number, this method
    * returns the list of accounts that belongs to
    * this customers.
    public nbAccountList getAccountList(String CustomerNo)
    throws java.rmi.RemoteException {
    nbAccountList accountList = null;
    if ((CustomerNo != null) && (!CustomerNo.equals(""))) {
    java.sql.Connection conn = null;
    java.sql.Statement stmt = null;
    java.sql.ResultSet rset = null;
    try {
    accountList = new nbAccountList();
    String sql = "SELECT * FROM " +
    props.getPropertyValue(props.NB_DBTABLE_ACCOUNT)
    +
    " WHERE " +
    "(" +
    props.getPropertyValue(props.NB_DBFIELD_ACCOUNT_CUSTOMERNO) +
    "='" + CustomerNo + "')";
    // DEBUG:
    nbDebug.write("accounts list SQL= " + sql);
    // DEBUG:
    // Let's get the connection, the statement, and the record
    set.
    conn = dataSourceObj.getConnection();
    stmt = conn.createStatement();
    rset = stmt.executeQuery(sql);
    // Let's loop for each single account
    int index = 0;
    nbAccount account = null;
    while (rset.next()) {
    String AccountNo =
    rset.getString(_props.getPropertyValue(_props.NB_DBFIELD_ACCTPERMIS_ACCOUNTN
    O));
    >
    // Instantiate an account object
    account = new nbAccount(AccountNo);
    index++;
    } catch (SQLException e) {
    nbUtility.logError(e, "SQLException while trying to get
    accounts data.");
    } finally {
    try {
    if (rset != null) { rset.close(); rset = null; }
    if (stmt != null) { stmt.close(); stmt = null; }
    if (conn != null) { conn.close(); conn = null; }
    } catch (SQLException e) {
    nbUtility.logError(e, "SQLException while trying to close
    connection.");
    return (accountList);
    Try our New Web Based Forum at http://softwareforum.sun.com
    Includes Access to our Product Knowledge Base!

  • Hey my iPod is not showing up on iTunes and my computer doesn't recognize it. It runs out of battery very fast and only shows the 'Connect to iTunes" screen. What do I do?

    Hey my iPod is not showing up on iTunes and my computer doesn't recognize it. It runs out of battery very fast and only shows the 'Connect to iTunes" screen. What do I do?

    http://support.apple.com/kb/ht1808
    http://support.apple.com/kb/ts1567
    Basic troubleshooting steps  
    17" 2.2GHz i7 Quad-Core MacBook Pro  8G RAM  750G HD + OCZ Vertex 3 SSD Boot HD 
    Got problems with your Apple iDevice-like iPhone, iPad or iPod touch? Try Troubleshooting 101

  • I am trying to download photos off my IPhone as the "Cloud" tells me I have run out of storage space. I have connected my phone to IPhoto on my Mac but when I clik on Import nothing happens. What am I doing wrong?

    I am trying to download photos off my IPhone as the "Cloud" tells me I have run out of storage space. I have connected my phone to IPhoto on my Mac but when I clik on Import nothing happens. What am I doing wrong?

    Help for iCloud storage space >>   Managing your iCloud storage

  • ORA-30928: "Connect by filtering phase runs out of temp tablespace"

    i have created a query that is sued to display a data in a label. This particular query will then be stored into a program that we use. The query runs just fine until this morning when it returns the error ORA-30928: "Connect by filtering phase runs out of temp tablespace". I have Googled and found out that I can do any of the following:
    Include a NO FILTERING hint - but did not work properly
    Increase the temp tablespace - not applicable to me since this runs in a production server that I don't have any access to.
    Are there other ways to fix this? By the way, below is the query that I use.
    SELECT * FROM(
    SELECT
    gn.wipdatavalue
    , gn.containername
    , gn.l
    , gn.q
    , gn.d
    , gn.l2
    , gn.q2
    , gn.d2
    , gn.l3
    , gn.q3
    , gn.d3
    , gn.old
    , gn.qtyperbox
    , gn.productname
    , gn.slot
    , gn.dt
    , gn.ws_green
    , gn.ws_pnr
    , gn.ws_pcn
    , intn.mkt_number dsn
    , gn.low_number
    , gn.high_number
    , gn.msl
    , gn.baketime
    , gn.exptime
    , NVL(gn.q, 0) + NVL(gn.q2, 0) + NVL(gn.q3, 0) AS qtybox
    , row_number () over (partition by slot order by low_number) as n
    FROM
    SELECT
    tr.*
    , TO_NUMBER(SUBSTR(wipdatavalue, 1, INSTR (wipdatavalue || '-', '-') - 1)) AS low_number
    , TO_NUMBER(SUBSTR(wipdatavalue, 1 + INSTR ( wipdatavalue, '-'))) AS high_number
    , pm.msllevel MSL
    , pm.baketime BAKETIME
    , pm.expstime EXPTIME
    FROM trprinting tr
    JOIN CONTAINER c ON tr.containername = c.containername
    JOIN a_lotattributes ala ON c.containerid = ala.containerid
    JOIN product p ON c.productid = p.productid
    LEFT JOIN otherdb.pkg_main pm ON trim(p.brandname) = trim(pm.pcode)
    WHERE (c.containername = :lot OR tr.SLOT= :lot)
    )gn
    LEFT JOIN otherdb.intnr intn ON TRIM(gn.productname) = TRIM(intn.part_number)
    connect by level <= HIGH_NUMBER + 1 - LOW_NUMBER and LOW_NUMBER = prior LOW_NUMBER and prior SYS_GUID() is not null
    ORDER BY low_number,n
    WHERE n LIKE :n AND wipdatavalue LIKE :wip AND ROWNUM <= 300 AND wipdatavalue NOT LIKE 0
    I am using Oracle 11g too.
    Thanks for the help everyone.

    Hi,
    The documentation implies that the START WITH and CONNECT BY clauses should come before the GROUP BY clause. I've never known it to make a difference before, but you might try putting the GROUP BY clause last.
    If you're GROUPing by LEVEL, what's the point of SELECTing MAX (LEVEL)? MAX (LEVEL) will always be the same as LEVEL.
    What are you trying to do?
    Post some sample data (CREATE TABLE and INSERT statements) and the results you want from that data, and somebody will help you get them.

  • JCo Connections in WD Model running out

    Hello,
    we have WD application that uses RFC model.
    During a load test we have observed that the connection
    pools are running out of JCo connections. The result is a an error message in the trace file
    and Http 500 response code to the end user.
    Number of concurrent users: 20
    Max Pool Size: 20
    Max Connections: 20
    Exception:
    [code]aused by: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool ME_LP_MODELDATA_TSTWEB1_PT_useSSO is exhausted. The current pool size limit is 20 connections.
         at com.sap.mw.jco.JCO$Pool.getClient(JCO.java:5150)
         at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:5849)
         at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:5799)
         at com.sap.mw.jco.JCO.getClient(JCO.java:8076)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.getClient(AbstractJCOClientConnection.java:393)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel.getCurrentlyUsedJcoClient(AiiModel.java:191)[/code]
    Questions:
    Is it necessary to have equal number of Max Connections as
    number of potential concurrent users?
    Or is there a way to manually release not used connections?
    Best Regards, Maik

    Hi,
    It is not necessary to create as many connections as there are concurrent users.
    We have to handle the scope of the connection properly and also close the connections once we complete the task.
    Re: How to close a model object connection for Adaptive RFC?
    Regards
    Bharathwaj

Maybe you are looking for