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

时间:2015-03-30 09:06:39

标签: mule

我已经创建了一个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
是的,请有人帮帮我。提前谢谢你

5 个答案:

答案 0 :(得分:8)

请从您的工作室部署zip文件..选择您的应用程序,然后转到文件菜单 - >出口 - >在Mule文件夹下 - >选择Anypoint studio到Mule deployable archieve - >给出名称..它将生成一个Zip文件..将该zip文件部署到独立的app文件夹中..这样就是..不要使用winzip或其他工具创建任何zip文件

答案 1 :(得分:2)

当您从Anypoint Studio运行mule应用程序时,它在mule嵌入式服务器上运行,因此您可以正确运行该应用程序。要独立运行您的应用程序,请确保以下内容与其他建议不同:

  • 独立服务器的版本是否与您在创建mule应用程序期间选择的服务器相同。

拥有一个maven项目总是好的。您可以通过右键单击并在anypoint studio中选择选项mavenize来对您的正常项目进行编组。

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

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

答案 2 :(得分:1)

它与版本无关。我认为这是部署方式的问题(As Anirban告诉你在app app foldeer中部署zip文件)

答案 3 :(得分:1)

您应该创建基于maven的mule项目并使用maven生成zip文件。 pom.xml应该包含要使用的mule版本。部署mule standalone生成的zip并使用mule start运行。

答案 4 :(得分:0)

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

  2. 如果没有添加此文件名并尝试再次运行它。尝试将您的应用程序导入为Zip文件并将其部署到cloudhub并尝试使用。