-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I have the following problem:

I get the error message below when running through a while containing a
pick (and in a corresponding onMessage another receive). I'm using
explicit correlation.
In the first run of the while loop everything happens as expected. In
the second one, I get the error below. It seems that ODE saved the
message of the first run, detects the "duplicate" in the second run  and
therefore prevents me from executing this (second) while loop run
(because it supposes that my message exchange is in an inconsistent
state). Is that correct?

If so, is there a possibility to disable this feature?

Does anybody have an idea about that or what could be done to avoid this
problem?

Any help is appreciated!

Thanks,
Christoph

Matcher event for iid 3677
2008-08-31 22:00:15,366 :: DEBUG - GeronimoLog.debug(66) | MatcherEvent
handling:

correlatorId=114.deliver_BTA_3A4_RequestPurchaseOrder_Response,
ckey={CorrelationKey setId=107, values=[39]}

2008-08-31 22:00:15,376 :: DEBUG - GeronimoLog.debug(66) | MatcherEvent
handling: found matching message in DB (i.e. message arrived before
<receive>)

2008-08-31 22:00:15,377 :: DEBUG - GeronimoLog.debug(66) | SELECT: 703:
matched to MESSAGE [EMAIL PROTECTED]
on CKEY {CorrelationKey setId=107, values=[39]}

2008-08-31 22:00:15,378 :: FATAL - GeronimoLog.fatal(116) | Engine
requested response while the message exchange hqejbhcnphr3k0vanale3r was
in the state RESPONSE

2008-08-31 22:00:15,378 :: ERROR - GeronimoLog.error(104) | The message
exchange seems to be in an unconsistent state, you're probably missing a
reply on a request/response interaction.

2008-08-31 22:00:15,379 :: DEBUG - GeronimoLog.debug(66) | initializing
partner {PartnerLinkInstance
partnerLinkDecl=OPartnerLink#114,scopeInstanceId=20507}  sessionId to
hqejbhcnphr3k0vanale08

2008-08-31 22:00:15,380 :: INFO - GeronimoLog.info(79) |
ActivityRecovery: Registering activity 390, failure reason:
org.apache.ode.bpel.iapi.BpelEngineException: Engine requested response
while the message exchange
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIuwTF0Do4wUHmzBsRArPzAJ9O102a9GjnZAmjZhcygKoYrHylZACgqcCY
Yrgh1gHAq1xEa/Le/QLuw78=
=kxSY
-----END PGP SIGNATURE-----

Reply via email to