On Tue, Jan 6, 2009 at 12:06 AM, Rosalin Pattnaik < [email protected]> wrote:
> Hi, > > I tried even with ode 1.2 version..but it didnt work. > This has been fixed in the 1.X branch but hasn't been released yet. Matthieu > > Regards, > Rosalin > > > On Tue, Jan 6, 2009 at 11:30 AM, Rosalin Pattnaik < > [email protected]> wrote: > >> Hi Matthieu, >> >> Can you please tell me what the fix was or point me to the bug no. for >> which this was fixed? >> I am using 1.1 , released version >> >> Thanks, >> Rosalin >> >> >> On Mon, Jan 5, 2009 at 9:25 PM, Matthieu Riou <[email protected]>wrote: >> >>> Hi Rosalin, >>> >>> Which version of ODE are you using? I fixed something like that some time >>> ago on the 1.X branch but it hasn't been released yet. >>> >>> Thanks, >>> Matthieu >>> >>> On Thu, Jan 1, 2009 at 11:19 PM, Rosalin Pattnaik < >>> [email protected]> wrote: >>> >>> > If we have bpel extension for retry on timeout with an invoke action , >>> but >>> > the ode crashes before the timeout has occured .And thus there is >>> neither a >>> > timeout exception nor has it received the response which might have >>> been >>> > lost in the time it was down .When the ode restarts which of the >>> following >>> > shd occur: >>> > >>> > >>> > - The ode resumes from the invoke state ,waits for the response , >>> > timesout and retries, get the response and proceed normally. >>> > - The process is not resumed. >>> > >>> > In my case the process is not resumed in case timeout exception has not >>> > occured , but in case the timeout has occured and then the ode crashes >>> then >>> > it retries gets the response and then completes succesfully. >>> > >>> > PFA the Bpel process and the external webservice impl. >>> > >>> > Regards, >>> > Rosalin >>> > >>> >> >> >
