On 12/20/06, stephan.lux <[EMAIL PROTECTED]> wrote:
stephan.lux wrote: > > Hi Guillaume, > > I have tried both: > > After increasing the workmanager threadpool i have received "Failed to > schedule work: java.lang.OutOfMemoryError: unable to create new native > thread" messages. > > So I have downloaded the latest 3.1 snapshot, applied the thread pool > settings of the named page and the VM crashes also by processing 2000 job > with an out of memory message. So I have limited the thread pool to 500 > and it works.
Creating new threads is quite memory intensive. Using 3.1-SNAPSHOT, thread pools are created per component, so you'd better keep the amount not too high (32 / 64 should work well).
> > What do you think about the change of my lightweight components to the new > file/ftp bindings? Does this bring a performance advantage? I have also > found a new servicemix-script component, but unfortunately no > documentation about it. Can you provide me a short sample configuration > how I can call a groovy script?
The lightweight components are not heavily worked on and you should use the new components if possible. For the script component, you can look at the junit test cases available at http://fisheye3.cenqua.com/browse/servicemix/trunk/deployables/serviceengines/servicemix-script/src/test/resources
> > Thanks, > Stephan > > > gnodet wrote: >> >> Use 3.1-SNAPSHOT and configure the thread pools to suit >> your needs (http://servicemix.goopen.org/site/thread-pools.html). >> >> Alternatively, you can grow the number of threads in the WorkManager >> (for ServiceMix 3.0), but 3.1 will certainly be more robust. >> > -- View this message in context: http://www.nabble.com/Severe-issues-while-load-testing-tf2845236s12049.html#a7993548 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
