[ODE-1048] Disable MEX_MATCHER job

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.7, 1.4
• Component/s: BPEL Runtime
• Assignee: Sathwik
• Reporter: Sathwik
• Created: 05/Mar/16 05:41
• Updated: 28/Nov/17 07:56
• Resolved: 08/Jul/16 07:14

Description

MEX_MATCHER job is triggered after registering an Early arriving message.

Early arriving messages are normally picked up when the MATCHER job executes. MEX_MATCHER is an overhead and there is lot of contention seen between MATCHER and MEX_MATCHER jobs under load.

There is deadlock situation arising between MEX_MATCHER and MATCHER jobs running concurrently.

MEX_MATCHER
1) lockPrimieMessages (locks all records in BPEL_UNMATCHED using the mex)

MATCHER
1) findRoute (locks route in BPEL_SELECTOR based on single correlation key set canonical value)

MEX_MATCHER
2) tries to findRoute (locked by Matcher)

MATCHER
2) tries to dequeueMessage (locked by Mex_Matcher)

Results in a deadlock.

Possible solution to overcome this deadlock:
Move the dequeueMessage call above the findRoute call in matcherEvent.

This is a proposal to deactivate MEX_MATCHER jobs. Henceforth, MEX_MATCHER jobs will not be triggered after an early message is registered.

In case MEX_MATCHER is necessary, kindly revert the changes done in this ticket.

Issue Links

• is required by: ODE-1061 List of Bugs to be ported to trunk from 1.3.7