[jira] Closed: (COCOON-2019) Make DefaultRunnableManager custom configurable

["Felix Knecht (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/COCOON-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Knecht closed COCOON-2019.
--------------------------------

    Resolution: Fixed

Refactored ThreadPool. Break out the ThreadPool into a bean. This will
make it easier to configure custom thread pools for the RunnableManager.
The RunnableManager will load all thread pools implementing the interface
'ThreadPool'.

A new thread pool can be added by defining the custom thread pool to add
in your spring configuration:

  <!--+
      | My thread pool
      +-->
  <bean name="org.apache.cocoon.components.thread.ThreadPool/myThreadPool" class="org.apache.cocoon.components.thread.DefaultThreadPool" scope="singleton">
    <property name="name" value="myThreadPool"/>
    <property name="poolPriority" value="NORM"/>
    <property name="daemon" value="true"/>
    <property name="queueSize" value="0"/>
    <property name="maxPoolSize" value="-1"/>
    <property name="minPoolSize" value="1"/>
    <property name="keepAliveTime" value="60000"/>
    <property name="blockPolicy" value="ABORT"/>
    <property name="shutdownGraceful" value="false"/>
    <property name="shutdownWaitTimeMs" value="-1"/>
    <property name="factory" ref="defaultThreadFactory"/>
  </bean>



> Make DefaultRunnableManager custom configurable
> -----------------------------------------------
>
>                 Key: COCOON-2019
>                 URL: https://issues.apache.org/jira/browse/COCOON-2019
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: * Cocoon Core
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Felix Knecht
>         Assigned To: Felix Knecht
>             Fix For: 2.2-dev (Current SVN)
>
>         Attachments: DefaultRunnableManager.diff
>
>
> Introduce data beans for configuration of the DefaultRunnableManager. This will give the chance to add customized configurations without the need of patch the configuration deployed with the jar file.
> The new way of configuration uses a bean-map to get the configurations -> Every bean implementing the interface ''org.apache.cocoon.components.thread.ThreadPoolConfiguration" will be taken as single thread-pool configuration. The two (already existing) configurations "default, daemon" will still be deployed with the jar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.