ODE
  1. ODE
  2. ODE-125

ERROR Invalid Response State for mex on Invoke action

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0-incubating
    • Component/s: BPEL Runtime
    • Labels:
      None
    • Environment:
      WindowsXP
      JDK 1.5
      Tomcat 6.0.10

      Description

      A Invoke action generates error on a response, causing TimeoutException

      ERROR - BpelRuntimeContextImpl.invocationResponse2(976) | Invalid response state for mex 1dk5h7um9k2li9897tk4q1: ASYNC
      DEBUG - BpelRuntimeContextImpl.execute(830) | Setting execution state on instance 322
      DEBUG - InstanceLockManager.unlock(88) | Thread[pool-3-thread-3,5,main]: unlock(iid=322)
      ERROR - ODEService.onAxisMessageExchange(154) | Timeout or execution error when waiting for response to MEX {MyRoleMex#1dk5h7um9k2li9897tk4pq [Client 1dk5h7um9k2li9897tk4pp] calling

      {http://wsdl.test.com/engine-process.wsdl}

      EngineProcess1Service.begin(...)} java.util.concurrent.TimeoutException: Message exchange org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture@51672e timed out when waiting for a response!

      1. TransformerService.wsdl
        6 kB
        Vipul Sabhaya
      2. TestServiceImpl.java
        0.3 kB
        Vipul Sabhaya
      3. TestService.java
        0.2 kB
        Vipul Sabhaya
      4. EngineProcess1.wsdl
        6 kB
        Vipul Sabhaya
      5. EngineProcess1.bpel
        4 kB
        Vipul Sabhaya
      6. deploy.xml
        1 kB
        Vipul Sabhaya

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Matthieu Riou
            Reporter:
            Vipul Sabhaya
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development