ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amin Anjomshoaa <anjomsh...@ifs.tuwien.ac.at>
Subject Re: Re: Keeping the order of incoming events
Date Sun, 13 Apr 2008 15:17:34 GMT
Dear Alex

Thanks for your attention. Yes, the correlation is working correctly and 
request is forwarded to the correct instance. The issue is, when process 
is waiting for a specific message (let's say message B) and accidentally 
another message arrives, then ODE reacts with a timeout !
A real world example: in an e-commerce platform the delivery can not be 
started before payment. So if a delivery message arrives before payment, 
process should react with a exception.
I will wait for a while and if no solution is posted by other users, 
will file a bug.


Alex Boisvert wrote:
> On Fri, Apr 11, 2008 at 11:00 PM, Alex Boisvert <boisvert@intalio.com>
> wrote:
>> On Fri, Apr 11, 2008 at 5:13 PM, Amin Anjomshoaa <
>> anjomshoaa@ifs.tuwien.ac.at> wrote:
>>> I have a question regarding the events order in a business process. Lets
>>> say we have a process that should work as follows:
>>> receive <A> ..... receive <B> .... receive <C>
>>> Now consider at the beginning, when the process is waiting to receive A,
>>> an event of type C arrives. Apparently Apache ODE waits for a while and then
>>> returns a timeout. I would like to know if there is a solution to throw an
>>> exception when the appropriate event is not arrived?
>> Good question.  I don't know why Ode would wait.   Message C is presumed
>> to have some form of correlation to an instance and if that instance isn't
>> available, the engine should be able to tell immediately.  Smells like a
>> bug.  Can you open an issue with a test-case illustrating this?
> Hmmm, re-reading your email a second time it's not clear whether receive <A>
> is instantiating the process.  Are the instance and a matching correlation
> set available when message C arrives?
> alex

View raw message