Flow should be ready to process messages as soon as the message processors are started

Details

  • User impact:
    Very High
  • Log Output:
    Hide
    Root Exception stack trace:
    org.mule.api.lifecycle.LifecycleException: Cannot process event as "SimpleFlowConstruct{MainFlow}" is stopped
    at org.mule.lifecycle.processor.ProcessIfStartedMessageProcessor.handleUnaccepted(ProcessIfStartedMessageProcessor.java:42)
    at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:48)
    at org.mule.construct.AbstractFlowConstruct$1$1.process(AbstractFlowConstruct.java:111)
        + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
    Show
    Root Exception stack trace: org.mule.api.lifecycle.LifecycleException: Cannot process event as "SimpleFlowConstruct{MainFlow}" is stopped at org.mule.lifecycle.processor.ProcessIfStartedMessageProcessor.handleUnaccepted(ProcessIfStartedMessageProcessor.java:42) at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:48) at org.mule.construct.AbstractFlowConstruct$1$1.process(AbstractFlowConstruct.java:111)     + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
  • Similar Issues:
    None

Description

A flow contains basically a message source and a message processor.
Flow.start requires to start the message processor first and then the message source. Flow is not fully started until all both components are started.
There are situations using a composite source, when the message source is not fully started (ex: using a composite source with two endpoint, one endpoint is started fast but not the other one). If the started endpoint receives a message before the second endpoint is started you will get a lifecycle exception because the flow is not started yet.

Real use case: having a composite source with tow JMS endpoints, the first one having messages already in the queue before starting mule.

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: