org.mule.api.lifecycle.LifecycleException: Failed to invoke lifecycle phase "dispose" on object: org.mule.util.queue.DelegateQueueManager@4f2a32d

MuleSoft JIRA | Håkan Dahl | 1 year ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Note: patterns are deprecated since 3.6.0 / MULE-7755, but now also seems partly defunct in 3.7.0 as per below. Configuration that previously worked in Mule 3.5.0 no longer works in 3.7.0. See attached demo-project with contained soap-project for reference. # The below configs works in 3.5.0: ## {noformat} <spring:beans> <spring:bean name="pingForConfigBean" class="se.skltp.agp.monitoring.PingForconfigurationTestProducer" /> </spring:beans> <simple-service name="pingforconfig-service" address="http://localhost:8083/pingforconfig?connector=httpConn" type="jax-ws" component-ref="pingForConfigBean" /> {noformat} ## {noformat} <spring:beans> <spring:bean name="pingForConfigBean" class="se.skltp.agp.monitoring.PingForconfigurationTestProducer" /> </spring:beans> <simple-service name="pingforconfig-service" address="http://localhost:8083/pingforconfig?connector=httpConn" type="jax-ws"> <component> <spring-object bean="pingForConfigBean"/> </component> </simple-service> {noformat} but gives startup error in 3.7.0 (see full stack attached): {noformat} 2015-10-19 17:39:41,192 [Mule.app.deployer.monitor.1.thread.1] INFO org.mule.lifecycle.AbstractLifecycleManager - Disposing connector: httpConn 2015-10-19 17:39:41,193 [Mule.app.deployer.monitor.1.thread.1] INFO org.mule.util.monitor.ExpiryMonitor - disposing monitor 2015-10-19 17:39:41,198 [Mule.app.deployer.monitor.1.thread.1] ERROR org.mule.config.spring.SpringRegistry - Failed to shut down registry cleanly: org.mule.Registry.Spring org.mule.api.lifecycle.LifecycleException: Failed to invoke lifecycle phase "dispose" on object: org.mule.util.queue.DelegateQueueManager@4f2a32d at org.mule.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:248) ~[mule-core-3.7.0.jar:3.7.0] at org.mule.lifecycle.phases.MuleContextDisposePhase.applyLifecycle(MuleContextDisposePhase.java:102) ~[mule-core-3.7.0.jar:3.7.0] ... Caused by: java.lang.NullPointerException at org.mule.util.queue.TransactionalQueueManager.doDispose(TransactionalQueueManager.java:61) ~[mule-core-3.7.0.jar:3.7.0] ... 2015-10-19 17:39:41,295 [Mule.app.deployer.monitor.1.thread.1] ERROR org.mule.module.launcher.application.DefaultMuleApplication - null org.mule.api.DefaultMuleException: You must specify a serviceClass attribute on the inbound endpoint when you are using a PassThroughComponent, BridgeComponent, or forward router. at org.mule.module.cxf.builder.WebServiceMessageProcessorBuilder.getTargetClass(WebServiceMessageProcessorBuilder.java:123) ~[mule-module- {noformat} # The below configs works in 3.7.0. BUT - how to provide properties for the component-class ? {noformat} <simple-service name="pingforconfig-service" address="http://localhost:8083/pingforconfig?connector=httpConn" type="jax-ws" component-class="se.skltp.agp.monitoring.PingForconfigurationTestProducer" /> {noformat}

    MuleSoft JIRA | 1 year ago | Håkan Dahl
    org.mule.api.lifecycle.LifecycleException: Failed to invoke lifecycle phase "dispose" on object: org.mule.util.queue.DelegateQueueManager@4f2a32d
  2. 0

    Note: patterns are deprecated since 3.6.0 / MULE-7755, but now also seems partly defunct in 3.7.0 as per below. Configuration that previously worked in Mule 3.5.0 no longer works in 3.7.0. See attached demo-project with contained soap-project for reference. # The below configs works in 3.5.0: ## {noformat} <spring:beans> <spring:bean name="pingForConfigBean" class="se.skltp.agp.monitoring.PingForconfigurationTestProducer" /> </spring:beans> <simple-service name="pingforconfig-service" address="http://localhost:8083/pingforconfig?connector=httpConn" type="jax-ws" component-ref="pingForConfigBean" /> {noformat} ## {noformat} <spring:beans> <spring:bean name="pingForConfigBean" class="se.skltp.agp.monitoring.PingForconfigurationTestProducer" /> </spring:beans> <simple-service name="pingforconfig-service" address="http://localhost:8083/pingforconfig?connector=httpConn" type="jax-ws"> <component> <spring-object bean="pingForConfigBean"/> </component> </simple-service> {noformat} but gives startup error in 3.7.0 (see full stack attached): {noformat} 2015-10-19 17:39:41,192 [Mule.app.deployer.monitor.1.thread.1] INFO org.mule.lifecycle.AbstractLifecycleManager - Disposing connector: httpConn 2015-10-19 17:39:41,193 [Mule.app.deployer.monitor.1.thread.1] INFO org.mule.util.monitor.ExpiryMonitor - disposing monitor 2015-10-19 17:39:41,198 [Mule.app.deployer.monitor.1.thread.1] ERROR org.mule.config.spring.SpringRegistry - Failed to shut down registry cleanly: org.mule.Registry.Spring org.mule.api.lifecycle.LifecycleException: Failed to invoke lifecycle phase "dispose" on object: org.mule.util.queue.DelegateQueueManager@4f2a32d at org.mule.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:248) ~[mule-core-3.7.0.jar:3.7.0] at org.mule.lifecycle.phases.MuleContextDisposePhase.applyLifecycle(MuleContextDisposePhase.java:102) ~[mule-core-3.7.0.jar:3.7.0] ... Caused by: java.lang.NullPointerException at org.mule.util.queue.TransactionalQueueManager.doDispose(TransactionalQueueManager.java:61) ~[mule-core-3.7.0.jar:3.7.0] ... 2015-10-19 17:39:41,295 [Mule.app.deployer.monitor.1.thread.1] ERROR org.mule.module.launcher.application.DefaultMuleApplication - null org.mule.api.DefaultMuleException: You must specify a serviceClass attribute on the inbound endpoint when you are using a PassThroughComponent, BridgeComponent, or forward router. at org.mule.module.cxf.builder.WebServiceMessageProcessorBuilder.getTargetClass(WebServiceMessageProcessorBuilder.java:123) ~[mule-module- {noformat} # The below configs works in 3.7.0. BUT - how to provide properties for the component-class ? {noformat} <simple-service name="pingforconfig-service" address="http://localhost:8083/pingforconfig?connector=httpConn" type="jax-ws" component-class="se.skltp.agp.monitoring.PingForconfigurationTestProducer" /> {noformat}

    MuleSoft JIRA | 1 year ago | Håkan Dahl
    org.mule.api.lifecycle.LifecycleException: Failed to invoke lifecycle phase "dispose" on object: org.mule.util.queue.DelegateQueueManager@4f2a32d

    Root Cause Analysis

    1. org.mule.api.lifecycle.LifecycleException

      Failed to invoke lifecycle phase "dispose" on object: org.mule.util.queue.DelegateQueueManager@4f2a32d

      at org.mule.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle()
    2. Mule Core
      MuleContextDisposePhase.applyLifecycle
      1. org.mule.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:248)[mule-core-3.7.0.jar:3.7.0]
      2. org.mule.lifecycle.phases.MuleContextDisposePhase.applyLifecycle(MuleContextDisposePhase.java:102)[mule-core-3.7.0.jar:3.7.0]
      2 frames