ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafal Rusin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ODE-552) Process instance did not continue after invoked process returned fault during P2P communication
Date Mon, 16 Mar 2009 11:22:50 GMT

     [ https://issues.apache.org/jira/browse/ODE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rafal Rusin updated ODE-552:
----------------------------

    Attachment: bpelex-sa-1.0-SNAPSHOT.jar
                bpelex.zip
                incorrectInternalCommunication-soapui-project.xml

> 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.1
>         Environment: Tomcat 6, Servicemix
>            Reporter: Rafal Rusin
>             Fix For: 1.3.1
>
>         Attachments: bpelex-sa-1.0-SNAPSHOT.jar, bpelex.zip, incorrectInternalCommunication-soapui-project.xml
>
>
> 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.


Mime
View raw message