ProfiledScheduledThreadPoolExecutor doesn't provide indicator for maxPoolSize, which is the threadPoolSize variable in our case. I think it was made intentionally because it's client-side property, so client better knows is it necessary to profile it or not.
I think we need to profile this property, it will help us debug DJM.