[
https://issues.apache.org/jira/browse/ODE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vittorio Ballestra updated ODE-417:
-----------------------------------
Summary: MessageExchange Failure not handled correctly (was:
MessageExchange Failure not handled correctly with async when
org.apache.ode.jbi.sendSynch=false)
In any case in the logs you can see this message :
BpelRuntimeContextImpl 1038 | Invalid response state for mex
hqejbhcnphr3qwggdfuoc6: ASYNC
> MessageExchange Failure not handled correctly
> ----------------------------------------------
>
> Key: ODE-417
> URL: https://issues.apache.org/jira/browse/ODE-417
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: SERVICEMIX + ODE-JBI-1.2-SNAPSHOT WITH EXTERNAL
> DATASOURCE (MySql)
> Reporter: Vittorio Ballestra
>
> Way to reproduce this behaviour:
> 1) create a simple process that makes an InOut exchange with some service on
> a JBI bus.
> 2) let this service reply with an error (not a fault)
> If sendSync is true the exchange is set in FAILURE state.
> If sendSync is false the exchange is left in ASYNC state.
> Stepping in debug mode you can see that the exchange is set in FAILURE state
> but this change is not persisted to database. When the async processor
> reloads the MessageExchange from DB it is still in ASYNC state.
> Tried a naive patch that makes a "flush" of the entity-manager just after
> setting the state to FAILURE but it hangs. Still indagating.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
