[ 
https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900404#action_12900404
 ] 

Thomas Haitzer commented on ODE-644:
------------------------------------

Hi,

I just got this error in ODE 1.3.4 by having a implemented a counter-example 
with exactly the pick activity inside a while loop.

Calling the method for the first time always works for me but when I try to 
call the same or another method with the same correlation set ... it will 
always result in this error:

 java.lang.IllegalArgumentException: INTERNAL ERROR: No ENTRY for RESPONSE 
CHANNEL

I am not very experienced with ODE, but since it works for the first call .. I 
see no point why it should not for the second.

The instance where it dispatches to is still ACTIVE.

I do think this bug is in some form still active.

Greetings ThoHai

> INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL [xy]
> --------------------------------------------------
>
>                 Key: ODE-644
>                 URL: https://issues.apache.org/jira/browse/ODE-644
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.3.2, 2.0
>            Reporter: William McCusker
>             Fix For: 1.3.3, 2.0
>
>         Attachments: responsechannel_hib_1x.diff, 
> responsechannel_hib_trunk.diff, responsechannel_jpa_1x.diff, 
> responsechannel_trunk_jpa.diff
>
>
> When a receive activity is repeated for the same partner link and operation 
> (for example a pick activity inside of a while loop)  the second message with 
> often result inINTERNAL ERROR: No ENTRY for RESPONSE CHANNEL [xy] where xy 
> ends up being the id of the old channel used for the first receive. In the 
> JPA case this is because org.apache.ode.dao.jpa.CorrelatorDAOImpl 
> removeLocalRoutes calls EntityManager remove but since it is using managed 
> transactions these changes are not necessarily committed immediately.
> The mem dao should be unaffected by this, still need to test hibernate but it 
> appears safe.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to