ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William McCusker (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL [xy]
Date Fri, 07 Aug 2009 22:31:14 GMT

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

William McCusker commented on ODE-644:
--------------------------------------

Welcome.

> 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.


Mime
View raw message