sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Sling Website > Apache Sling Commons Thread Pool
Date Wed, 03 Aug 2011 07:57:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/2042/9/1/_/styles/combined.css?spaceKey=SLINGxSITE&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">Apache
Sling Commons Thread Pool</a></h2>
    <h4>Page  <b>added</b> by             <a href="">Carsten
    <div class="notificationGreySide">
         <p>The Apache Sling Commons Thread Pool bundle provides a thread pool services.
All thread pools are managed by the <em></em>.
This service can be used to get a thread pool.</p>

<p>Thread pools are managed by name - there is a default thread pool and custom thread
pools can be generated on demand using a unique name.</p>

<p>The thread pools are actually wrappers around the thread pool support (executer)
from the Java library. The advantage of using this thread pool service is, that the pools
can be configured and managed through OSGi configurations. In addition the bundle contains
a plugin for the Apache Felix Web Console.</p>

<p>When using the ThreadPoolMananger it is important to release a thread pool using
the manager after it has been used.</p>
    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
       <a href="">View
       <a href=";showCommentArea=true#addcomment">Add

View raw message