It works for me. If you are really curious if the right number of
threads are being started (outside of the test I suggested in a previous
email), I would simply do System.out.println("number of active threads "
+ Thread.activeCount()); in the service code... this would obviously
have some number of threads running in an idle container, and the number
should increase to the maximum under heavy concurrent load. Remember,
you need to generate many (equal to or more than the number of max
threads set at the container) concurrent client requests to cause the
container to allocate those extra threads.
Samuel LIU wrote:
Anyone had experience in setting containerThreads in
$GLOBUS_LOCATION/etc/globus_wsrf_core/server-config.wsdd and getting it work?
_________________________________________________________________
Connect and share in new ways with Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008
