Uploaded image for project: 'ODE'
  1. ODE
  2. ODE-552

Process instance did not continue after invoked process returned fault during P2P communication

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.3.2
    • 1.3.4
    • BPEL Runtime
    • None
    • Tomcat 6, Servicemix

    Description

      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.

      Attachments

        1. bpelex.zip
          3 kB
          Rafal Rusin
        2. bpelex-sa-1.0-SNAPSHOT.jar
          14 kB
          Rafal Rusin
        3. incorrectInternalCommunication.diff
          7 kB
          Rafal Rusin
        4. incorrectInternalCommunication-soapui-project.xml
          4 kB
          Rafal Rusin
        5. log-smx.txt
          0.9 kB
          Rafal Rusin
        6. log-tomcat.txt
          0.3 kB
          Rafal Rusin
        7. request.soap
          0.3 kB
          Rafal Rusin

        Activity

          People

            rrusin Rafal Rusin
            rrusin Rafal Rusin
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: