[
https://issues.apache.org/jira/browse/FELIX-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954143#comment-17954143
]
Paul Rütter commented on FELIX-6783:
------------------------------------
Sounds like a few mbeans to get to these values in realtime could help here,
including a setter to adjust the threadpool size for a running application.
A PR would be considered of course.
> Improve monitoring of EventAdmin's threadpool
> ---------------------------------------------
>
> Key: FELIX-6783
> URL: https://issues.apache.org/jira/browse/FELIX-6783
> Project: Felix
> Issue Type: Task
> Components: Event Admin
> Affects Versions: eventadmin-1.6.4
> Reporter: Joerg Hoh
> Priority: Major
>
> We have a functionality which heavily uses the EventAdmin to send
> asnychronous events; this results in a heavy usage of the threadpool, and we
> often have the maxiumum number of threads active. But beyond this (which is
> also only visible in threaddumps, the actual number of threads active in that
> threadpool is not exposed at all) we don't have a chance to find out the
> actual size of the queue of the executor.
> There should be a way to monitor the relevant runtime information of the
> eventadmin to better understand what's going on.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
