You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/12/16 16:05:18 UTC
[jira] Created: (SLING-1244) Redesign thread pool management
Redesign thread pool management
-------------------------------
Key: SLING-1244
URL: https://issues.apache.org/jira/browse/SLING-1244
Project: Sling
Issue Type: Improvement
Affects Versions: Commons Threads 2.0.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
The current thread pool management has some drawbacks:
- the api contract is slightly confusing, e.g. create with a new configuration could be called and this new configuration is completly ignored
- no reference counting of thread pools - thread pools are only shutdown when the bundle is shutdown
- thread pools are not manageable through config admin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1244) Redesign thread pool management
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1244.
-----------------------------------
> Redesign thread pool management
> -------------------------------
>
> Key: SLING-1244
> URL: https://issues.apache.org/jira/browse/SLING-1244
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons Threads 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons Threads 3.0.0
>
>
> The current thread pool management has some drawbacks:
> - the api contract is slightly confusing, e.g. create with a new configuration could be called and this new configuration is completly ignored
> - no reference counting of thread pools - thread pools are only shutdown when the bundle is shutdown
> - thread pools are not manageable through config admin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1244) Redesign thread pool management
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1244.
-------------------------------------
Resolution: Fixed
Redesigned the module with revision 891673. Thread pools are now manageable through the configuration admin. If a pool is taken from the manager it has to be released through the manager again.
> Redesign thread pool management
> -------------------------------
>
> Key: SLING-1244
> URL: https://issues.apache.org/jira/browse/SLING-1244
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons Threads 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons Threads 3.0.0
>
>
> The current thread pool management has some drawbacks:
> - the api contract is slightly confusing, e.g. create with a new configuration could be called and this new configuration is completly ignored
> - no reference counting of thread pools - thread pools are only shutdown when the bundle is shutdown
> - thread pools are not manageable through config admin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1244) Redesign thread pool management
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1244:
------------------------------------
Component/s: Commons
Fix Version/s: Commons Threads 3.0.0
> Redesign thread pool management
> -------------------------------
>
> Key: SLING-1244
> URL: https://issues.apache.org/jira/browse/SLING-1244
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons Threads 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons Threads 3.0.0
>
>
> The current thread pool management has some drawbacks:
> - the api contract is slightly confusing, e.g. create with a new configuration could be called and this new configuration is completly ignored
> - no reference counting of thread pools - thread pools are only shutdown when the bundle is shutdown
> - thread pools are not manageable through config admin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.