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. -- Bruce Tong Software Engineer Office of Information Technology Ohio University -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
