Reached maximum capacity of pool MyPoolDS making 0 new resource instances instead of 10
Reached maximum capacity of pool MyPoolDS making 0 new resource instances instead of 10

Issue:

What to do when you see a similar message in weblogic server logs:

<BEA-000627> <Reached maximum capacity of pool "MyPoolDS", making "0" new resource instances instead of "10".>

Suggestions:

  1. What is the right thing to do after Reached maximum capacity of pool?

    • You can get this message, in many scenarios
      • When the number of connections configured for the connection pool using MaxCapacity is not sufficient for the application use. In this case, it is suggested to increase the no: of connections
      • When there is no available thread to get the connection. As a thumb rule, it is always recommended to keep the execute thread size equal to the max number of connection.

  2. You can tune the ‘InactiveConnectionTimeoutSeconds’ parameter:

    • InactiveConnectionTimeoutSeconds refers to the number of inactive seconds on a reserved connection before Weblogic Server reclaims the connection and releases it back into the connection pool
    • You can use the Inactive Connection Timeout feature to reclaim leaked connections - connections that were not explicitly closed by the application. Note that this feature is not intended to be used in place of properly closing connections.
    • When set to 0, the feature is disabled
    • In addition to all the above information, it is always recommended to follow the following settings for your connection pool in your production environment to improve performance:
      • set InitialCapacity = MaxCapacity
      • This will ensure that all connections are opened during Weblogic Server start. As creation of a physical database connection is very expensive, all needed connections should be opened immediately and kept open
      • disable shrinking by setting to false
      • As mentioned above, creation of physical database connections is expensive, connections should be established once and kept during the complete lifetime of the Weblogic Server instance
      • Set to true, this will ensure that connections are tested before they go to the application and are reopened if needed set to false
      • As connection testing is an overhead that should be avoided where possible, connection testing for connections that an application gives back to the pool is an unnecessary effort. As long as connections are tested during a getConnection, this is not needed
      • Using ‘TestConnectionsOnReserve’ and ‘TestConnectionsOnRelease’ may have an impact on performance

Cheers:)

Unni

comments here

December 7, 2009
363 words

Categories
Tags
example hugo blog

Connect. Socialize.

Sponsors