Mule
  1. Mule
  2. MULE-5011

Config for app 'default' not found

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0-RC1
    • Fix Version/s: Bug Backlog
    • Component/s: Core: Deployment
    • Labels:
      None
    • User impact:
      Medium
    • Log Output:
      Hide
      org.mule.module.launcher.InstallException: Config for app 'default' not found: /tmp/mule-standalone-3.0.0-RC1-SNAPSHOT/apps/default/mule-config.xml
              at org.mule.module.launcher.DefaultMuleApplication.install(DefaultMuleApplication.java:91)
              at org.mule.module.launcher.ApplicationWrapper.install(ApplicationWrapper.java:99)
              at org.mule.module.launcher.DefaultMuleDeployer.deploy(DefaultMuleDeployer.java:34)
              at org.mule.module.launcher.DeploymentService.start(DeploymentService.java:98)
              at org.mule.module.launcher.MuleContainer.start(MuleContainer.java:130)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:592)
              at org.mule.module.reboot.MuleContainerWrapper.start(MuleContainerWrapper.java:64)
              at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:2788)
      Show
      org.mule.module.launcher.InstallException: Config for app 'default' not found: /tmp/mule-standalone-3.0.0-RC1-SNAPSHOT/apps/default/mule-config.xml         at org.mule.module.launcher.DefaultMuleApplication.install(DefaultMuleApplication.java:91)         at org.mule.module.launcher.ApplicationWrapper.install(ApplicationWrapper.java:99)         at org.mule.module.launcher.DefaultMuleDeployer.deploy(DefaultMuleDeployer.java:34)         at org.mule.module.launcher.DeploymentService.start(DeploymentService.java:98)         at org.mule.module.launcher.MuleContainer.start(MuleContainer.java:130)         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)         at java.lang.reflect.Method.invoke(Method.java:592)         at org.mule.module.reboot.MuleContainerWrapper.start(MuleContainerWrapper.java:64)         at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:2788)
    • Similar Issues:
      MULE-8263Mule global log config is not found when application has plugins
      MULE-7520Avoid writing app log entries in container log file when not using an specific log4j config file for the app.
      MULE-3032Improve error message when config file is not found.
      MULE-8093Domain default is deleted during start causing all related apps to fail.
      MULE-1643when space is in path to config file, won't be found
      MULE-1463Update deprecated configs for example apps
      MULE-5351JDBC driver found but is not loaded
      MULE-5325Provide defaults and config-by-convention for <jetty:webapp/>
      MULE-7544Change derby config to use embedded driver by default
      MULE-2083Improve handling of global (default) beans in config

      Description

      • unpack the mule distro
      • set MULE_HOME to the unpack location
      • run $MULE_HOME/bin/mule

      Although we create a "default" application in the "apps" folder, it's empty and thus hot deploy complains about a missing mule-config.xml file (see log).

      This is not a serious issue as the running Mule works fine when you drop additional applications into the apps folder. However, the warning logged on startup is confusing for users who aren't proficient with Mule's hot deployment feature.

        Activity

        Hide
        Dirk Olmes added a comment -

        as a workaround I have added an empty config file for now: http://fisheye.codehaus.org/changelog/mule/?cs=19082

        Show
        Dirk Olmes added a comment - as a workaround I have added an empty config file for now: http://fisheye.codehaus.org/changelog/mule/?cs=19082
        Hide
        Dirk Olmes added a comment -

        Increasing the severity to major - Mule IDE's new hot deployment builder copies all classes into the app folder. If the user didn't create a config yet and starts Mule, they will see the same exception as above. Mule should handle this case gracefully and not even try to deploy the app.

        Show
        Dirk Olmes added a comment - Increasing the severity to major - Mule IDE's new hot deployment builder copies all classes into the app folder. If the user didn't create a config yet and starts Mule, they will see the same exception as above. Mule should handle this case gracefully and not even try to deploy the app.
        Hide
        Jeyaram Deivachandran added a comment -

        Tested on Mule 3.4.2, this issue is fixed

        Show
        Jeyaram Deivachandran added a comment - Tested on Mule 3.4.2, this issue is fixed

          People

          • Assignee:
            Andrew Perepelytsya
            Reporter:
            Dirk Olmes
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development