apache camel - ActiveMQ starts to fail in Fuse Jboss when a feature is deployed -
im having problem when deploy feature. feature contains 3 bundles, , karaf deploys these bundles, when deployed activemq starts having problems.
the deployed bundles simples. "complicated" camel route expose cxf endpoint , call endpoint mock. attached threar .kar, zip of kar , fuse log. service running, problem activemq happend
the error same:
2013-05-14 15:19:48,046 | info | vemq broker: amq | activemqservicefactory$$anon$1 | ? ? | 106 - org.springframework.context - 3.1.3.release | refreshing org.fusesource.mq.fabric.activemqservicefactory$$anon$1@33c91e: 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 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.springframework.beans.factory.support.defaultlistablebeanfactory@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 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 @ com.sun.jmx.mbeanserver.repository.addmbean(repository.java:453)[:1.6.0_30] @ com.sun.jmx.interceptor.defaultmbeanserverinterceptor.internal_addobject(defaultmbeanserverinterceptor.java:1484)[:1.6.0_30] @ com.sun.jmx.interceptor.defaultmbeanserverinterceptor.registerdynamicmbean(defaultmbeanserverinterceptor.java:963)[:1.6.0_30] @ com.sun.jmx.interceptor.defaultmbeanserverinterceptor.registerobject(defaultmbeanserverinterceptor.java:917)[:1.6.0_30] @ com.sun.jmx.interceptor.defaultmbeanserverinterceptor.registermbean(defaultmbeanserverinterceptor.java:312)[:1.6.0_30] @ com.sun.jmx.mbeanserver.jmxmbeanserver.registermbean(jmxmbeanserver.java:482)[:1.6.0_30] @ org.apache.activemq.broker.jmx.managementcontext.registermbean(managementcontext.java:380)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] @ org.apache.activemq.broker.jmx.annotatedmbean.registermbean(annotatedmbean.java:72)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] @ org.apache.activemq.broker.brokerservice.startmanagementcontext(brokerservice.java:2337)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] @ org.apache.activemq.broker.brokerservice.start(brokerservice.java:543)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] @ 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) 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) 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 start. 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 @ com.sun.jmx.mbeanserver.repository.addmbean(repository.java:453)[:1.6.0_30] @ com.sun.jmx.interceptor.defaultmbeanserverinterceptor.internal_addobject(defaultmbeanserverinterceptor.java:1484)[:1.6.0_30] @ com.sun.jmx.interceptor.defaultmbeanserverinterceptor.registerdynamicmbean(defaultmbeanserverinterceptor.java:963)[:1.6.0_30] @ com.sun.jmx.interceptor.defaultmbeanserverinterceptor.registerobject(defaultmbeanserverinterceptor.java:917)[:1.6.0_30] @ com.sun.jmx.interceptor.defaultmbeanserverinterceptor.registermbean(defaultmbeanserverinterceptor.java:312)[:1.6.0_30] @ com.sun.jmx.mbeanserver.jmxmbeanserver.registermbean(jmxmbeanserver.java:482)[:1.6.0_30] @ org.apache.activemq.broker.jmx.managementcontext.registermbean(managementcontext.java:380)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] @ org.apache.activemq.broker.jmx.annotatedmbean.registermbean(annotatedmbean.java:72)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] @ org.apache.activemq.broker.brokerservice.startmanagementcontext(brokerservice.java:2337)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] @ org.apache.activemq.broker.brokerservice.start(brokerservice.java:543)[114:org.apache.activemq.activemq-osgi:5.8.0.redhat-60024] @ 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 fuse log https://dl.dropboxusercontent.com/u/225304/fuse.log
dropbox url .kar file https://dl.dropboxusercontent.com/u/225304/pruebafeature-1.0-snapshot.kar
this example used clean fuse. ideas of happening? dont know if problem configuration of activemq, or else.
this recive when list activemq in karaf
this when list broker in karaf
jbossfuse:karaf@root> 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 = 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
the features.xml in kar incorrect cause error. has bundle like
<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> those bundles fundamental container , installed container default.
it shouldn't in features.xml, or if they're there, should have resolver="(obr)" feature , dependency="true" bundle obr resolver can kick in prevent install redundant bundles.
moreover,
<bundle>mvn:org.apache.aries.blueprint/org.apache.aries.blueprint/1.0.1.redhat-60024</bundle> is invalid aries.blueprint 1.0.x, should be
<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> instead. otherwise see errors like
error: bundle org.apache.aries.blueprint [251] eventdispatcher: error during dispatch. (java.lang.classcastexception: org.apache.aries.blueprint.ext.impl.extnamespacehandler cannot cast org.apache.aries.blueprint.namespacehandler) java.lang.classcastexception: org.apache.aries.blueprint.ext.impl.extnamespacehandler cannot cast org.apache.aries.blueprint.namespacehandler
this means have 2 conflict aries.blueprint bundle installed in container messed everything.
in summary, change features.xml in kar like
<?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> can make work. freeman
Comments
Post a Comment