MySQLNonTransientConnectionException and Reached maximum capacity of pool

Hi. I'm using jedeveloper 11g and weblogic 10.3x and I'm quite new at this. I have an application with basic CRUD functions deployed in my weblogic server with a MySQL database as its data source. It was running well until we encountered an SQL exception error. Here's the log of the error:
BEA-001112 - Test "SELECT 1" set up for pool "EvCoreMySqlDS" failed with exception: "com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after statement closed.".
After some time, we tried accessing the page again. This time, it was now running perfectly well again. Then sometimes it throws this error with a blank page.
BEA-000627 - Reached maximum capacity of pool "EvCoreMySqlDS", making "0" new resource instances instead of "1".
Can anyone help me regarding these two errors? Are these two errors related? Could you please enlighten me how did these occur? And most importantly, how can I fix this? Thanks.
Edited by: rageDev on Sep 2, 2010 11:44 PM

Hi Kal,
we already enabled Inactive connection timeout is 900 still its throughing the info.
Thanks,
Edited by: 834617 on Nov 28, 2012 10:39 AM

Similar Messages

  • Outage with BEA-000627 Reached maximum capacity of pool

    Hi , i am having an outage in the application and at the time of outage i am seeing a lot of <BEA-000627> <Reached maximum capacity of pool > messages.
    Now just before i am getting <BEA-000627> <Reached maximum capacity of pool > i have seen messages of :
    <BEA-001128> <Connection for pool "iemphsysOracleCP" closed.>
    there are 45 such connection closing messages .
    the initial capcity for connection is 25 and maximum capacity is 75 , 50 threads are allowed to run.
    just after closing the connection by weblogic , i see only one message of connection created , but after that i see messages of reached maximum capacity.
    The shirking is allowed and shrinking frequency is 900 secs, now the connections are closed when there are connections existing in the pool above the initial capacity and they are not being used, so weblogic closes the connection, in my problem the connections are closed and just after that one connection created and i see messages of reached maximum capacity , if connections are closed then these should be able to be created again and i shoud not see that maximum capacity message.
    The test connections frequency is also 0 and testconns on reserve set to true , also testconnon release is true.
    Remove infected connections is enabled.
    how it can reach maximum capacity while just before that it is closing the connections ????

    gaurav joshi wrote:
    Hi , i am having an outage in the application and at the time of outage i am seeing a lot of <BEA-000627> <Reached maximum capacity of pool > messages.
    Now just before i am getting <BEA-000627> <Reached maximum capacity of pool > i have seen messages of :
    <BEA-001128> <Connection for pool "iemphsysOracleCP" closed.>
    there are 45 such connection closing messages .
    the initial capcity for connection is 25 and maximum capacity is 75 , 50 threads are allowed to run.
    just after closing the connection by weblogic , i see only one message of connection created , but after that i see messages of reached maximum capacity.
    The shirking is allowed and shrinking frequency is 900 secs, now the connections are closed when there are connections existing in the pool above the initial capacity and they are not being used, so weblogic closes the connection, in my problem the connections are closed and just after that one connection created and i see messages of reached maximum capacity , if connections are closed then these should be able to be created again and i shoud not see that maximum capacity message.
    The test connections frequency is also 0 and testconns on reserve set to true , also testconnon release is true.
    Remove infected connections is enabled.
    how it can reach maximum capacity while just before that it is closing the connections ????Hi. Can you tell me the version of WLS you're using, and also
    show me the whole pool definition? There's no need for shrink.
    I would recommend turning it off. I would set initial capacity
    and max capacity to 50. I would turn off test-conn-on-release.
    That is a waste of performance.
    Joe

  • Reached maximum capacity of pool "eis/PRAdapterCF", making "0" new resource

    Hi All,
    We configured weblogic with pega. I am getting below error. Any idea ?
    I enabled test conection reserve. and increased test frequency 900
    ####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746443> <BEA-000627> <Reached maximum capacity of pool "eis/PRAdapterCF", making "0" new resource instances instead of "1".>
    ####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746444> <BEA-000628> <Created "1" resources for pool "eis/PRAdapterCF", out of which "1" are available and "0" are unavailable.>
    ####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746749> <BEA-000627> <Reached maximum capacity of pool "eis/PRAdapterCF", making "0" new resource instances instead of "1".>
    ####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746750> <BEA-000628> <Created "1" resources for pool "eis/PRAdapterCF", out of which "1" are available and "0" are unavailable.>
    ####<Nov 13, 2012 1:25:46 PM CST> <Info> <Common> <test4> <PEGA> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1352834746837> <BEA-Thanks,
    Edited by: 834617 on Nov 13, 2012 11:32 AM

    Hi Kal,
    we already enabled Inactive connection timeout is 900 still its throughing the info.
    Thanks,
    Edited by: 834617 on Nov 28, 2012 10:39 AM

  • WLS 10.3.0.0 Solaris SPARC and DBMS Oracle 10gR2 connection pooling issue

    Hi all,
    we are currently testing Weblogic Server 10.3.0.0 in order to migrate our production system from WLS 8.1 to it.
    While testing the new setup, we encountered some strange behaviour of the connection pooling within WLS.
    We configured a XA-Connection pool to our DB (Oracle 10gR2) by using
    a) the Oracle XA-thin-driver delivered within WLS 10.3.0.0
    and alternatively
    b) the Oracle 11.2.0.2 OCI-driver of the Oracle 11g database client.
    We´ve got the same issue with both variants. We defined an initial capacity of 5 connections and a maximum capacity of 30 connections.
    Our application is running flawlessly using the connection pool, but the amount of active sessions between the application server and the database server is increasing rapidly and the maximum capacity is exceeded. We are seeing up to multiple hundreds of sessions from the application server to our database server. Obviously the connections aren´t cleaned up.
    We are using the following settings for the JDBC-Connection:
    initial capacity = 5
    max. capacity = 30
    Capacity increment = 1
    Statement cache type = LRU
    Statement cache size = 10
    Test connections on reserve = true
    Test frequency = 120
    Test table name = "sql select 1 from dual"
    seconds to trust an idle pool connection = 10
    shrink frequency = 0
    connecttion creation retry frequency = 120
    login delay = 0
    incative connection timeout = 10
    max. waiting for connection = 2147483647
    connection reserve timeout= = -1
    Ignare in-use connections = true
    pinned-to-thread = false
    remoce infected connections enabled = true
    Does anyone have an idea how to track/solve this issue?
    Kind regards
    Marc

    Hi Joe,
    we´ve tested with the thin driver using an initial capacity of 5 and a maximum capacity of 15. During our tests (in a very short time period) the maximum capacity has not been exceeded. But we saw some exceptions in the managed server logfile which made us curious.
    When these exceptions are occuring, a new connection to the database server is established. We are seeing for a short time a total count of 6 connections which is immediately decreasing to the initial capacity of 5. We will do some further testing over the next hours and monitor the connection usage.
    The connection we are dealing with is the one called "ZDB2".
    This is an excerpt of the logfile:
    ####<18.10.2010 19:45 Uhr MESZ> <Debug> <JDBCConn> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-02F7EA174F1D84653A69> <> <1287423940610> <BEA-000000> <java.lang.Exception: Pinned: autoCommit=true,enabled=true,isXA=true,isJTS=false,vendorID=0,connUsed=true,doInit=false,'null',destroyed=false,poolname=ZDB2,appname=null,moduleName=null,connectTime=177,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=true,lastSuccessfulConnectionUse=1287423940605,secondsToTrustAnIdlePoolConnection=10,currentUser=java.lang.Exception
         at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:308)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:314)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:427)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
         at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1473)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1272)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:425)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:382)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:338)
         at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
         at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
         at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
         at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
         at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1547)
         at org.hibernate.loader.Loader.doQuery(Loader.java:673)
         at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
         at org.hibernate.loader.Loader.doList(Loader.java:2220)
         at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104)
         at org.hibernate.loader.Loader.list(Loader.java:2099)
         at org.hibernate.hql.classic.QueryTranslatorImpl.list(QueryTranslatorImpl.java:912)
         at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172)
         at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121)
         at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
         at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:811)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderPersistenceGenerated.findByPrimaryKey(OrderPersistenceGenerated.java:45)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1356)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:830)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1276)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:19812)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1289)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:823)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1341)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:816)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1255)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:7332)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1266)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:809)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1636)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    ,currentThread=Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],lastUser=null,currentError=null,currentErrorTimestamp=null,JDBC4Runtime=true,supportStatementPoolable=true,needRestoreClientInfo=false,defaultClientInfo={} is set to be refreshed
         at weblogic.jdbc.common.internal.ConnectionEnv.setRefreshNeeded(ConnectionEnv.java:518)
         at weblogic.jdbc.wrapper.Connection.getVendorConnection(Connection.java:292)
         at de.dpcom.persistence.hibernate.BinaryBlobType.nullSafeSet(BinaryBlobType.java:109)
         at org.hibernate.type.CustomType.nullSafeSet(CustomType.java:146)
         at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:1997)
         at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2371)
         at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2307)
         at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2607)
         at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92)
         at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
         at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232)
         at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140)
         at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
         at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
         at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CertificatePersistenceGenerated.updateCertificate(CertificatePersistenceGenerated.java:116)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceImplStandard.updateCertificate(CustomerManagementServiceImplStandard.java:1282)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceTransactionHandler.updateCertificateTx(CustomerManagementServiceTransactionHandler.java:711)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceSessionBean.updateCertificate(CustomerManagementServiceSessionBean.java:1104)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementEJB_ap2i9a_ELOImpl.updateCertificate(CustomerManagementEJB_ap2i9a_ELOImpl.java:19199)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceApplicationProxy.updateCertificate(CustomerManagementServiceApplicationProxy.java:1101)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceImpl.publishCertificate(ProductionResultProcessingServiceImpl.java:1131)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceTransactionHandler.publishCertificateTx(ProductionResultProcessingServiceTransactionHandler.java:298)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean.publishCertificate(ProductionResultProcessingServiceSessionBean.java:517)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.publishCertificate(ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.java:1804)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceApplicationProxy.publishCertificate(ProductionResultProcessingServiceApplicationProxy.java:471)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishCertificate(OrderManagementServiceImpl.java:1825)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1664)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940797> <BEA-001072> <Connection for XA pool "ZDB2" created.>
    ####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-001132> <Initialized statement cache of size "10" for connection in pool "ZDB2".>
    ####<18.10.2010 19:45 Uhr MESZ> <Info> <Common> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-000628> <Created "1" resources for pool "ZDB2", out of which "1" are available and "0" are unavailable.>
    Any suggestions?
    Kind regards
    Marc

  • Datasource Maximum capacity in Cluster

    Hi,
    I have configured a datasource and assigned maximum capacity of 10 and initial capacity to 2 and targeted it to all server in a clusters(node 1 & node 2).
    now how the connections will be utilized in the clustered mode. Both the node will have maximum of 10 connection limit
    or each node will have maximum of 10 connection limit ? please clarify me.
    Thanks
    KK

    Maximum Capacity
    Maximum capacity is number of allocated session in database side for WebLogic Server divide by number of WebLogic server. Example, DBA allocated 500 session for WebLogic server which has 5 server, so this config value is 500/5 = 100
    Initial Capacity
    Initial capacity mean number of initial session created when data source started. Recommended value for Initial Capacity is equal to Maximum Capacity size database connection pools. In this case WebLogic never increase the number of connections when it needed by application. Negative impact for this case is increase DB load although only few session use by WebLogic, but if impact in database side is not significant its work well.
    Regards
    Mukesh Negi
    http://weblogicserveradministration.blogspot.in/2010/10/jdbc-connection-pool-performance-tuning.html

  • Satellite M110 - RAM upgrade and maximum capacity

    I have a Satellite M110 and would like to upgrade the RAM as much as possible. It has the original RAM from the factory. The manual gives me the model numbers for memory depending on the model of the computer - ie either PC2-4200 or PC2-5300. How do I tell which one I have? I can't see either of those numbers anywhere. Is 1GB the largest RAM this computer will take?

    Hi lenore104,
    The maximum RAM capacity is also depending on the chipset. Furthermore the maximum RAM capacity can also be found in user manual.
    Did you find this information?
    The specifications of memory modules you can find on memory module itself. So if you remove the current memory module you should see a sticker on it with technical information such as PC2-4200.
    If you post the exact model number of the notebook we can search on Toshiba website for maximum capacity.

  • Toshiba Satellite L750-1LM PSK6RE-01N00RG5 Ram Upgrade and Maximum Capacity help

    Hello, I have Toshiba Satellite L750-1LM PSK6RE-01N00RG5 I want to upgrade my ram. How much is the maximum capacity of ram ? Through a command in linux I found it is 16GB (8gb and 8gb)Is there any limitation in speed?In my ram slots says 1.5v if I buy 1.35v will be a problem? Is this ram compatible with my laptop?RAM CORSAIR CMSO8GX3M2A1333C9 SO-DIMM 8GB (2X4GB) PC3-10666 DUAL CHANNEL KIT Size: 8GB (2 x 4GB kit).
    Memory Type: DDR3 PC3-10600 204-pin SODIMM
    Bus Speed: 1333 MHz.
    Timings: 9-9-9-24.
    Power: 1.5 V.
    Additional features: Non ECC Memory. I know from Kingston Support that this ram is not compatible with my laptop        RAM KINGSTON KVR1333D3S9/8G 8GB SO-DIMM DDR3 PC3-10600 1333MHZ VALUE RAMand that I cannot buy any Kingston memory due to they stop supporting my laptop.

     
    Satellite L750-1LM (PSK6RE-01N00xxx)
    According to the spec above, there are two slots and you can have up to 8 GB of DDR3 RAM (1,066 MHz).
    Toshiba peddles this: 4GB DDR3 (1066MHz) PA3677U-1M4G
    See the section Additional Memory Module, which begins on p. 3-17 of the User's Manual (attached).

  • NSS6000 and maximum capacity

    I am going to build a RAID5  config in my Cisco/Linksys NSS6000.  I am going to buy (4) Sata drives but  wasn't sure if there is a limit to the size of drives that the NSS6000 can  handle.  I was thinking of getting (4) 500gb drives but am seeing 1.5tb drives  becoming cheaper and am thinking of getting 4 of those instead.  Anybody know  the limitations on the NSS6000?
    thanks.

    Hi lenore104,
    The maximum RAM capacity is also depending on the chipset. Furthermore the maximum RAM capacity can also be found in user manual.
    Did you find this information?
    The specifications of memory modules you can find on memory module itself. So if you remove the current memory module you should see a sticker on it with technical information such as PC2-4200.
    If you post the exact model number of the notebook we can search on Toshiba website for maximum capacity.

  • UnsyncCircularQueue$FullQ Queue exceed maximum capacity of: '65536' element

    dear friends:
    Does anyone knows the problem like this <BEA-002911> <WorkManager ClusterMessaging failed to schedule a request due to weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements
    weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity of: '65536' elements
    why this happend and how to solve it?
    thanks a lot!

    Hi,
    Weblogic has a maximum storage for Pending Request queue configured at 65536. At this point, it will stop accepting incoming request to your Server Socket port.
    This means that your Weblogic server / JVM very likely has depleted its internal Thread Pool triggering Weblogic to start queuing incoming requests; eventually reaching its maximum capacity.
    From a resolution perspective, you will need to investigate the root cause, Thread Dump generation and analysis will be required in your case.
    Please generate a JVM Thread Dump (kill -3 <pid> for UNIX OS) and share detail on Thread contention / problem pattern.
    Thanks.
    P-H
    http://javaeesupportpatterns.blogspot.com/

  • Channel has reached maximum concurrency (5,000 concurrent messages)

    Hi Experts,
    I have executed a scenario: IDocs to AS400 (JDBC Adapter). Some IDocs were processed succesfully but some are giving the following error.
    "com.sap.aii.af.ra.ms.api.RecoverableException: Channel has reached maximum concurrency (5,000 concurrent messages) and no free resource found within 5,000 milliseconds; increase the maximum concurrency level"
    Can any one faced this problem? Please do needful...
    Regards,
    Ramesh.

    Hi,
    This error occurs when the channel has only few (minimum 1) resources in the pool(to connect the DB in parallel) and the messages load to that channel is high. Hence, channel will reach to maximum concurrency( minimum 1, by default). In this case, you can increase this maximum concurrency value to higher value (could be 3 to 5) and check whether the issue is happening still.
    Hope this feature implementation will solve your problem.
    Regards,
    Soorya

  • Problem with reached maximum number of connections to database

    Dear Experts,
    Our Production system was not responding properly last week.
    The below was the reply from the Basis team.
    "It seems that we have again problem with reached maximum number of connections to database. We have extended this number to 100 this year and now it seems that it’s not enough again. It seems that something is running on Production, which takes over too many connections."
    They have increased the number to 200 as a work around.
    Do we have any means to find out, which component or application is causing the issue.
    Please advise me if any better way is available to correct the issue.
    Please see the below trace.
    From default trace:
    ======
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.R
    esourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You
    can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections ar
    e not enough for current load.
            at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:60)
            at com.sap.security.core.persistence.datasource.imp.J2EEConnectionPool.getConnection(J2EEConnectionPool.java:205)
            ... 61 more
    Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to
    DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unr
    eachable. 3) Connections are not enough for current load.
            at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:230)
            at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:343)
            at com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54)
            at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:52)
            ... 62 more
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: No c
    onnection to data source SAPEPPDB available. All 100 pooled connections are in use and 70 connection requests are currently waiting. The connection pool size might
    need to be adjusted.
            at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:192)
            at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:221)
            ... 65 more
    Caused by: com.sap.sql.log.OpenSQLException: No connection to data source SAPEPPDB available. All 100 pooled connections are in use and 70 connection requests are
    currently waiting. The connection pool size might need to be adjusted.
    ======
    Thanks and Kind Regards,
    Jelbin

    Stop all instances(including DB) and start again, Hope it should work.
    It may happened that jar has not been synchronized with the database and may be version mismatch with the java.
    719778 - Data Source fails to return connection
    1650472 - Transactions are interrupted due to database connection periodically failing to establish
    1138877 - How to Deploy External Drivers JDBC/JMS Adapters
    Change the connection pool so that it can connect to DB as per the note 719778
    Regards
    Vijay Kalluri

  • Queue exceed maximum capacity of '256' elements.

              Has anyone seen this one before??
              Thanks
              Thomas
              weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity
              of: '256' elements.
              weblogic.utils.UnsyncCircularQueue$FullQueueException:      of: '256' elements
              at weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:72)
              at weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:94)
              at weblogic.kernel.ExecuteThreadManager.execute(ExecuteThreadManager.java:343)
              at weblogic.kernel.Kernel.execute(Kernel.java:338)
              at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:304)
              at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:923)
              at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:844)
              at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:222)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:794)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:570)
              at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:681)
              at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:627)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              

    Hi,
              The queue in question here is not a JMS queue. Instead,
              this is the "execute queue" of jobs waiting to be
              serviced by a thread in its thread pool.
              I think the size of these queues is configurable on the
              thread pool. Note that if dead-lock is locking up threads
              and causing the problem,
              you will likely need to increase the number of threads
              or dedicate server-side resources to their own thread pools
              rather than (or in addition to) increasing the size
              of the execute queues. (A thread dump helps
              in diagnose dead-locks.)
              Likely this error is on a server side thread pool, so
              there should be warnings/error messages in the server logs
              that describe what is happening.
              Tom
              Thomas Kreig wrote:
              > Has anyone seen this one before??
              > Thanks
              > Thomas
              >
              > weblogic.utils.UnsyncCircularQueue$FullQueueException: Queue exceed maximum capacity
              > of: '256' elements.
              > weblogic.utils.UnsyncCircularQueue$FullQueueException:      of: '256' elements
              > at weblogic.utils.UnsyncCircularQueue.expandQueue(UnsyncCircularQueue.java:72)
              > at weblogic.utils.UnsyncCircularQueue.put(UnsyncCircularQueue.java:94)
              > at weblogic.kernel.ExecuteThreadManager.execute(ExecuteThreadManager.java:343)
              > at weblogic.kernel.Kernel.execute(Kernel.java:338)
              > at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:304)
              > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:923)
              > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:844)
              > at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:222)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:794)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:570)
              > at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:681)
              > at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:627)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              

  • Channal Reaches Maximum - Urgent

    Hi all
              when i start my Weblogic 81 sp2, MQ Channal reacheds 92 connection.
              why its increase?.
              can u explain.
              i am using IBM MQ Series 5.3 as a foreign JMS server.
              and i have 8 MDB to lisiten queues and i defined 8 channal only. but when i start weblogic 81 server(Production Mode) , that time channal connections are reaching 90+, than its keep on increasing.
              plz let me, how to rectify the pbm.
              thanx n advance
              regards
              muruganandam

    I presume that the MDBs in your server are set up to dequeue from MQ. So, when you boot the server, they connect to MQ and they start receiving messages. How do you have them configured? This will control how many connections are deployed for the MDBs.
              The "max-beans-in-free-pool" parameter in the descriptor of the MDB sets a maximum number of connections for each MDB that you deploy. The server limits this number to one-half the total number of threads in the server for each MDB, but if your server is running with 16 threads, and max-beans-in-free-pool is larger than 8, then you'll have 8 connetions for each MDB.
              (Plus, that means that WLS will open eight JMS connections per MDB. How many "channels" MQ opens with those either JMS connections is something that only IBM knows.)
              If you look at your MDB descriptors and reduce "max-beans-in-free-pool" for each MDB, you can reduce the number of MQ connections that are created.

  • How do I add new Apple ID as it said it reach maximum

    Please tell me how do I add new apple id as I already added a lot and it's said that it reach maximum. I forgot my Apple ID password and can't recover because I cant ***** the email.

    Easy. Open System Preferences > iCloud and sign in with the same Apple ID and password you used when you initially set up your MacBook Pro. Select the iCloud services you wish to use.
    I also want to know how to sink my phone with my Mac
    Read iOS: Syncing your data with iTunes
    Instructional video

  • What's The Maximum Capacity of Mac Mail

    Hi All
    I am new in Mac world, I was using outlook in windows with many email, the email files around 3GB, I did the converter of emails by using outlook2mail application.
    My questions are, how much the maximum capacity of mac mail, and now I am using mac mail with few emails, its working fast, if I transfer all my emails to mac mail (1000s emails, around 3GB) is it will work in same speed or it will work slow or die ?
    Thanks
    Khalid

    You've asked an unanswerable question. To my best knowledge there are no limits, other than as Barney says the available space on your hard drive. Also, it's impossible to quantify it because email messages vary in size. Do you delete large attachments? Have you created new Mail folders Mail > Mailboxes Sidebar > +? I do have a friend who has over 20,000. If anything gets mucked up you can always rebuild a mailbox from your Mail menu > Mailbox >Rebuild.
    -mj

Maybe you are looking for