[jira] [Commented] (TAP5-1714) Allow to specify name for the threads created by ParallelExecutorImpl

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982324#comment-13982324 ] 

ASF subversion and git services commented on TAP5-1714:
-------------------------------------------------------

Commit 1a37c6abd59254d3e9e6ce676cd7b300d704ecac in tapestry-5's branch refs/heads/master from [~jkemnade]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=1a37c6a ]

TAP5-2219, TAP5-1778, TAP5-1714: when transforming the template stream, use the same encoding for the input and the output


> Allow to specify name for the threads created by ParallelExecutorImpl
> ---------------------------------------------------------------------
>
>                 Key: TAP5-1714
>                 URL: https://issues.apache.org/jira/browse/TAP5-1714
>             Project: Tapestry 5
>          Issue Type: Wish
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.4, 5.2
>            Reporter: Jochen Kemnade
>            Priority: Minor
>
> It would be great if the ParallelExecutorImpl used a custom ThreadFactory that used names like "parallelexecutor-thread-n" for the created threads. "parallelexecutor" could be made an overrideable symbol, e.g. tapestry.thread-pool.thread-name-prefix. That would allow different Tapestry-based web applications running in the same container to use different prefixes for the threads making them more distinguishable when monitoring the container with visualvm or the like.
> I could come up with a patch if you want me to.



--
This message was sent by Atlassian JIRA
(v6.2#6252)