Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.4.3
  • Fix Version/s: 3.0.1
  • Component/s: Modules: BPM / Rules
  • Labels:
    None
  • Environment:

    JBPM

  • User impact:
    High
  • Similar Issues:
    None

Description

Exception when using Global Receiver in BPM Connector

Below is the stack trace of the error,

04/17/08 18:59:01.508 [ERROR] GraphElement action threw exception: No corresponding receiver found for processName = QueryLimits, processId = 1
org.mule.config.ConfigurationException: No corresponding receiver found for processName = QueryLimits, processId = 1
at org.mule.providers.bpm.ProcessConnector.generateMessage(ProcessConnector.java:226)
at org.mule.providers.bpm.jbpm.MuleMessageService.generateMessage(MuleMessageService.java:54)

After looking into the code, I feel that there is any issue in registering the Global Receiver.

In registerListener(...) method of AbstractConnector,
Object receiverKey = getReceiverKey(component, endpoint);
receiverKey for endpoint="bpm://*" is returning empty String,
So the EMPTY STRING is stored as Key for global receiver in receivers Hashmap of ProcessConnector.

But in toUrl(..) method of ProcessConnector, the below code shows that you are using "bpm://*" as receiver key for retrieving the BPM's Global receiver.
else if (isAllowGlobalReceiver())

{ return GLOBAL_RECEIVER; }

So there is a mismatch in receiver key for BPM's Global Receiver.

Activity

Hide
Travis Carlson added a comment -

jBPM can be used as a component as of 3.0.1, therefore the global receiver is no longer relevant.

Show
Travis Carlson added a comment - jBPM can be used as a component as of 3.0.1, therefore the global receiver is no longer relevant.

People

Vote (1)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
2h
Original Estimate - 2 hours
Remaining:
2h
Remaining Estimate - 2 hours
Logged:
Not Specified
Time Spent - Not Specified