You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/12/18 10:42:01 UTC

[jira] Commented: (CAMEL-3437) Managed thread pool should have better object names and provide source and route details if applicable

    [ https://issues.apache.org/jira/browse/CAMEL-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972760#action_12972760 ] 

Claus Ibsen commented on CAMEL-3437:
------------------------------------

trunk: 1050603.

> Managed thread pool should have better object names and provide source and route details if applicable
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3437
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3437
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> Currently thread pool just use the class name and instance hashcode. This makes it harder for end users to know which pools is what.
> So we should use id of thread pool if possible. Also if the thread pool is from an EIP in the routes, then the source and route details should be added as attributes.
> For example the Threads EIP or Aggregator in parallel mode both uses a thread pool.

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