ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nowakowski, Mateusz" <Mateusz.Nowakow...@sabre-holdings.com>
Subject RE: onAlarm doesn't work for flows ??
Date Tue, 01 Apr 2008 09:15:30 GMT
Yes, these instructions are invocations.

I tested it also without flow activity and bpel returns after invoke
activity, not after delay time. 

I used ode in async mode and under service mix.

I think it may be ServiceMix integration issue.

Mateusz Nowakowski
-----Original Message-----
From: matthieu.riou@gmail.com [mailto:matthieu.riou@gmail.com] On Behalf
Of Matthieu Riou
Sent: Friday, March 28, 2008 4:11 PM
To: user@ode.apache.org
Subject: Re: onAlarm doesn't work for flows ??


At first sight it seems a bit odd as I'm not aware of any "classic"
that would put the alarm condition of an event handler on hold. But what
those 2 parallel long instructions exactly? Invocations? Maybe a bit
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


On 3/28/08, Nowakowski, Mateusz <Mateusz.Nowakowski@sabre-holdings.com>
> 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
> Not after 5 seconds.
> --
> Regards
> Mateusz Nowakowski

View raw message