You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "René Bos (JIRA)" <ji...@apache.org> on 2007/05/25 12:18:16 UTC
[jira] Commented: (ODE-125) ERROR Invalid Response State for mex on
Invoke action
[ https://issues.apache.org/jira/browse/ODE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499022 ]
René Bos commented on ODE-125:
------------------------------
This has been fixed for me some time ago.
> ERROR Invalid Response State for mex on Invoke action
> -----------------------------------------------------
>
> Key: ODE-125
> URL: https://issues.apache.org/jira/browse/ODE-125
> Project: Ode
> Issue Type: Bug
> Components: BPEL Runtime
> Environment: WindowsXP
> JDK 1.5
> Tomcat 6.0.10
> Reporter: Vipul Sabhaya
> Assigned To: Matthieu Riou
> Attachments: deploy.xml, EngineProcess1.bpel, EngineProcess1.wsdl, TestService.java, TestServiceImpl.java, TransformerService.wsdl
>
>
> 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!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.