• Online Training

    Online Training

    How to handle 'Weblogic Resource Limit Exception'

    Guys, Anyone come across the exception while using weblogic as your application hosted server.
    The error weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool to allocate to applications, please increase the size of the pool and retry. ResourceLimit Exception tells you that your application is not able to obtain a JDBC connection from your weblogic datasource beyond an extent. At this point we will be seeing system status as "OVERLOADED" in console.


    Root Cause: There were two reasons that we can expect here.

    1. Connection Leak: There might be some connection leakages in the code. Whatever the connections open are not closed properly. Due to this every time when a new user connects to the DB will always be in a active state which intern increases the active connections to reach the threshold of the maximum capacity of the datasource.

    2. Unsuitable connection pool parameters:  When connection pool maximum capacity is less when compared with calls made by the application which makes the pool size to fill quite often leading to an overloaded case. In that case we may need to increase the Maximum capacity value in weblogic.


    How to Fix:
    1. Check for any connection leaks in the code properly and verify all opened connections are closed.

     2. Monitor the DB usage, DB response time and DB calls/sec. Based upon the readings change the connection pool parameters.

    Work Around fix; Restart the managed server to release the connections. 

    4 comments

    Post a Comment