X

Tackling "Failed to evaluate correlation query"

Ramkumar Menon
Director, Product Strategy

Problem observed on BPEL PM 10.1.3.3.

I developed a simple BPEL process that uses BPEL correlation to receive callbacks into the process.

For this purpose, I altered the process WSDL to add one more operation.

The initiating operation was named "processOrder". I decided to name the callback operation as "processOrderCallback".

I promptly defined two properties on the correlation set and provided aliases for both for the invocation and callback messages.

When I invoke the process, it throws up a CubeException and goes to recovery mode.

Why? Possibly because the callback operation name is a "superstring" of the invocation operation name.

When I looked at the logs, I could see that the engine was trying to evaluate the correlation query for the callback on the initiating message.

What I did next - just renamed the operation to "receiveOrderCallback" and re-ran the instance.

Bingo! - it worked.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.