camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-3437) Managed thread pool should have better object names and provide source and route details if applicable
Date Sat, 18 Dec 2010 10:50:01 GMT

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

Claus Ibsen resolved CAMEL-3437.
--------------------------------

    Resolution: Fixed

trunk: 1050612.

Improved naming for common thread pools used internally in Camel such as for producer template,
error handlers, graceful shutdown etc.

> 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.


Mime
View raw message