I tried both options but it still doesn't work. When activemq is started just with camel, logs are continuously filled with lines like:
DEBUG AbstractRegion - Removing consumer: ID:xxxx.xxxxx.hr-42408-1205915755611-2:1:221:1 and DEBUG AbstractRegion - Adding consumer: ID:xxxx.xxxxx.hr-42408-1205915755611-2:1:347:1 But when I start both camel and bridging, there are no logs like that. James.Strachan wrote: > > Yes its an XML namespace issue. > > Either add to your last <bean> element the: > xmlns="http://www.springframework.org/schema/beans"; > > or move the last <bean> element nearer the top (before any non-spring > xmlns="..." statements > > > On 18/03/2008, puska <[EMAIL PROTECTED]> wrote: >> >> Here it is: >> >> >> <beans >> xmlns="http://www.springframework.org/schema/beans"; >> xmlns:amq="http://activemq.org/config/1.0"; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xsi:schemaLocation="http://www.springframework.org/schema/beans >> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd >> http://activemq.org/config/1.0 >> http://activemq.apache.org/schema/activemq-core.xsd >> >> http://activemq.apache.org/camel/schema/spring >> >> http://activemq.apache.org/camel/schema/spring/camel-spring.xsd";> >> >> <!-- Allows us to use system properties as variables in this >> configuration >> file --> >> <bean >> >> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/> >> >> <broker xmlns="http://activemq.org/config/1.0"; brokerName="localhost" >> dataDirectory="${activemq.base}/data"> >> >> <!-- Destination specific policies using destination names or >> wildcards >> --> >> <destinationPolicy> >> <policyMap> >> <policyEntries> >> >> <policyEntry topic="FOO.>" producerFlowControl="false" >> memoryLimit="1mb"> >> <dispatchPolicy> >> <strictOrderDispatchPolicy/> >> </dispatchPolicy> >> <subscriptionRecoveryPolicy> >> <lastImageSubscriptionRecoveryPolicy/> >> </subscriptionRecoveryPolicy> >> </policyEntry> >> >> </policyEntries> >> </policyMap> >> </destinationPolicy> >> >> >> <!-- The transport connectors ActiveMQ will listen to --> >> <transportConnectors> >> <transportConnector name="openwire" uri="tcp://localhost:61616" >> discoveryUri="multicast://default"/> >> <transportConnector name="ssl" uri="ssl://localhost:61617"/> >> <transportConnector name="stomp" uri="stomp://localhost:61613"/> >> <transportConnector name="xmpp" uri="xmpp://localhost:61222"/> >> </transportConnectors> >> >> >> >> <jmsBridgeConnectors> >> <jmsQueueConnector >> outboundQueueConnectionFactory="#remoteFactory"> >> <inboundQueueBridges> >> <inboundQueueBridge >> inboundQueueName="a-any-doc-type" >> localQueueName="any-doc-type" /> >> </inboundQueueBridges> >> <outboundQueueBridges> >> <outboundQueueBridge >> outboundQueueName="any-doc-type" >> localQueueName="k-any-doc-type"/> >> </outboundQueueBridges> >> </jmsQueueConnector> >> </jmsBridgeConnectors> >> >> >> <!-- The store and forward broker networks ActiveMQ will listen to >> --> >> <networkConnectors> >> <!-- by default just auto discover the other brokers --> >> <networkConnector name="default-nc" uri="multicast://default"/> >> </networkConnectors> >> >> </broker> >> >> >> >> <camelContext id="camel" >> xmlns="http://activemq.apache.org/camel/schema/spring";> >> <package>something.camel</package> >> </camelContext> >> >> >> >> >> <!-- lets create a command agent to respond to message based admin >> commands on the ActiveMQ.Agent topic --> >> <commandAgent xmlns="http://activemq.org/config/1.0"/> >> >> >> <!-- An embedded servlet engine for serving up the Admin console --> >> <jetty xmlns="http://mortbay.com/schemas/jetty/1.0";> >> <connectors> >> <nioConnector port="8161" /> >> </connectors> >> >> <handlers> >> <webAppContext contextPath="/admin" >> resourceBase="${activemq.base}/webapps/admin" logUrlOnStart="true" /> >> <webAppContext contextPath="/demo" >> resourceBase="${activemq.base}/webapps/demo" logUrlOnStart="true" /> >> </handlers> >> </jetty> >> >> <!-- JMS ConnectionFactory to use remote --> >> >> <bean id="remoteFactory" >> class="org.apache.activemq.ActiveMQConnectionFactory"> >> >> <property name="brokerURL" value="failover:tcp://10.52.5.201:61616" /> >> </bean> >> </beans> >> >> >> >> >> James.Strachan wrote: >> > >> > Could you show us the complete activemq.xml that doesn't work? >> > >> > On 18/03/2008, puska <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi, >> >> >> >> I'm using Camel to route messages depending on their content. >> >> I wrote some java classes and point to their package in camelContext >> >> tag: >> >> >> >> <camelContext id="camel" >> >> xmlns="http://activemq.apache.org/camel/schema/spring";> >> >> <package>something.camel</package> >> >> </camelContext> >> >> >> >> It works fine, but when I activate bridging: >> >> >> >> <jmsBridgeConnectors> >> >> <jmsQueueConnector outboundQueueConnectionFactory="#remoteFactory"> >> >> <inboundQueueBridges> >> >> <inboundQueueBridge inboundQueueName="a-any-doc-type" >> >> localQueueName="any-doc-type" /> >> >> </inboundQueueBridges> >> >> <outboundQueueBridges> >> >> <outboundQueueBridge outboundQueueName="any-doc-type" >> >> localQueueName="k-any-doc-type"/> >> >> </outboundQueueBridges> >> >> </jmsQueueConnector> >> >> </jmsBridgeConnectors> >> >> ... >> >> <bean id="remoteFactory" >> >> class="org.apache.activemq.ActiveMQConnectionFactory"> >> >> <property name="brokerURL" >> value="failover:tcp://10.53.50.201:61616" /> >> >> </bean> >> >> >> >> then only bridging works. >> >> Separately both functions work, but when I use both of them, only >> >> bridging >> >> works... >> >> >> >> Can anybody tell me why this happens? >> >> Thanks. >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Camel-routing-doesn%27t-work-when-jms-bridging-is-active-tp16121768s2354p16121768.html >> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> > -- >> > James >> > ------- >> > http://macstrac.blogspot.com/ >> > >> > Open Source Integration >> > http://open.iona.com >> > >> > >> >> >> -- >> View this message in context: >> http://www.nabble.com/Camel-routing-doesn%27t-work-when-jms-bridging-is-active-tp16121768s2354p16123633.html >> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/Camel-routing-doesn%27t-work-when-jms-bridging-is-active-tp16121768s2354p16143208.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
