[
https://issues.apache.org/jira/browse/ODE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafal Rusin resolved ODE-550.
-----------------------------
Resolution: Cannot Reproduce
No process attached
> Correlated receive in parallel for-each loop produce exception with all
> backends
> --------------------------------------------------------------------------------
>
> Key: ODE-550
> URL: https://issues.apache.org/jira/browse/ODE-550
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.2
> Environment: JPA/Derby
> JPA/Oracle
> Hibernate/Oracle
> Reporter: Andi
>
> trying to get a relatively simple process which performs a correlated
> receive in parallel for-each loop (attached) - just the sweet spot for BPEL ;)
> I've tried with:
> - Derby/JPA - java.sql.SQLException: A lock could not be obtained due
> to a deadlock (full stack in earlier emails)
> - Hibernate/Oracle - the exception is below (hibernate 3.2.5/ oracle
> 10.2)
> - JPA / Oracle - This didn't produce exceptions, but it produced the
> following error, which killed the process instance...
> o 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.
> INFO - GeronimoLog.info(79) | ActivityRecovery: Registering activity 25,
> failure reason: org.apache.ode.bpel.iapi.BpelEngineException: Engine
> requested response
> while the message exchange hqejbhcnphr426192c3r3o was in the state
> COMPLETED_OK on channel 45
> Attached are:
> - BPEL process files
> - Log from Hibranate/Oracle
> A few more notes:
> - the process is defined with an input message accepting anyType (for ease
> of playing around). Request messages do need to look like the SOAP envelope
> below.
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:urn="urn:bpel:BpelMock">
> <soapenv:Header/>
> <soapenv:Body>
> <urn:BPELInRequest>
> <Part1>
> <priority>2</priority>
> <command>5</command>
> <requestId>REQUEST_ID_141</requestId>
> <current-priority></current-priority>
> <message-id>12</message-id>
> <command-data><data>some random stuff</data></command-data>
> </Part1>
> </urn:BPELInRequest>
> </soapenv:Body>
> </soapenv:Envelope>
> - The "requestId" element content is used a part of the correlation key
> (which allows executing multiple processes).
> - The process invokes a 1-way operation and attempts to correlate a
> reciprocal invocation which echo's the data..It seems that that's where the
> issue occurs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
