1. 首頁
  2. 問答
  3. 部署功能時，ActiveMQ在Fuse Jboss中開始失敗

部署功能時，ActiveMQ在Fuse Jboss中開始失敗

2013-05-14 72 views
0

當我部署功能時，Im出現問題。該功能包含三個捆綁包，Karaf可以很好地部署這些捆綁包，但是當它們部署時，ActiveMQ開始出現問題。部署功能時，ActiveMQ在Fuse Jboss中開始失敗

部署的捆綁包很簡單。 「複雜」是駱駝路線，他暴露CXF端點並調用端點模擬。我只是附加到這個卡爾，卡爾的拉鍊和我的保險絲日誌。該服務正在運行，但與ActiveMQ的問題總是happend

的錯誤是總是相同的：

2013-05-14 15:19:48,046 | INFO | veMQ Broker: amq | ActiveMQServiceFactory$$anon$1 | ?         ? | 106 - org.springframework.context - 3.1.3.RELEASE | Refreshing [email protected]: startup date [Tue May 14 15:19:48 ART 2013]; root of context hierarchy 
2013-05-14 15:19:48,048 | INFO | veMQ Broker: amq | XBeanXmlBeanDefinitionReader  | ?         ? | 105 - org.springframework.beans - 3.1.3.RELEASE | Loading XML bean definitions from file [/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/etc/activemq.xml] 
2013-05-14 15:19:48,095 | INFO | veMQ Broker: amq | DefaultListableBeanFactory  | ?         ? | 105 - org.springframework.beans - 3.1.3.RELEASE | Pre-instantiating singletons in org.s[email protected]1885c3a: defining beans [org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,org.apache.activemq.xbean.XBeanBrokerService#0]; root of factory hierarchy 
2013-05-14 15:19:48,159 | INFO | veMQ Broker: amq | PListStoreImpl     | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | PListStore:[/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq/amq/tmp_storage] started 
2013-05-14 15:19:48,163 | ERROR | veMQ Broker: amq | BrokerService     | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Failed to start Apache ActiveMQ (amq, null). Reason: javax.management.InstanceAlreadyExistsException: org.apache.activemq:type=Broker,brokerName=amq 
javax.management.InstanceAlreadyExistsException: org.apache.activemq:type=Broker,brokerName=amq 
      at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)[:1.6.0_30] 
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)[:1.6.0_30] 
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)[:1.6.0_30] 
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)[:1.6.0_30] 
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)[:1.6.0_30] 
      at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)[:1.6.0_30] 
      at org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] 
      at org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] 
      at org.apache.activemq.broker.BrokerService.startManagementContext(BrokerService.java:2337)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] 
      at org.apache.activemq.broker.BrokerService.start(BrokerService.java:543)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] 
      at org.fusesource.mq.fabric.ActiveMQServiceFactory$ClusteredConfiguration$$anon$3.run(ActiveMQServiceFactory.scala:307)[128:org.jboss.amq.mq-fabric:6.0.0.redhat-024] 
2013-05-14 15:19:48,164 | INFO | veMQ Broker: amq | BrokerService     | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Apache ActiveMQ 5.8.0.redhat-60024 (amq, null) is shutting down 
2013-05-14 15:19:48,168 | INFO | veMQ Broker: amq | TransportConnector    | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Connector openwire Stopped 
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | PListStoreImpl     | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | PListStore:[/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq/amq/tmp_storage] stopped 
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | KahaDBStore      | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Stopping async queue tasks 
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | KahaDBStore      | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Stopping async topic tasks 
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | KahaDBStore      | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Stopped KahaDB 
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | BrokerService     | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Apache ActiveMQ 5.8.0.redhat-60024 (amq, null) uptime 0.010 seconds 
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | BrokerService     | ?         ? | 114 - org.apache.activemq.activemq-osgi - 5.8.0.redhat-60024 | Apache ActiveMQ 5.8.0.redhat-60024 (amq, null) is shutdown 
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | ActiveMQServiceFactory   | ?         ? | 128 - org.jboss.amq.mq-fabric - 6.0.0.redhat-024 | Broker amq failed to start. Will try again in 10 seconds 
2013-05-14 15:19:48,169 | INFO | veMQ Broker: amq | ActiveMQServiceFactory   | ?         ? | 128 - org.jboss.amq.mq-fabric - 6.0.0.redhat-024 | Exception on start: javax.management.InstanceAlreadyExistsException: org.apache.activemq:type=Broker,brokerName=amq 
javax.management.InstanceAlreadyExistsException: org.apache.activemq:type=Broker,brokerName=amq 
      at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)[:1.6.0_30] 
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)[:1.6.0_30] 
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)[:1.6.0_30] 
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)[:1.6.0_30] 
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)[:1.6.0_30] 
      at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)[:1.6.0_30] 
      at org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] 
      at org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] 
      at org.apache.activemq.broker.BrokerService.startManagementContext(BrokerService.java:2337)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] 
      at org.apache.activemq.broker.BrokerService.start(BrokerService.java:543)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] 
      at org.fusesource.mq.fabric.ActiveMQServiceFactory$ClusteredConfiguration$$anon$3.run(ActiveMQServiceFactory.scala:307)[128:org.jboss.amq.mq-fabric:6.0.0.redhat-024]

Dropbox的URL和保險絲LOG https://dl.dropboxusercontent.com/u/225304/fuse.log

Dropbox的URL來.KAR文件https://dl.dropboxusercontent.com/u/225304/PruebaFeature-1.0-SNAPSHOT.kar

這個例子我用了一個乾淨的保險絲。有什麼想法發生了什麼？我不知道問題是ActiveMQ的配置，還是其他的。

這是我recive我在Karaf

列出的ActiveMQ這是當我列出經紀人karaf

JBossFuse:[email protected]> activemq:query --jmxlocal 
Name = KahaDBPersistenceAdapter[/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq/kahadb] 
brokerName = amq 
Transactions = [] 
Size = 13411 
InstanceName = KahaDBPersistenceAdapter[/home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq/kahadb] 
Data = [1] 
type = Broker 
Service = PersistenceAdapter 

brokerName = amq 
service = Health 
CurrentStatus = Good 
type = Broker 

brokerName = amq 
connector = clientConnectors 
type = Broker 
StatisticsEnabled = true 
connectorName = openwire 

destinationName = ActiveMQ.Advisory.MasterBroker 
MemoryUsageByteCount = 0 
DequeueCount = 0 
type = Broker 
destinationType = Topic 
Name = ActiveMQ.Advisory.MasterBroker 
MinEnqueueTime = 0 
MaxAuditDepth = 2048 
AverageEnqueueTime = 0.0 
InFlightCount = 0 
MemoryLimit = 67108864 
brokerName = amq 
EnqueueCount = 1 
MaxEnqueueTime = 0 
MemoryUsagePortion = 1.0 
ProducerCount = 0 
UseCache = true 
BlockedProducerWarningInterval = 30000 
AlwaysRetroactive = false 
Options = 
MaxProducersToAudit = 64 
PrioritizedMessages = false 
ConsumerCount = 0 
ProducerFlowControl = true 
Subscriptions = [] 
QueueSize = 0 
MaxPageSize = 200 
DispatchCount = 0 
MemoryPercentUsage = 0 
ExpiredCount = 0 

TopicSubscribers = [] 
TemporaryQueues = [] 
Uptime = 1 minute 
TemporaryTopicSubscribers = [] 
MemoryPercentUsage = 0 
BrokerVersion = 5.8.0.redhat-60024 
StatisticsEnabled = true 
TotalDequeueCount = 0 
TopicProducers = [] 
QueueSubscribers = [] 
Topics = [org.apache.activemq:type=Broker,brokerName=amq,destinationType=Topic,destinationName=ActiveMQ.Advisory.MasterBroker] 
TotalMessageCount = 0 
SslURL = 
TemporaryQueueSubscribers = [] 
BrokerName = amq 
DynamicDestinationProducers = [] 
Persistent = true 
DataDirectory = /home/ramiro/tecPlata/jboss-fuse-6.0.0.redhat-024/data/amq 
Queues = [] 
DurableTopicSubscribers = [] 
TotalConsumerCount = 0 
InactiveDurableTopicSubscribers = [] 
JobSchedulerStoreLimit = 0 
TempPercentUsage = 0 
MemoryLimit = 67108864 
VMURL = vm://amq 
OpenWireURL = tcp://fluxit-ntb-43:61616?maximumConnections=1000 
JobSchedulerStorePercentUsage = 0 
TotalEnqueueCount = 1 
TemporaryQueueProducers = [] 
StompSslURL = 
TemporaryTopics = [] 
StompURL = 
Slave = false 
BrokerId = ID:fluxit-ntb-43-58596-1368558172573-0:1 
TotalProducerCount = 0 
StorePercentUsage = 0 
brokerName = amq 
StoreLimit = 107374182400 
TransportConnectors = {openwire=tcp://fluxit-ntb-43:61616?maximumConnections=1000} 
TemporaryTopicProducers = [] 
TempLimit = 53687091200 
QueueProducers = [] 
type = Broker

來源

2013-05-14 Chubutin

回答

0

的features.xml在你家是不正確造成此錯誤。它有一些像捆綁

<bundle>mvn:org.apache.felix/org.apache.felix.configadmin/1.2.4</bundle> 
<bundle>mvn:org.apache.aries/org.apache.aries.util/1.0.0</bundle> 
<bundle>mvn:org.apache.aries.proxy/org.apache.aries.proxy.api/1.0.0</bundle> 
<bundle>mvn:org.apache.aries.blueprint/org.apache.aries.blueprint/1.0.1.redhat-60024</bundle>

這些捆綁包是非常基本的容器，並已默認通過容器安裝。

它不應該在你的features.xml，或者如果他們在那裏，你應該有 解析器=「（OBR）」的功能，並依賴=「真」對於那些捆綁，這樣OBR解析器可以踢以防止安裝冗餘捆綁軟件。

此外，

<bundle>mvn:org.apache.aries.blueprint/org.apache.aries.blueprint/1.0.1.redhat-60024</bundle>

是aries.blueprint 1.0.x的無效的，它應該是

<bundle dependency="true" start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.api/1.0.1.redhat-60024</bundle> 
<bundle dependency="true" start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core/1.0.1.redhat-60024</bundle> 
<bundle dependency="true" start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.0.1.redhat-60024</bundle>

代替。否則，你會看到這樣的錯誤

ERROR: Bundle org.apache.aries.blueprint [251] EventDispatcher: Error during dispatch. (java.lang.ClassCastException: org.apache.aries.blueprint.ext.impl.ExtNamespaceHandler cannot be cast to org.apache.aries.blueprint.NamespaceHandler)

java.lang.ClassCastException：org.apache.aries.blueprint.ext.impl.ExtNamespaceHandler不能轉換到org.apache.aries.blueprint.NamespaceHandler

這意味着你的容器中安裝了兩個衝突的aries.blueprint包，幾乎所有東西都搞砸了。

在總結，改變你的features.xml在你家的一樣

<?xml version="1.0" encoding="UTF-8"?> 
<features> 
    <feature name='tosMock' version='1.0.0-SNAPSHOT'> 
    <bundle>mvn:com.tecplata.esb.services/tosMock/1.0.0-SNAPSHOT</bundle> 
    </feature> 
    <feature name='esb-entities' version='1.0.0-SNAPSHOT'> 
    <bundle>mvn:com.tecplata.esb/esb-entities/1.0.0-SNAPSHOT</bundle> 
    </feature> 
    <feature name='vesselsService-sei' version='1.0.0-SNAPSHOT'> 
    <feature version='1.0.0-SNAPSHOT'>esb-entities</feature> 
    <bundle>mvn:com.tecplata.esb.services.sei/vesselsService-sei/1.0.0-SNAPSHOT</bundle> 
    </feature> 
    <feature name='vesselsVisitorService' version='1.0.0-SNAPSHOT'> 
    <bundle>mvn:org.apache.camel/camel-core/2.10.0.redhat-60024</bundle> 
    <feature version='1.0.0-SNAPSHOT'>vesselsService-sei</feature> 
    <bundle>mvn:com.tecplata.esb.services/vesselsVisitorService/1.0.0-SNAPSHOT</bundle> 
    </feature> 
</features>

使它發揮作用。 Freeman

來源

2013-05-15 07:30:01

相關問題

 相關問題