[
https://issues.apache.org/jira/browse/ODE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Boisvert updated ODE-552:
------------------------------
Fix Version/s: (was: 1.3.3)
1.3.4
> 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
> 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.
-
You can reply to this email to add a comment to the issue online.
