ODE
  1. ODE
  2. ODE-644

INTERNAL ERROR: No ENTRY for RESPONSE CHANNEL [xy]

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.2, 2.0
    • Fix Version/s: 1.3.3, 2.0
    • Component/s: BPEL Runtime
    • Labels:
      None

      Description

      When a receive activity is repeated for the same partner link and operation (for example a pick activity inside of a while loop) the second message with often result inINTERNAL ERROR: No ENTRY for RESPONSE CHANNEL [xy] where xy ends up being the id of the old channel used for the first receive. In the JPA case this is because org.apache.ode.dao.jpa.CorrelatorDAOImpl removeLocalRoutes calls EntityManager remove but since it is using managed transactions these changes are not necessarily committed immediately.

      The mem dao should be unaffected by this, still need to test hibernate but it appears safe.

      1. responsechannel_hib_trunk.diff
        1 kB
        William McCusker
      2. responsechannel_hib_1x.diff
        1 kB
        William McCusker
      3. responsechannel_trunk_jpa.diff
        0.9 kB
        William McCusker
      4. responsechannel_jpa_1x.diff
        0.9 kB
        William McCusker

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            William McCusker
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development