【问题标题】:MULE error [main] org.mule.module.launcher.application.DefaultMuleApplication: nullMULE 错误 [main] org.mule.module.launcher.application.DefaultMuleApplication: null
【发布时间】:2017-01-26 06:13:50
【问题描述】:

尝试在 MuleStudio 3.5 中运行我的 MULE 项目时出现以下错误。两周前我正在运行同一个项目,并且没有对这个特定项目进行任何更改。我唯一做的就是向工作区添加一个新项目。如果我尝试运行新项目,我会得到同样的错误。我也尝试删除新项目,但没有奏效。但是,我在工作区中有其他项目运行良好。任何想法或想法将不胜感激。

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Initializing app 'max_nd_max_workorders'                 +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INFO  2016-06-16 09:43:03,741 [main] org.mule.lifecycle.AbstractLifecycleManager: Initialising RegistryBroker
INFO  2016-06-16 09:43:03,920 [main] org.mule.config.spring.MuleApplicationContext: Refreshing org.mule.config.spring.MuleApplicationContext@1f2586d6: startup date [Thu Jun 16 09:43:03 MDT 2016]; root of context hierarchy
INFO  2016-06-16 09:43:09,353 [main] org.mule.lifecycle.AbstractLifecycleManager: Initialising connector: httpMaxWOPollingConnector
WARN  2016-06-16 09:43:09,475 [main] org.springframework.beans.GenericTypeAwarePropertyDescriptor: Invalid JavaBean property 'port' being accessed! Ambiguous write methods found next to actually used [public void org.mule.endpoint.URIBuilder.setPort(java.lang.String)]: [public void org.mule.endpoint.URIBuilder.setPort(int)]
INFO  2016-06-16 09:43:12,439 [main] org.mule.lifecycle.AbstractLifecycleManager: Initialising model: _muleSystemModel
INFO  2016-06-16 09:43:12,573 [main] org.mule.lifecycle.AbstractLifecycleManager: Initialising connector: httpConnector
INFO  2016-06-16 09:43:12,611 [main] org.mule.lifecycle.AbstractLifecycleManager: Initialising connector: httpProxyConnector
org.mule.module.launcher.application.DefaultMuleApplication: null
java.lang.IllegalArgumentException
at org.springframework.asm.ClassReader.<init>(Unknown Source)
at org.springframework.asm.ClassReader.<init>(Unknown Source)
at org.springframework.asm.ClassReader.<init>(Unknown Source)
at org.springframework.core.LocalVariableTableParameterNameDiscoverer.inspectClass(LocalVariableTableParameterNameDiscoverer.java:110)
at org.springframework.core.LocalVariableTableParameterNameDiscoverer.getParameterNames(LocalVariableTableParameterNameDiscoverer.java:85)
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:193)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1049)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:953)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:490)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:461)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:626)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
at org.mule.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:89)
at org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:109)
at org.mule.config.spring.SpringXmlConfigurationBuilder.createSpringRegistry(SpringXmlConfigurationBuilder.java:119)
at org.mule.config.spring.SpringXmlConfigurationBuilder.doConfigure(SpringXmlConfigurationBuilder.java:73)
at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:46)
at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78)
at org.mule.config.builders.AutoConfigurationBuilder.autoConfigure(AutoConfigurationBuilder.java:101)
at org.mule.config.builders.AutoConfigurationBuilder.doConfigure(AutoConfigurationBuilder.java:57)
at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:46)
at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78)
at org.mule.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:84)
at org.mule.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:207)
at org.mule.module.launcher.application.ApplicationWrapper.init(ApplicationWrapper.java:64)
at org.mule.module.launcher.DefaultMuleDeployer.deploy(DefaultMuleDeployer.java:47)
at org.mule.tooling.server.application.ApplicationDeployer.main(ApplicationDeployer.java:127)


INFO  2016-06-15 13:50:48,189 [main]   org.mule.module.launcher.application.DefaultMuleApplication: App 'max_nd_pm_workorders' never started, nothing to dispose of
Exception in thread "main" org.mule.module.launcher.DeploymentInitException: IllegalArgumentException: 

mule-deploy.properties:

   redeployment.enabled=true
   encoding=UTF-8
   domain=default
   config.resources=max_nd_max_workorders.xml

【问题讨论】:

  • 另外,控制台中的错误输出似乎没有帮助。我发现其他帖子有同样的错误,但原因更明确。
  • 我能想到的就是清理目标文件夹。检查运行配置,看看你是否传递了任何参数
  • 分享你的 mule-deploy 属性文件
  • 我用 mule-deploy.properties 编辑了我的帖子,并在错误发生之前添加了初始化部分。
  • 另外,我已经清理了目标文件夹,并且运行配置中没有传递任何参数。

标签: mule mule-studio


【解决方案1】:

我也遇到过同样的情况,但我没想过要证明任何解决方案的合理性。此外,我不记得有任何解决问题的固定解决方案。请尝试以下任何为我解决此问题的方法。

  • 检查 mule-deploy.properties 是否没有多余的空格或换行符,并确保所有需要的属性都正确
  • 检查您是否没有两次使用相同的端口号或相同的连接器
  • 检查您是否没有错误地使用两个 http 侦听器,因为我认为新版本的 Mule(3.6 及更高版本)不支持此功能
  • 清除/删除工作区中的 .metadata 和 .mule 文件夹
  • 对于以上项目,您需要再次将所有项目重新导入为“从文件夹位置导入项目”。确保取消选中将项目复制到工作空间

如果没有任何效果,则进行新的 anypoint studio 安装,然后将所有项目导入到新工作区中。

【讨论】:

  • 请告诉我以上哪一项对您有用。其中之一肯定对我有用。
【解决方案2】:

我在使用 mule server 3.8.3 EE 时遇到了类似的问题。通过降级到 3.7.0 EE 得到修复

【讨论】:

    猜你喜欢
    • 2014-09-26
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多