JIRA

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Create Issue
  • Mule
  • MULE-5011

Config for app 'default' not found

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • 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:
    None

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

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
Hide
Permalink
Dirk Olmes added a comment - 18/Aug/10 11:35 AM

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 - 18/Aug/10 11:35 AM as a workaround I have added an empty config file for now: http://fisheye.codehaus.org/changelog/mule/?cs=19082
Hide
Permalink
Dirk Olmes added a comment - 06/Oct/10 04:42 AM

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 - 06/Oct/10 04:42 AM 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.

People

  • Assignee:
    Andrew Perepelytsya
    Reporter:
    Dirk Olmes
Vote (0)
Watch (0)

Dates

  • Created:
    16/Aug/10 02:59 AM
    Updated:
    06/Oct/10 04:42 AM

Agile

  • View on Board
  • Atlassian JIRA (v5.0.7#734-sha1:8ad78a6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.