You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Rafal Rusin (JIRA)" <ji...@apache.org> on 2010/04/14 00:39:50 UTC
[jira] Resolved: (ODE-552) Process instance did not continue after
invoked process returned fault during P2P communication
[ https://issues.apache.org/jira/browse/ODE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin resolved ODE-552.
-----------------------------
Resolution: Fixed
Applied in commit APACHE_ODE_1.X@910573
> Process instance did not continue after invoked process returned fault during P2P communication
> -----------------------------------------------------------------------------------------------
>
> Key: ODE-552
> URL: https://issues.apache.org/jira/browse/ODE-552
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.2
> Environment: Tomcat 6, Servicemix
> Reporter: Rafal Rusin
> Assignee: Rafal Rusin
> Fix For: 1.3.4
>
> Attachments: bpelex-sa-1.0-SNAPSHOT.jar, bpelex.zip, incorrectInternalCommunication-soapui-project.xml, incorrectInternalCommunication.diff, log-smx.txt, log-tomcat.txt, request.soap
>
>
> There are 2 processes
> A:
> invoke B
> B:
> throw fault
> A stops and logs show something like this:
> 11:49:34,708 | WARN | pool-4-thread-4 | OdeService | org.apache.ode.jbi.OdeService 187 | Ignoring unknown async reply: {MyRoleMex#hqejbhcnphr44dfq3nre56 [Client hqejbhcnphr44dfq3nre55] calling {http://ftang.org/hello}HelloWorld2.process(...)}
> I'm providing reproduction processes for JBI & Tomcat.
--
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