Issues with AQ Adapter in BPEL

Question

Hi,
I am currently using SOA suite 10g and my BPEL process dequeues from AQ Adapter the message and continues with the BPEL Flow.Currently I have a PL/SQL block to enqueue into the custom AQ Table.I see that after I enqueue the messages are present in the queue table and after sometime it disapppears.But the instance is not created in BPEL console for the record created in the custom queue table.Sometimes the BPEL instance is created in BPEL console.Kindly let me know your inputs on where these messages must be disappearing without showing up in the BPEL Console?
Also I have another clarification:Is there any setting in BPEL wherein I can dequeue only few threads from the queue to prevent overloading BPEL from creating many concurrent threads at the same time.
Thanks & Regards,
Anand

Answer 1

Anand,
Your transaction is rolling back because of some fault with the PLSQL call that you are making.
1. Try to put a catch or catch all block - that catches the fault instead of rolling back the instance.
2. You do not need a rejectMessageHandler in this case because the message will already be in Invoke Message table. You should see the message in Recovery(Invokes) in these scenarios and you should be able to recover from there.
Regarding your query regarding threads:
By default there will be only one thread per node that dequeues message from queue, but the scope of that threads ends once the message is placed in invoke message table. Once the message reach invoke message - It's the Invoker thread (Part of Invoke Thread Pool) who does the processing(Again there is a in memory queue in middle, but for the high level, I am ignoring it).
If you really wanted to single thread it, Make the Dequeue synchronous to the queue(by setting deliverypersistpolicy to off.immediate) and set adapter.aq.dequeue.threads to 1.
Hope it helps!!