Hi, At first sight it seems a bit odd as I'm not aware of any "classic" scenario that would put the alarm condition of an event handler on hold. But what are those 2 parallel long instructions exactly? Invocations? Maybe a bit more context would help me infer what the problem might be. Also can you reproduce it with a simple test process that I could use to see what's wrong?
Thanks, Matthieu On 3/28/08, Nowakowski, Mateusz <[EMAIL PROTECTED]> wrote: > > Hi all, > > I think that onAlarm doesn't work while performing flow instruction. > > I have for example onAlarm set for 5 seconds: > <bpel:eventHandlers> > <bpel:onAlarm> > <bpel:for>"PT5S"</bpel:for> > <bpel:scope> > <bpel:throw > faultName="tns:TimeoutFault"/> > </bpel:scope> > </bpel:onAlarm> > </bpel:eventHandlers> > > And I have > <bpel:flow> > ... Two parallel long instructions... > </bpel:flow> > > And I noticed that onAlarm is executed after <flow> instructions finish. > Not after 5 seconds. > > -- > Regards > > Mateusz Nowakowski >
