[jira] Resolved: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL [xy]

["Alex Boisvert (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Boisvert resolved ODE-644.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0
                   1.3.3

Patches applied.  Thanks Bill!!

boisvert@sixtine:~/svn/ode/1.1$ svn commit -m "ODE-644: INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL [xy]"
Sending        dao-hibernate/src/main/java/org/apache/ode/daohib/bpel/CorrelatorDaoImpl.java
Sending        dao-jpa/src/main/java/org/apache/ode/dao/jpa/CorrelatorDAOImpl.java
Transmitting file data ..
Committed revision 802257.

boisvert@sixtine:~/svn/ode/trunk$ svn commit -m "ODE-644: INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL [xy]"
Sending        dao-hibernate/src/main/java/org/apache/ode/daohib/bpel/CorrelatorDaoImpl.java
Sending        dao-jpa/src/main/java/org/apache/ode/dao/jpa/CorrelatorDAOImpl.java
Transmitting file data ..
Committed revision 802258.


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