You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2010/04/13 14:29:36 UTC
[jira] Updated: (ODE-417) MessageExchange Failure not handled
correctly (with OPENJPA)
[ https://issues.apache.org/jira/browse/ODE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-417:
---------------------------------
Fix Version/s: 1.3.5
> MessageExchange Failure not handled correctly (with OPENJPA)
> ------------------------------------------------------------
>
> Key: ODE-417
> URL: https://issues.apache.org/jira/browse/ODE-417
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.2
> Environment: SERVICEMIX + ODE-JBI-1.2-SNAPSHOT WITH EXTERNAL DATASOURCE (MySql)
> Reporter: Vittorio Ballestra
> Fix For: 1.3.5
>
> Attachments: failuretest-sa-1.0-SNAPSHOT.jar, patch.txt, sample-failing-sa.tar.bz2
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira