Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 3.0.1
-
Fix Version/s: 3.1.3 (EE only)
-
Component/s: Core: Services
-
Labels:None
-
User impact:High
-
Configuration:
-
Similar Issues:None
Description
As reported on the user forum, the first configuration (flow+service) works but not the second (flow+flow), which seems due to the fact flows don't terminate with a message processor that would use the endpoint's connector's replyTo handler.
Any chance to have this fixed? Users are forced to workarounds like manually adding the ReplyToPropertyRequestReplyReplier to all their flows, which will become a maintenance issue when upgrading to a Mule version with this bug fixed.