Hi,
As you're using Servicemix 3.3.2, for better performance of concurrent
client, you need add synchronous="false" to cxf bc consumer
configuration.
Also you need configure a big thread pool for the cxf bc and cxf se
component, take a look at [1] to get more details.
[1]http://servicemix.apache.org/thread-pools.html
Freeman
On 2011-8-9, at 上午4:10, Lorenzo Bolzani wrote:
Hi,
I try to better explain the situation.
I'm running Servicemix 3.3.2, jdk 1.5.0, on linux 2.6.38
I have deployed a simple cxf component that does nothing at all and
returns a simple result class.
I have a client generated from the WSDL that invokes the component
using several threads, up to 100 to quickly reproduce the problem.
This client runs inside eclipse.
After a few seconds requests stop to be passed to the cxf component.
As attachment there is the log of DeliveryChannelImpl with level
DEBUG. You can see that threads gradually stop to be notified and
all remain waiting.
This "freeze" is a problem we have in production with a few threads
and complex bpel processes.
Let me know if and how I can provide more infos about this problem.
Thanks, bye
Lorenzo
<servicemix-lock2.log.zip>
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
