Esb parallel processing problems with jms adapter and bpel

Question

Hi,
I have esb project which dequeues from a jms adapter and then the esb router calls a bpel process. This bpel process takes about 10 seconds. The first step this bpel does is to return true ( to the client) to the esb router so the ESB thinks he is ready. This does not work.
Now if I use in the esb router asyn routing rule to the bpel ws then the esb dequeus all the messages from the queue. All the esb entries are green. But the esb starts one for one the bpel process and then updates the esb entry with a new start time ( very strange) .
If I use a sync routing rule then it dequeues and call the bpel process one for one.
How I can parallel proces the jms messages ,because I have 2 quad cores cpu's . Async routing rules looks like the solution.
How can the esb detects the bpel is still running even with the first action in bpel is to return true. I expected when the esb retrieves true from the bpel ws it ends the current esb entry and goes on with the next. So the total esb time takes a few seconds and not so long as the last the bpel proces finishes.
And why is he updating the starting time.
Thanks Edwin
Message was edited by:
biemond

Answer 1

I have esb project which dequeues from a jms adapter
and then the esb router calls a bpel process. This
bpel process takes about 10 seconds. The first step
this bpel does is to return true ( to the client) to
the esb router so the ESB thinks he is ready. This
does not work. I am not sure if it can ever work, if you reply and then still proceed with your BPEL process.
Here is something I would like to suggest:
Can you try ESB -- (sync) --> BPEL, where BPEL process itself is Async. In that case, esb will consume all the messages very fast and BPEL will get that message and put in Delivery Queue and reply back to ESB. Now BPEL will process them simultaniously based Receiver/Worker threads defined in your env.
HTH,
Chintan