Aborting Processes In Bpm

Question

Hello,
We have been using Oracle BM Studio(Version: 10.3.1.0, Build: #94375 to be precise). I have a problem I'd like to share, I have been searching the forums, but could not find a solution to this. I have a grab activity, which grabs a parent instance. When the instance is grabbed, I am trying to kill te child processes of it one by one, via some notification wait at the child process, with the optional method of the grab activity. (The child pocess does the same job, if needed). But whatever I did, I could not get the message to be receieved at the child process. There is no exception thrown, I keep sending the message by 'Notification.send', but nothing happens. I used different versions of Notification.send with different number of parameters, I used the external, parent, internal, child approaches in the message wait activity. But I still could not succeed in making the child process be aborted. I dont want the parent of all processes to be aborted, it must end normally, but the children be killed when the grabbed parent instance is routed. Below is a portion of my code that I have been playing with for a while. Any idea what I might be doing wrong?
if(children != null && children.keys != null) {
     foreach (child in children.keys) {
          if( !children[child].indexOf(SOME_CONSTANT) == 0 ) {
               try{
                    String instanceId = children[child].split(delim : "@")[0];
                    Notification.send(instanceId, "NotificationWaitSelfAbortParent", "In", null);
                    '5s'.sleep();
                    Notification.send(children[child], "NotificationWaitSelfAbortParent", "In", null);
                    }catch(Throwable t){
                              t.printStackTrace();
                              throw t;
Regards
Edited by: user10745623 on 27.Ara.2011 05:40
Edited by: user10745623 on 27.Ara.2011 05:41

Answer 1

Hi,
The other way didn't work because you are using an optional method. Optional methods are read-only (that is to say, that the transaction will be rolled back). When you send the notification using the Notification.send component, the notification and child instance processing is getting done in the same transaction.
I guess that now you are using PAPI to grab the child instances. PAPI components open a new transaction per operation. Therefore, PAPI invocations will succeed even if you are invoking them in a read-only method.
Hope this helps,
Ariel