You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "William McCusker (JIRA)" <ji...@apache.org> on 2009/08/07 17:41:14 UTC
[jira] Created: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
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
Attachments: responsechannel_jpa_1x.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.
[jira] Commented: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "Thomas Haitzer (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "William McCusker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William McCusker updated ODE-644:
---------------------------------
Attachment: responsechannel_trunk_jpa.diff
jpa patch for trunk
> 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
> Attachments: 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.
[jira] Commented: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "Phil (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868539#action_12868539 ]
Phil commented on ODE-644:
--------------------------
Hi,
I just stumpled upon this issue using ODE 2.0 beta2. So I guess this not fixed there yet, or have I found a new problem?
In my case, the error occurs after a receive from the outside, but unfortunately not always. A second message with the same content then usually works.
DEBUG - GeronimoLog.debug(66) | handleWorkEvent: MYROLE_INVOKE event for process instance 152
FATAL - GeronimoLog.fatal(116) | INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL 180
ERROR - GeronimoLog.error(108) | Work for instance {http://www.example.com/exampleProcess}ExampleProcess-1#152 in thread Thread[ODEServerImpl-10,5,main] resulted in an exception.
org.apache.ode.bpel.iapi.BpelEngineException: java.lang.IllegalArgumentException: INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL 180
at org.apache.ode.bpel.engine.Contexts.execTransaction(Contexts.java:92)
The instance mentioned (152) is in fact the wrong one; it has already terminated.
What is the status of this bug?
Thanks.
Phil
> 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.
[jira] Commented: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "William McCusker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740763#action_12740763 ]
William McCusker commented on ODE-644:
--------------------------------------
I have not been able to reproduce this issue using hibernate with the embedded derby database, however the theory is the same as for jpa. Hibernate does not guarantee when statements as flushed which is most likely why this is difficult to reproduce. Explicitly calling Session.flush should ensure that old routes are not reused when they are scheduled to be removed.
> 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
> Attachments: responsechannel_hib_1x.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.
[jira] Updated: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "William McCusker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William McCusker updated ODE-644:
---------------------------------
Attachment: responsechannel_hib_trunk.diff
> 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
> 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.
[jira] Updated: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "William McCusker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William McCusker updated ODE-644:
---------------------------------
Attachment: responsechannel_hib_1x.diff
> 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
> Attachments: responsechannel_hib_1x.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.
[jira] Resolved: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "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.
[jira] Updated: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "William McCusker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William McCusker updated ODE-644:
---------------------------------
Attachment: responsechannel_jpa_1x.diff
patch for 1x jpa
> 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
> Attachments: responsechannel_jpa_1x.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.
[jira] Commented: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "William McCusker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740664#action_12740664 ]
William McCusker commented on ODE-644:
--------------------------------------
Looking back in the user mailing list I see someone did report seeing this same issue with hibernate.
> 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
> Attachments: 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.
[jira] Commented: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "William Liu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853702#action_12853702 ]
William Liu commented on ODE-644:
---------------------------------
Hi, All!
Sorry to bother again! But have this bug been fixed in 1.3.3? I'm still facing the same error just in the scenario as William described: 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]
To fix this bug, do I need to download 1.x sources and apply your patches and build ODE myself?
Thank you very much!
> 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.
[jira] Commented: (ODE-644) INTERNAL ERROR: No ENTRY for RESPONSE
CHANNEL [xy]
Posted by "William McCusker (JIRA)" <ji...@apache.org>.
[ 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.