2015-12-11 45 views
0

我现在几天运行servicemix 6.1.0。带有文件和jdbc端点的骆驼路线工作 - 很酷的东西。ServiceMix:logmessage“无法启动代理”

现在我想添加activemq。当我从头开始安装servicemix时,一切看起来都很好 - jms的作品。

但是现在我在启动时在日志文件中看到异常,并且命令[email protected]>activemq:list不会返回任何内容。

下面是日志文件的部分内容:

... 
2015-12-11 10:43:35,081 | INFO | ctivemq.server]) | PListStoreImpl     | 176 - org.apache.activemq.activemq-osgi - 5.12.1 | PListStore:[C:\CAD_JOBS\apache-servicemix-6.1.0\data\amq-broker\amq-broker\tmp_storage] started 
2015-12-11 10:43:35,084 | INFO | ctivemq.server]) | ActiveMQServiceFactory$1   | 161 - org.apache.servicemix.bundles.spring-context - 3.2.14.RELEASE_1 | Publishing application context as OSGi service with properties {org.springframework.context.service.name=org.apache.activemq.activemq-osgi, Bundle-SymbolicName=org.apache.activemq.activemq-osgi, Bundle-Version=5.12.1} 
2015-12-11 10:43:35,093 | ERROR | ctivemq.server]) | configadmin      | 6 - org.apache.felix.configadmin - 1.8.4 | [org.osgi.service.cm.ManagedServiceFactory, id=813, bundle=176/mvn:org.apache.activemq/activemq-osgi/5.12.1]: Updating configuration org.apache.activemq.server.24d13a82-a253-4d1e-8355-bcbf0fff6927 caused a problem: Cannot start the broker 
org.osgi.service.cm.ConfigurationException: null : Cannot start the broker 
    at org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:120)[176:org.apache.activemq.activemq-osgi:5.12.1] 
    at Proxye6b76768_a1ce_4232_9f62_ee376293401b.updated(Unknown Source)[:] 
    at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)[6:org.apache.felix.configadmin:1.8.4] 
    at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)[6:org.apache.felix.configadmin:1.8.4] 
    at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1597)[6:org.apache.felix.configadmin:1.8.4] 
    at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1540)[6:org.apache.felix.configadmin:1.8.4] 
    at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[6:org.apache.felix.configadmin:1.8.4] 
    at java.lang.Thread.run(Thread.java:722)[:1.7.0_17] 
Caused by: java.lang.IllegalArgumentException: Service object is not an instance of "org.springframework.core.env.EnvironmentCapable". 
    at org.apache.felix.framework.Felix.registerService(Felix.java:3386)[org.apache.felix.framework-4.2.1.jar:] 
    at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)[org.apache.felix.framework-4.2.1.jar:] 
    at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.publishContextAsOsgiServiceIfNecessary(AbstractOsgiBundleApplicationContext.java:344)[165:org.springframework.osgi.core:1.2.1] 
    at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:237)[165:org.springframework.osgi.core:1.2.1] 
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)[161:org.apache.servicemix.bundles.spring-context:3.2.14.RELEASE_1] 
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.access$301(AbstractDelegatedExecutionApplicationContext.java:69)[165:org.springframework.osgi.core:1.2.1] 
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$1.run(AbstractDelegatedExecutionApplicationContext.java:186)[165:org.springframework.osgi.core:1.2.1] 
    at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)[165:org.springframework.osgi.core:1.2.1] 
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.normalRefresh(AbstractDelegatedExecutionApplicationContext.java:182)[165:org.springframework.osgi.core:1.2.1] 
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$NoDependenciesWaitRefreshExecutor.refresh(AbstractDelegatedExecutionApplicationContext.java:89)[165:org.springframework.osgi.core:1.2.1] 
    at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:175)[165:org.springframework.osgi.core:1.2.1] 
    at org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:102)[176:org.apache.activemq.activemq-osgi:5.12.1] 
    ... 7 more 
2015-12-11 10:43:35,095 | INFO | FelixStartLevel | BlueprintContainerImpl   | 15 - org.apache.aries.blueprint.core - 1.4.4 | Bundle org.apache.servicemix.activemq.service/6.1.0 is waiting for dependencies [(objectClass=javax.transaction.TransactionManager)] 
2015-12-11 10:43:35,101 | INFO | FelixStartLevel | BlueprintContainerImpl   | 15 - org.apache.aries.blueprint.core - 1.4.4 | Bundle org.apache.servicemix.activemq.camel/6.1.0 is waiting for dependencies [(&(&(transacted=false)(name=default-cf))(objectClass=javax.jms.ConnectionFactory))] 
2015-12-11 10:43:35,104 | INFO | FelixStartLevel | CXFActivator      | 92 - org.apache.cxf.cxf-core - 3.1.4 | Adding the extensions from bundle org.apache.camel.camel-cxf-transport (231) [org.apache.camel.component.cxf.transport.CamelTransportFactory] 
... 

的问题是:什么脚麻为什么和如何解决这一问题? Thx为您的时间。

+0

你写的 '当我从头开始安装一切的ServiceMix看起来很好 - JMS的作品。'这是否意味着在安装新的ServiceMix后代理商可以正常工作? – KSobkowiak

+0

是的,它可以在全新解包后使用。运行带有jms-endpoint的路由后,队列中会有消息。我假设我做了一些事情导致activemq在重启时失败。但我认为那只是像'install camel-jdbc'之类的东西。我迷路了... – chris

+0

我试图安装一些jpa,jdbc,交易功能,它看起来不错。如果您可以尝试从全新安装开始重新检查问题,以检查哪个功能会中断代理,那将会很不错 – KSobkowiak

回答

1

您可以检查是否没有安装任何Spring 4.x功能或JAR。 你可以看到安装的功能与

功能:列表

类似的问题发生在安装时弹簧JDBC中的ServiceMix 6.1.0(从网站上下载的zip的ServiceMix)

功能:安装弹簧JDBC(这导致的ActiveMQ到破产)

功能:安装弹簧JDBC/3.2.14.RELEASE_1(ActiveMQ的仍然有效)。

我怀疑安装spring 4.x JAR会导致某人看到太新的JAR,但我没有进一步调查。

功能:安装骆驼SQL

安装弹簧JDBC 3.2.14.RELEASE_1(在SMX 6.1.0)