Avalon Excalibur



Jakarta main

Avalon main

About
  • Overview
  • Changes
  • Download
  • API Docs


  • Released Components
  • Command-Line Inspection
  • Collections
  • Component Utilities
  • Concurrent Threading
  • DataSource Management
  • IO Utilities
  • Pooling Support
  • Property Utilities


  • Components under Development
  • Internationalization
  • Piping Support
  • Proxy Implementation
  • Thread Pool Management



  • Avalon Excalibur : Pooling Support


    Optimise your resources with pools

    Find Avalon Excalibur's Pool implementations in the org.apache.avalon.excalibur.pool package. There are many implementations that are ThreadSafe, and one that is not. You have the option of not limiting used resources at all, or limiting the used resources based on specific rules.

    If you are using the Exalibur Component Management package, you can have your components implement Poolable or Recyclable from this package, and your components will be pooled. The Components are pooled with a soft resource limmiting pool. That means that as additional resources are needed, they are created--but once they are returned to the pool, the extra instances are decommissioned.

    The Excalibur DataSources package also uses this package, and uses a hard resource limiting pool. If the number of open JDBC Connections exceeds the limit, an exception is thrown.


    by Berin Loritsch, Leo Simons



    Copyright © 1999-2001 The Apache Software Foundation. All Rights Reserved.