I would be surprised if this was a ServiceMix integration issue; it's most likely an issue in the BPEL runtime if it exists.
If you can create a Jira issue that demonstrates the behavior, we'll look into it. thanks! alex On Tue, Apr 1, 2008 at 2:15 AM, Nowakowski, Mateusz < [EMAIL PROTECTED]> wrote: > 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. > > -- > Regards > Mateusz Nowakowski > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Matthieu Riou > Sent: Friday, March 28, 2008 4:11 PM > To: [email protected] > Subject: Re: onAlarm doesn't work for flows ?? > > 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 > > >
