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
