在Mule standalone中部署Mule应用程序时出错

在Mule standalone中部署Mule应用程序时出错,mule,Mule,我已经创建了一个mule应用程序,当我使用mule 3.5.6 CE运行它时,它在anypoint studio中运行良好,但当我尝试在mule-standalone-3.6.1中部署它时,我得到以下结果: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + New app 'pushv1' + +++++++++++++++

我已经创建了一个mule应用程序,当我使用mule 3.5.6 CE运行它时,它在anypoint studio中运行良好,但当我尝试在mule-standalone-3.6.1中部署它时,我得到以下结果:

 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    + New app 'pushv1'                                         +
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    INFO  2015-03-30 10:56:03,009 [WrapperListener_start_runner] org.mule.module.lau
    ncher.application.DefaultMuleApplication: App 'pushv1' never started, nothing to
     dispose of
    ERROR 2015-03-30 10:56:03,010 [WrapperListener_start_runner] org.mule.module.lau
    ncher.DefaultArchiveDeployer:
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    + Failed to deploy artifact 'pushv1', see below            +
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    org.mule.module.launcher.InstallException: Config for app 'pushv1' not found: C:
    \mule-standalone-3.6.1\apps\pushv1\mule-config.xml
            at org.mule.module.launcher.application.DefaultMuleApplication.install(D
    efaultMuleApplication.java:100) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.artifact.ArtifactWrapper$3.execute(ArtifactW
    rapper.java:74) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.artifact.ArtifactWrapper.executeWithinArtifa
    ctClassLoader(ArtifactWrapper.java:129) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.artifact.ArtifactWrapper.install(ArtifactWra
    pper.java:69) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifa
    ctDeployer.java:24) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.DefaultArchiveDeployer.guardedDeploy(Default
    ArchiveDeployer.java:310) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.DefaultArchiveDeployer.deployArtifact(Defaul
    tArchiveDeployer.java:330) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.DefaultArchiveDeployer.deployExplodedApp(Def
    aultArchiveDeployer.java:297) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.DefaultArchiveDeployer.deployExplodedArtifac
    t(DefaultArchiveDeployer.java:108) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.DeploymentDirectoryWatcher.deployExplodedApp
    s(DeploymentDirectoryWatcher.java:290) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.DeploymentDirectoryWatcher.start(DeploymentD
    irectoryWatcher.java:151) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.MuleDeploymentService.start(MuleDeploymentSe
    rvice.java:100) ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at org.mule.module.launcher.MuleContainer.start(MuleContainer.java:152)
    ~[mule-module-launcher-3.6.1.jar:3.6.1]
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0
    _40]
            at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0
    _40]
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1
    .8.0_40]
            at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_40]
            at org.mule.module.reboot.MuleContainerWrapper.start(MuleContainerWrappe
    r.java:52) ~[mule-module-reboot-3.6.1.jar:3.6.1]
            at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:
    2788) ~[wrapper-3.2.3.jar:3.2.3]
    INFO  2015-03-30 10:56:03,012 [WrapperListener_start_runner] org.mule.module.lau
    ncher.DeploymentDirectoryWatcher:
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    + Mule is up and kicking (every 5000ms)                    +
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    INFO  2015-03-30 10:56:03,033 [Mule.app.deployer.monitor.1.thread.1] org.mule.mo
    dule.launcher.DefaultArchiveDeployer: ================== Request to Undeploy Art
    ifact: pushv1
    INFO  2015-03-30 10:56:03,035 [Mule.app.deployer.monitor.1.thread.1] org.mule.mo
    dule.launcher.application.DefaultMuleApplication: App 'pushv1' never started, no
    thing to dispose of
    ERROR 2015-03-30 10:56:03,040 [WrapperListener_start_runner] org.mule.module.lau
    ncher.MuleDeploymentService: java.lang.NullPointerException

谁能帮帮我吗。提前感谢您

请从您的工作室部署zip文件。。选择应用程序,然后进入文件菜单->导出->Mule文件夹下->选择任意点studio到Mule可部署Archive->给出名称。。它将生成一个Zip文件。。在standalone的应用程序文件夹中部署该zip文件。。就是这样。。不要使用winzip或其他工具创建任何zip,这与版本无关。我认为这是部署方式的问题,正如Anirban告诉我们的,在你的应用程序foldeer中部署zip文件。你应该创建基于maven的mule项目,并使用maven生成zip文件。
xml应该包含要使用的mule版本。部署mule standalone中生成的zip并使用mule start运行。

当您从Anypoint Studio运行mule应用程序时,它会在mule embedded server上运行,因此您能够正确运行应用程序。要在单机版上运行应用程序,请确保除其他建议外,还包括以下内容:

独立服务器的版本是否与您在创建mule应用程序期间选择的服务器相同。 有一个maven项目总是好的。通过右键单击并在anypoint studio中选择选项mavenize,您可以对普通项目进行mavenize

一旦mavenize,它就开始构建和安装依赖项。它可以在您的控制台中看到。最后,您将获得构建成功消息

现在转到目标文件夹,您将获得项目的zip文件。只需将其选中并粘贴到standalone的apps文件夹中即可

首先需要检查的是mule-deploy.properties文件中是否有此xml文件

如果没有,请添加此文件名并尝试再次运行。尝试将应用程序作为Zip文件导入并部署到cloudhub,然后重试


您是如何创建可部署文件夹的?从anypoint工作室来的?是的。我已经创建了要在anypoint studio中部署的应用程序,它在嵌入式服务器3.5.0 CE中运行良好。请检查应用程序中是否有mule-config.xml写入mule-deploy.properties。。。如果有,,然后更改并将其从中删除这是我的mule-deploy.properties的内容:*生成的内容**mule应用程序部署描述符Sun Mar 29 14:59:25 WEST 2015重新部署。enabled=true encoding=UTF-8 domain=default config.resources=pushv1.xml您正在部署和获得此问题的独立版本以及哪个版本独立运行是否正常???另一个选项是使用maven。您必须下载它,安装它,在Studio中配置它,然后生成一个POM文件。该过程的所有说明都可以在mulesoft.org上找到