It would defintiely be something that can cause problems.
We are currently trying to resolve this. It seems to rear
it's head (SM-512) on Windows, more than Linux, this has
me baffled
servicemix-bpe ... JbiInvokeAction only ever sends out a sendSync()
when invoking a partner (JBI Component).
The BPEL spec discussed correlation-sets as method of performing async
calls.
We can see that <flows> and <sequences> control the threading of
servicemix-bpe
but because there is a sendSync for every message going out, it means
the threadpool
can get eaten up pretty quickly.
my 2 cents.
Guillaume Nodet wrote:
SM-512 is a pretty big issue, but it does not have by itself any solution
(see my comment in JIRA).
However, SM-521 could be implemented to be able to easily tune thread
pools
and queue sizes to
avoid deadlocks. Though it may require quite an amount of
refactoring, i'm
wondering if we should
implement it for 3.0 ?
