ChannelRendererMaxActiveThreads corresponds to the peak concurrent threads ever used. So this means at one point there were 13 concurrently busy threads.

-Eric

On 09/21/2011 12:58 PM, Bruce Tong wrote:
I'm playing around with jmxterm pulling various MBean attributes. It's
both neat and easy. I've bumped into something that has me puzzled.

Consider this configuration...

org.jasig.portal.ChannelManager.threadPool_initialThreads=150
org.jasig.portal.ChannelManager.threadPool_maxThreads=150

... and then when I ask the MBean for the max number of rendering
threads, I get...

ChannelRendererMaxActiveThreads = 13;

13? I expected 150.

I'm playing with 3.2.5+. I've not really looked at uPortal internals
before, so I'm probably in left field, but it looks like both of those
150 values will get to a subclass of ThreadPoolExecutor.


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to