org.mule.api.DefaultMuleException: File ".profile" does not exist or cannot be read

Google Groups | herbison | 3 years ago
  1. 0

    [mule-user] File ".profile" does not exist or cannot be read

    Google Groups | 3 years ago | herbison
    org.mule.api.DefaultMuleException: File ".profile" does not exist or cannot be read
  2. 0

    mule file catch lock exception

    Stack Overflow | 3 years ago | Sérgio Abreu
    org.mule.api.DefaultMuleException: File "teste.zip" does not exist or cannot be read
  3. 0

    When a context-property for the xslt-transfomer has a null value, {code}org.mule.module.xml.transformer.XsltTransformer{code} is not handling it therefore setting a null parameter to {code}javax.xml.transform.Transformer#setParameter{code} and it is supported to set null values so an NPE is thrown. *Instead the XsltTransformer should handle this and throw a MuleException with the proper message.* {code} ERROR 2016-03-01 17:29:18,161 [[xslunittest].connector.http.mule.default.receiver.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : The Context Property for key "vtn" cannot have a null value Type : org.mule.api.DefaultMuleException Code : MULE_ERROR-11 JavaDoc : http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/DefaultMuleException.html ******************************************************************************** Exception stack is: 1. The Context Property for key "vtn" cannot have a null value (org.mule.api.DefaultMuleException) org.mule.module.xml.transformer.XsltTransformer:242 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/DefaultMuleException.html) ******************************************************************************** Root Exception stack trace: org.mule.api.DefaultMuleException: The Context Property for key "vtn" cannot have a null value at org.mule.module.xml.transformer.XsltTransformer.doTransform(XsltTransformer.java:242) {code}

    MuleSoft JIRA | 9 months ago | Guillermo Fernandes
    org.mule.api.DefaultMuleException: The Context Property for key "vtn" cannot have a null value
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 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.DefaultMuleException: You must specify a serviceClass attribute on the inbound endpoint when you are using a PassThroughComponent, BridgeComponent, or forward router.
  6. 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.DefaultMuleException: You must specify a serviceClass attribute on the inbound endpoint when you are using a PassThroughComponent, BridgeComponent, or forward router.

    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.DefaultMuleException

      File ".profile" does not exist or cannot be read

      at org.mule.transport.file.FileMessageReceiver.attemptFileLock()
    2. org.mule.transport
      FileMessageReceiver.poll
      1. org.mule.transport.file.FileMessageReceiver.attemptFileLock(FileMessageReceiver.java:608)
      2. org.mule.transport.file.FileMessageReceiver.processFile(FileMessageReceiver.java:290)
      3. org.mule.transport.file.FileMessageReceiver.poll(FileMessageReceiver.java:238)
      3 frames
    3. Mule Core
      WorkerContext.run
      1. org.mule.transport.AbstractPollingMessageReceiver.performPoll(AbstractPollingMessageReceiver.java:219)
      2. org.mule.transport.PollingReceiverWorker.poll(PollingReceiverWorker.java:84)
      3. org.mule.transport.PollingReceiverWorker.run(PollingReceiverWorker.java:53)
      4. org.mule.work.WorkerContext.run(WorkerContext.java:311)
      4 frames
    4. Java RT
      Thread.run
      1. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      2. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      3. java.lang.Thread.run(Thread.java:662)
      3 frames