activemq在windows下啟動報錯,閃退問題

來源:互聯網
上載者:User

標籤:activemq   閃退   windows   win7   報錯   

2015-04-22 22:42:36,825 | WARN  | Exception thrown from LifecycleProcessor on context close | org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMainjava.lang.IllegalStateException: LifecycleProcessor not initialized - call 'refresh' before invoking lifecycle methods via the context: [email protected]: startup date [Wed Apr 22 22:42:32 CST 2015]; root of context hierarchyat org.springframework.context.support.AbstractApplicationContext.getLifecycleProcessor(AbstractApplicationContext.java:360)[spring-context-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1057)[spring-context-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:1010)[spring-context-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.apache.activemq.hooks.SpringContextHook.run(SpringContextHook.java:30)[activemq-spring-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:809)[activemq-broker-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.xbean.XBeanBrokerService.stop(XBeanBrokerService.java:122)[activemq-spring-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.broker.BrokerService.start(BrokerService.java:601)[activemq-broker-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBeanBrokerService.java:73)[activemq-spring-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_09]at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)[:1.7.0_09]at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)[:1.7.0_09]at java.lang.reflect.Method.invoke(Unknown Source)[:1.7.0_09]at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1638)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1579)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1509)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:296)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:293)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628)[spring-beans-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932)[spring-context-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)[spring-context-3.2.8.RELEASE.jar:3.2.8.RELEASE]at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:64)[xbean-spring-3.16.jar:3.16]at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:52)[xbean-spring-3.16.jar:3.16]at org.apache.activemq.xbean.XBeanBrokerFactory$1.<init>(XBeanBrokerFactory.java:104)[activemq-spring-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.xbean.XBeanBrokerFactory.createApplicationContext(XBeanBrokerFactory.java:104)[activemq-spring-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.xbean.XBeanBrokerFactory.createBroker(XBeanBrokerFactory.java:67)[activemq-spring-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:71)[activemq-broker-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:54)[activemq-broker-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:87)[activemq-console-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)[activemq-console-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:150)[activemq-console-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)[activemq-console-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)[activemq-console-5.10-SNAPSHOT.jar:5.10-SNAPSHOT]at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_09]at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)[:1.7.0_09]at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)[:1.7.0_09]at java.lang.reflect.Method.invoke(Unknown Source)[:1.7.0_09]at org.apache.activemq.console.Main.runTaskClass(Main.java:262)[activemq.jar:5.10-SNAPSHOT]at org.apache.activemq.console.Main.main(Main.java:115)[activemq.jar:5.10-SNAPSHOT]at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_09]

報錯如上,此問題很詭異,網上其實已經有很多文章解決該問題了,但都是針對linux的,說是linux主機名稱裡有“-”,"."等字元。把主機名稱裡的這些字元去掉就解決了。

樓主也看到解決方案了,但以為那僅是linux上的解決方案,所以就沒有用此方法來解決window下 的同樣問題。

不曾想windows其實也是同樣的道理。當樓主把activemq版本一降再降,下載了好多低版本activemq,發現啟動時都是同樣錯誤。在active-root-path/data/activemq.log檔案裡有日誌詳細。

查驗了網上各種方法,都沒搞定,最後樓主決定按照linux的解決套路來,把windows電腦名稱改為純英文字母,原電腦名稱:lee_pc,修改後為leepc,然後重啟電腦,再重新運行activemq.bat,神奇的自然就好了。

其實很簡單的問題,是吧。

activemq在windows下啟動報錯,閃退問題

聯繫我們

該頁面正文內容均來源於網絡整理,並不代表阿里雲官方的觀點,該頁面所提到的產品和服務也與阿里云無關,如果該頁面內容對您造成了困擾,歡迎寫郵件給我們,收到郵件我們將在5個工作日內處理。

如果您發現本社區中有涉嫌抄襲的內容,歡迎發送郵件至: info-contact@alibabacloud.com 進行舉報並提供相關證據,工作人員會在 5 個工作天內聯絡您,一經查實,本站將立刻刪除涉嫌侵權內容。

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.