org.mule.api.lifecycle.LifecycleException: Cannot process event as "__intercepted_chain_flow_" is stopped

MuleSoft JIRA | Evangelina Martinez Ruiz Moreno | 11 months ago
  1. 0

    Currently the APIKit does not support more than one API Proxy configuration in the same application. This is because for each configuration is creating a flow named "__intercepted_chain_flow_". Since the last one overrides the existing one, only the last proxy to be initialized will work. Steps to reproduce: 1) Add two proxy configurations in the same application Expected behavior: - The two proxies working as expected Current behavior: - On starting the application, a warning saying: {code} WARN 2015-09-01 21:56:57,613 [Mule.app.deployer.monitor.1.thread.1] org.mule.config.spring.SpringRegistry: Spring registry already contains an object named '__intercepted_chain_flow_'. The previous object will be overwritten. {code} And when doing a request, the following error: {code} ERROR 2015-09-01 21:56:59,132 [[proxy].connector.http.mule.default.receiver.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Cannot process event as "__intercepted_chain_flow_" is stopped Code : MULE_ERROR-70167 -------------------------------------------------------------------------------- Exception stack is: 1. Cannot process event as "__intercepted_chain_flow_" is stopped (org.mule.api.lifecycle.LifecycleException) org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor:440 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/lifecycle/LifecycleException.html) -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.api.lifecycle.LifecycleException: Cannot process event as "__intercepted_chain_flow_" is stopped at org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor.handleUnaccepted(AbstractPipeline.java:440) at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:45) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** {code}

    MuleSoft JIRA | 1 year ago | Evangelina Martinez Ruiz Moreno
    org.mule.api.lifecycle.LifecycleException: Cannot process event as "__intercepted_chain_flow_" is stopped
  2. 0

    Currently the APIKit does not support more than one API Proxy configuration in the same application. This is because for each configuration is creating a flow named "__intercepted_chain_flow_". Since the last one overrides the existing one, only the last proxy to be initialized will work. Steps to reproduce: 1) Add two proxy configurations in the same application Expected behavior: - The two proxies working as expected Current behavior: - On starting the application, a warning saying: {code} WARN 2015-09-01 21:56:57,613 [Mule.app.deployer.monitor.1.thread.1] org.mule.config.spring.SpringRegistry: Spring registry already contains an object named '__intercepted_chain_flow_'. The previous object will be overwritten. {code} And when doing a request, the following error: {code} ERROR 2015-09-01 21:56:59,132 [[proxy].connector.http.mule.default.receiver.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Cannot process event as "__intercepted_chain_flow_" is stopped Code : MULE_ERROR-70167 -------------------------------------------------------------------------------- Exception stack is: 1. Cannot process event as "__intercepted_chain_flow_" is stopped (org.mule.api.lifecycle.LifecycleException) org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor:440 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/lifecycle/LifecycleException.html) -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.api.lifecycle.LifecycleException: Cannot process event as "__intercepted_chain_flow_" is stopped at org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor.handleUnaccepted(AbstractPipeline.java:440) at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:45) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** {code}

    MuleSoft JIRA | 11 months ago | Evangelina Martinez Ruiz Moreno
    org.mule.api.lifecycle.LifecycleException: Cannot process event as "__intercepted_chain_flow_" is stopped
  3. 0

    Currently the APIKit does not support more than one API Proxy configuration in the same application. This is because for each configuration is creating a flow named "__intercepted_chain_flow_". Since the last one overrides the existing one, only the last proxy to be initialized will work. Steps to reproduce: 1) Add two proxy configurations in the same application Expected behavior: - The two proxies working as expected Current behavior: - On starting the application, a warning saying: {code} WARN 2015-09-01 21:56:57,613 [Mule.app.deployer.monitor.1.thread.1] org.mule.config.spring.SpringRegistry: Spring registry already contains an object named '__intercepted_chain_flow_'. The previous object will be overwritten. {code} And when doing a request, the following error: {code} ERROR 2015-09-01 21:56:59,132 [[proxy].connector.http.mule.default.receiver.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Cannot process event as "__intercepted_chain_flow_" is stopped Code : MULE_ERROR-70167 -------------------------------------------------------------------------------- Exception stack is: 1. Cannot process event as "__intercepted_chain_flow_" is stopped (org.mule.api.lifecycle.LifecycleException) org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor:440 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/lifecycle/LifecycleException.html) -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.api.lifecycle.LifecycleException: Cannot process event as "__intercepted_chain_flow_" is stopped at org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor.handleUnaccepted(AbstractPipeline.java:440) at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:45) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** {code}

    MuleSoft JIRA | 1 year ago | Evangelina Martinez Ruiz Moreno
    org.mule.api.lifecycle.LifecycleException: Cannot process event as "__intercepted_chain_flow_" is stopped
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Currently the APIKit does not support more than one API Proxy configuration in the same application. This is because for each configuration is creating a flow named "__intercepted_chain_flow_". Since the last one overrides the existing one, only the last proxy to be initialized will work. Steps to reproduce: 1) Add two proxy configurations in the same application Expected behavior: - The two proxies working as expected Current behavior: - On starting the application, a warning saying: {code} WARN 2015-09-01 21:56:57,613 [Mule.app.deployer.monitor.1.thread.1] org.mule.config.spring.SpringRegistry: Spring registry already contains an object named '__intercepted_chain_flow_'. The previous object will be overwritten. {code} And when doing a request, the following error: {code} ERROR 2015-09-01 21:56:59,132 [[proxy].connector.http.mule.default.receiver.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Cannot process event as "__intercepted_chain_flow_" is stopped Code : MULE_ERROR-70167 -------------------------------------------------------------------------------- Exception stack is: 1. Cannot process event as "__intercepted_chain_flow_" is stopped (org.mule.api.lifecycle.LifecycleException) org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor:440 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/lifecycle/LifecycleException.html) -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.api.lifecycle.LifecycleException: Cannot process event as "__intercepted_chain_flow_" is stopped at org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor.handleUnaccepted(AbstractPipeline.java:440) at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:45) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** {code}

    MuleSoft JIRA | 11 months ago | Evangelina Martinez Ruiz Moreno
    org.mule.api.lifecycle.LifecycleException: Cannot process event as "__intercepted_chain_flow_" is stopped
  6. 0

    MUnit test fails - Cannot process event as "getCSVAccountsFlow" is stopped MULE_ERROR-166

    Stack Overflow | 1 year ago | gohmer
    org.mule.api.lifecycle.LifecycleException: Cannot process event as "getCSVAccountsFlow" is stopped

    2 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.mule.api.lifecycle.LifecycleException

      Cannot process event as "__intercepted_chain_flow_" is stopped

      at org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor.handleUnaccepted()
    2. Mule Core
      ExceptionToMessagingExceptionExecutionInterceptor.execute
      1. org.mule.construct.AbstractPipeline$ProcessIfPipelineStartedMessageProcessor.handleUnaccepted(AbstractPipeline.java:440)
      2. org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:45)
      3. org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24)
      3 frames