ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthieu Riou <matthieu.r...@gmail.com>
Subject Re: Correlation routing issue in ODE
Date Tue, 03 Feb 2009 15:33:58 GMT
On Tue, Feb 3, 2009 at 7:00 AM, Bill McCusker <wmccusker@parasoft.com>wrote:

> Has anyone else be able to reproduce this?
>

I'm not aware of the correlation having been recently broken, although I'm
not sure we have test cases for reply correlations. I'll give your process a
try today.

Matthieu


>
>
> Bill McCusker wrote:
>
>>   Hi,
>>
>>   Attached is a simple process that I am deploying to an ODE build off the
>> 1.X branch in tomcat and the resulting debugging logs. I invoke two
>> operations on the process, first the openAccount operation to start the
>> process which initiates a correlation set based on the reply to the initial
>> request using the ID part from the input message. I then invoke the
>> closeAccount operation to end the process. The trouble is the closeAccount
>> message is not being routed to the correct instance. About half the time ODE
>> finds no routes in the db and the message gets saved to the db instead of
>> being routed to the active instance. I am using the embedded derby database.
>> Tracking the debugging logging lead to
>> org.apache.ode.dao.jpa.CorrelatorDAOImpl.findRoute(CorrelationKeySet
>> correlationKeySet). At first I thought the cause was due to List.remove()
>> being called inside a for loop but that was not causing the problem I am
>> seeing, however attached is a patch to avoid possible bugs that it might
>> cause.  It turns out for some reason the Query in this method is returning
>> an empty list. I have not been able to figure out why. Any ideas? Thanks.
>>
>> Bill McCusker
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message