[
https://issues.apache.org/jira/browse/ODE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728819#action_12728819
]
William McCusker commented on ODE-634:
--------------------------------------
1.) This was caused by the message route not being persisted to the back end.
Explicitly calling persist of the message route being created by
org.apache.ode.dao.jpa.CorrelatorDAOImpl addRoute fixed this problem.
2.) The conflicting receive fault was trigger by a race condition between
processing the event handler's associated scope and the select runnable. If the
scope completes first the is no problem however often times the select runnable
would be processed first and attempt to register a receiver for the same
partner link, operation and message exchange resulting in a conflicting
receive. By having event handlers wait runnable move it's out standing request
to a "waiting to reply" state the select runnable can register that it waiting
for a new request.
I will attach the patch I have for the 1.x branch and then will look into
porting the patch to 2.x
> Event Handles not working
> -------------------------
>
> Key: ODE-634
> URL: https://issues.apache.org/jira/browse/ODE-634
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.2, 1.3.3, 2.0
> Reporter: William McCusker
>
> When attempting to send a message to an event handler one of two
> possibilities occur:
> 1.) Event Handler fails to receive message.
> 2.) message is receive but conflicting receive fault triggered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
