Can you also create a Jira Issue with your process and the web service you're invoking? It's probably a different problem in that case.
Thanks, Matthieu On 4/25/07, René Bos <[EMAIL PROTECTED]> wrote:
I have the error without a previous error.. René -----Original Message----- From: Matthieu Riou [mailto:[EMAIL PROTECTED] Sent: donderdag 26 april 2007 5:02 To: ode-user@incubator.apache.org Subject: Re: Invalid response state for mex: ASYNC As I replied in another thread, this probably comes from a previous error during invocation. Could you check your logs to make sure that you don't have a previous error? For example something like: ERROR - ExternalService$1.afterCompletion(146) | Error sending message to Axis2 for ODE mex {PartnerRoleMex#hqejbhcnphr280ets66rl3 [PID { http://bpel.test.com/process}EngineTest-1] calling [EMAIL PROTECTED](...)} org.apache.axis2.AxisFault: A header representing a Message Addressing Property is not valid and the message cannot be processed at org.apache.axis2.description.OutInAxisOperationClient.execute( OutInAxisOperation.java:308) at org.apache.ode.axis2.ExternalService$1.afterCompletion( ExternalService.java:136) ..... Thanks, Matthieu On 4/25/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: > > Hi, > > It seems the process isn't getting a reply properly for some reason, > however I couldn't reproduce this with our scenarios. Do you have something > we could use to reproduce it? If so, please create a Jira issue and attach > your process / service. > > Thanks, > Matthieu > > On 4/25/07, René Bos <[EMAIL PROTECTED]> wrote: > > > > I just noticed this error (after the test with the webservice online..) > > after a while: > > > > ERROR - ODEService.onAxisMessageExchange(155) | Timeout or execution > > error when waiting for response to MEX {MyRoleMex#-bpgd3nvdqfl8uj5lwddddk > > [Client -bpgd3nvdqfl8uj5lwddddl] calling { > > http://RemoveObject.wsdl}RemoveObjectService.initiate(...)} > > java.util.concurrent.TimeoutException: Message exchange > > [EMAIL PROTECTED] when waiting for a response! > > ERROR - ODEService.onAxisMessageExchange(156) | > > java.util.concurrent.TimeoutException: Message exchange > > [EMAIL PROTECTED] when waiting for a response! > > > > René > > > > -----Original Message----- > > From: René Bos [mailto:[EMAIL PROTECTED] > > Sent: woensdag 25 april 2007 10:59 > > To: ode-user@incubator.apache.org > > Subject: RE: Invalid response state for mex: ASYNC > > > > > > As I said in a different thread, I have the same problem as you Jan. > > > > I noticed that the problem also occurred when the affecting webservice > > if offline! So I attached my process with the logs of an online (internal) > > webservice, and one when it was offline... I hope you can find something! > > Even as you don't have the webserice, I think you can debug it because the > > problem also occurs when it is offline.. > > > > At this time I can't invoke anything from any of my processes.. So I > > hope this can be figured out :) > > > > René > > > > -----Original Message----- > > From: Alex Boisvert [mailto: [EMAIL PROTECTED] > > Sent: maandag 16 april 2007 17:13 > > To: ode-user@incubator.apache.org > > Subject: Re: Invalid response state for mex: ASYNC > > > > > > On 4/13/07, Jan Loewe < [EMAIL PROTECTED]> wrote: > > > > > > Hi Alex, > > > > > > Am Donnerstag, den 12.04.2007, 15:48 -0700 schrieb Alex Boisvert: > > > > This is odd. Did you try turning on DEBUG logging for > > org.apache.ode? > > > > There are a couple of debug messages in the ExternalService class > > that > > > > should give you a better idea of what's happening. > > > I did, but this did not help. I just (accidentally) figured out that > > > this also happens if the external service is unavailable. > > > > > > Am I right, that those mexids flying around identify a connection > > > between endpoints? So if MessageExchangeImpl has a MessageExchangeDAO > > > with a certain id assigned and there is a response attached to it, the > > > MessageExchangeDAO retrieved later via > > > ProcessInstanceDAO.getConnection().getMessageExchange should have the > > > same response attached, if I it has the same id? > > > > > > Yes, you're correct. A message exchange groups together related > > messages > > (of the same message exchange pattern), such as a request and response, > > or > > request and associated fault. The MEX are persisted, as well as the > > messages, so you should be able to retrieve them later on using the same > > MEX > > id. > > > > If you have a way to reproduce this, such as a sample deployment > > package, > > I'd be happy to debug it. > > > > cheers, > > alex > > > >
