It seems there is a problem here ;)
Each seda queue / component should have its own thread pool and not use
only one common thread pool, else deadlocks may happen as you just
experienced. Could you raise a JIRA please, it should be fixed asap.
On 8/3/06, anandhs <[EMAIL PROTECTED]> wrote:
I tried to play with some of these, but it did not make a difference to
our
scenario.
We have 2 services A and B. A makes sync requests to B. We have a JMS
client
that feeds requests to A and that triggers a sync request to B. We are
trying to push some 5000 requests (not sequential). Now
With st flow - A gets all the responses from B and we are good
with Seda flow - A gets some responses from B (sometimes none) and
then all the threads are blocked on syncsend(), looks like B has no
threads
to service requests.
with JMS flow ( A and B on different VMs), we see the similar
behavior
as with seda flow
With async requests everything works just fine. We have tried increasing
seda capacity and workmanager thread count, that did not help.
So what should we be configuring?
Thanks
Anand
--
View this message in context:
http://www.nabble.com/Tuning-service-mix-tf2017005.html#a5640667
Sent from the ServiceMix - User forum at Nabble.com.
--
Cheers,
Guillaume Nodet
