org.mule.api.lifecycle.LifecycleException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • 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}
    via by Evangelina Martinez Ruiz Moreno,
  • 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}
    via by Evangelina Martinez Ruiz Moreno,
  • 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}
    via by Evangelina Martinez Ruiz Moreno,
  • 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}
    via by Evangelina Martinez Ruiz Moreno,
    • org.mule.api.lifecycle.LifecycleException: Cannot process event as "prepare-message-for-lookup-and-update" 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) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:107) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.BlockingProcessorExecutor.executeNext(BlockingProcessorExecutor.java:94) at org.mule.processor.BlockingProcessorExecutor.execute(BlockingProcessorExecutor.java:56) at org.mule.processor.AbstractRequestResponseMessageProcessor.processBlocking(AbstractRequestResponseMessageProcessor.java:56) at org.mule.processor.AbstractRequestResponseMessageProcessor.process(AbstractRequestResponseMessageProcessor.java:47) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:107)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,