[ODE-125] ERROR Invalid Response State for mex on Invoke action

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0-incubating
• Component/s: BPEL Runtime
• Environment: WindowsXP; JDK 1.5; Tomcat 6.0.10
• Assignee: Matthieu Riou
• Reporter: Vipul Sabhaya
• Created: 25/Apr/07 23:06
• Updated: 29/May/07 22:05
• Resolved: 25/May/07 13:01

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!