You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Yari Marchetti <ya...@staff.dada.net> on 2008/07/31 16:42:10 UTC
Camel and JMX
Hi,
i already enabled the JMX for ActiveMQ, and it's working well, but I'm
stuck on getting it
to work under Camel.
In my activemq.xml i have:
<broker xmlns="http://activemq.apache.org/schema/core"
brokerName="Test"
dataDirectory="${activemq.base}/var/"
useJmx="true" >
.
.
.
<managementContext>
<managementContext connectorPort="61611"
jmxDomainName="org.apache.activemq" />
</managementContext>
</broker>
<camelContext id="camel">
<jmxAgent id="agent" mbeanObjectDomainName="org.apache.camel"
mbeanServerDefaultDomain="org.apache.camel" />
<route>
<from uri="activemq:dadanet.events.incoming"/>
<to uri="activemq:dadanet.events.GSA_LOG" />
</route>
</camelContext>
I have tried several different setups but Camel doesn't seem to register
to the default JVM
MBean server, like ActiveMQ does.
any clues?
Re: JMS-JMS bridge and wildcards
Posted by Minh Tu Duong <mi...@maas.de>.
Hi Rob,
i try to the features of jms component and the same proplem happens:
configuration:
------------------
<camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
<from uri="activemq:*.*"/>
<to uri="remoteAMQ:*.*"/>
</route>
</camelContext>
<bean id="remoteAMQ" class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory">
<bean class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="tcp://192.168.1.218:61616"/>
</bean>
</property>
</bean>
-------------------
and when i send message to name.somename queue at local AMQ, it will be
sent automatically to *.* queue at remoteAMQ. not to name.somename queue
at remoteAMQ as Trav wants.
cheers
Minh Tu.
Rob Davies schrieb:
> We will be deprecating the JMS-JMS bridge - as its functionality is
> now better replaced by Apache Camel - see
> http://activemq.apache.org/camel/jms.html
>
> cheers,
>
> Rob
> On 8 Aug 2008, at 11:49, Minh Tu Duong wrote:
>
>> Hi all,
>>
>> some body know that this bug already fixed? JMS bridge works
>> correctly with wildcards.
>>
>> cheers,
>> Minh Tu.
>>
>> Travis Endersby schrieb:
>>> apache-activemq-5.1.0
>>>
>>> On Aug 1, 2008, at 1:46 AM, Rob Davies wrote:
>>>
>>>> that's an odd one - which version are you using?
>>>>
>>>> cheers,
>>>>
>>>> Rob
>>>>
>>>> On 31 Jul 2008, at 18:00, Travis Endersby wrote:
>>>>
>>>>> Hi Folks,
>>>>>
>>>>> I am looking to bridge many queues, such as "com.blah.foo" ,
>>>>> "com.blah.bar", "com.blah.nOtherThings" between some jms servers.
>>>>>
>>>>>
>>>>> This is working great with the below type of set up, in that all
>>>>> messages get accross ...Yet they lose their actual topic/queue
>>>>> name and come in as the actual wildcard queue itself).
>>>>>
>>>>> ie; how do I make sure that "com.blah.in.foo" comes across as
>>>>> "com.blah.in.foo" instead of "com.blah.in.<"
>>>>>
>>>>> Thanks in advance
>>>>> Trav
>>>>>
>>>>>
>>>>> <jmsBridgeConnectors>
>>>>> <jmsQueueConnector
>>>>> outboundQueueConnectionFactory="#remoteFactory">
>>>>> <inboundQueueBridges>
>>>>> <inboundQueueBridge
>>>>> inboundQueueName="com.blah.in.>" / >
>>>>> </inboundQueueBridges>
>>>>> <outboundQueueBridges>
>>>>> <outboundQueueBridge
>>>>> outboundQueueName="com.blah.outbound.*" />
>>>>> </outboundQueueBridges>
>>>>> </jmsQueueConnector>
>>>>> </jmsBridgeConnectors>
>>>>
>>>
>>
>
Re: JMS-JMS bridge and wildcards
Posted by Rob Davies <ra...@gmail.com>.
We will be deprecating the JMS-JMS bridge - as its functionality is
now better replaced by Apache Camel - see http://activemq.apache.org/camel/jms.html
cheers,
Rob
On 8 Aug 2008, at 11:49, Minh Tu Duong wrote:
> Hi all,
>
> some body know that this bug already fixed? JMS bridge works
> correctly with wildcards.
>
> cheers,
> Minh Tu.
>
> Travis Endersby schrieb:
>> apache-activemq-5.1.0
>>
>> On Aug 1, 2008, at 1:46 AM, Rob Davies wrote:
>>
>>> that's an odd one - which version are you using?
>>>
>>> cheers,
>>>
>>> Rob
>>>
>>> On 31 Jul 2008, at 18:00, Travis Endersby wrote:
>>>
>>>> Hi Folks,
>>>>
>>>> I am looking to bridge many queues, such as "com.blah.foo" ,
>>>> "com.blah.bar", "com.blah.nOtherThings" between some jms servers.
>>>>
>>>>
>>>> This is working great with the below type of set up, in that all
>>>> messages get accross ...Yet they lose their actual topic/queue
>>>> name and come in as the actual wildcard queue itself).
>>>>
>>>> ie; how do I make sure that "com.blah.in.foo" comes across as
>>>> "com.blah.in.foo" instead of "com.blah.in.<"
>>>>
>>>> Thanks in advance
>>>> Trav
>>>>
>>>>
>>>> <jmsBridgeConnectors>
>>>> <jmsQueueConnector
>>>> outboundQueueConnectionFactory="#remoteFactory">
>>>> <inboundQueueBridges>
>>>> <inboundQueueBridge
>>>> inboundQueueName="com.blah.in.>" / >
>>>> </inboundQueueBridges>
>>>> <outboundQueueBridges>
>>>> <outboundQueueBridge
>>>> outboundQueueName="com.blah.outbound.*" />
>>>> </outboundQueueBridges>
>>>> </jmsQueueConnector>
>>>> </jmsBridgeConnectors>
>>>
>>
>
Re: JMS-JMS bridge and wildcards
Posted by Minh Tu Duong <mi...@maas.de>.
Hi all,
some body know that this bug already fixed? JMS bridge works correctly
with wildcards.
cheers,
Minh Tu.
Travis Endersby schrieb:
> apache-activemq-5.1.0
>
> On Aug 1, 2008, at 1:46 AM, Rob Davies wrote:
>
>> that's an odd one - which version are you using?
>>
>> cheers,
>>
>> Rob
>>
>> On 31 Jul 2008, at 18:00, Travis Endersby wrote:
>>
>>> Hi Folks,
>>>
>>> I am looking to bridge many queues, such as "com.blah.foo" ,
>>> "com.blah.bar", "com.blah.nOtherThings" between some jms servers.
>>>
>>>
>>> This is working great with the below type of set up, in that all
>>> messages get accross ...Yet they lose their actual topic/queue name
>>> and come in as the actual wildcard queue itself).
>>>
>>> ie; how do I make sure that "com.blah.in.foo" comes across as
>>> "com.blah.in.foo" instead of "com.blah.in.<"
>>>
>>> Thanks in advance
>>> Trav
>>>
>>>
>>> <jmsBridgeConnectors>
>>> <jmsQueueConnector
>>> outboundQueueConnectionFactory="#remoteFactory">
>>> <inboundQueueBridges>
>>> <inboundQueueBridge
>>> inboundQueueName="com.blah.in.>" / >
>>> </inboundQueueBridges>
>>> <outboundQueueBridges>
>>> <outboundQueueBridge
>>> outboundQueueName="com.blah.outbound.*" />
>>> </outboundQueueBridges>
>>> </jmsQueueConnector>
>>> </jmsBridgeConnectors>
>>
>
Re: JMS-JMS bridge and wildcards
Posted by Travis Endersby <tr...@gmail.com>.
apache-activemq-5.1.0
On Aug 1, 2008, at 1:46 AM, Rob Davies wrote:
> that's an odd one - which version are you using?
>
> cheers,
>
> Rob
>
> On 31 Jul 2008, at 18:00, Travis Endersby wrote:
>
>> Hi Folks,
>>
>> I am looking to bridge many queues, such as "com.blah.foo" ,
>> "com.blah.bar", "com.blah.nOtherThings" between some jms servers.
>>
>>
>> This is working great with the below type of set up, in that all
>> messages get accross ...Yet they lose their actual topic/queue name
>> and come in as the actual wildcard queue itself).
>>
>> ie; how do I make sure that "com.blah.in.foo" comes across as
>> "com.blah.in.foo" instead of "com.blah.in.<"
>>
>> Thanks in advance
>> Trav
>>
>>
>> <jmsBridgeConnectors>
>> <jmsQueueConnector
>> outboundQueueConnectionFactory="#remoteFactory">
>> <inboundQueueBridges>
>> <inboundQueueBridge
>> inboundQueueName="com.blah.in.>" / >
>> </inboundQueueBridges>
>> <outboundQueueBridges>
>> <outboundQueueBridge
>> outboundQueueName="com.blah.outbound.*" />
>> </outboundQueueBridges>
>> </jmsQueueConnector>
>> </jmsBridgeConnectors>
>
Re: JMS-JMS bridge and wildcards
Posted by Rob Davies <ra...@gmail.com>.
that's an odd one - which version are you using?
cheers,
Rob
On 31 Jul 2008, at 18:00, Travis Endersby wrote:
> Hi Folks,
>
> I am looking to bridge many queues, such as "com.blah.foo" ,
> "com.blah.bar", "com.blah.nOtherThings" between some jms servers.
>
>
> This is working great with the below type of set up, in that all
> messages get accross ...Yet they lose their actual topic/queue name
> and come in as the actual wildcard queue itself).
>
> ie; how do I make sure that "com.blah.in.foo" comes across as
> "com.blah.in.foo" instead of "com.blah.in.<"
>
> Thanks in advance
> Trav
>
>
> <jmsBridgeConnectors>
> <jmsQueueConnector
> outboundQueueConnectionFactory="#remoteFactory">
> <inboundQueueBridges>
> <inboundQueueBridge
> inboundQueueName="com.blah.in.>" / >
> </inboundQueueBridges>
> <outboundQueueBridges>
> <outboundQueueBridge
> outboundQueueName="com.blah.outbound.*" />
> </outboundQueueBridges>
> </jmsQueueConnector>
> </jmsBridgeConnectors>
JMS-JMS bridge and wildcards
Posted by Travis Endersby <tr...@gmail.com>.
Hi Folks,
I am looking to bridge many queues, such as "com.blah.foo" ,
"com.blah.bar", "com.blah.nOtherThings" between some jms servers.
This is working great with the below type of set up, in that all
messages get accross ...Yet they lose their actual topic/queue name
and come in as the actual wildcard queue itself).
ie; how do I make sure that "com.blah.in.foo" comes across as
"com.blah.in.foo" instead of "com.blah.in.<"
Thanks in advance
Trav
<jmsBridgeConnectors>
<jmsQueueConnector
outboundQueueConnectionFactory="#remoteFactory">
<inboundQueueBridges>
<inboundQueueBridge
inboundQueueName="com.blah.in.>" / >
</inboundQueueBridges>
<outboundQueueBridges>
<outboundQueueBridge
outboundQueueName="com.blah.outbound.*" />
</outboundQueueBridges>
</jmsQueueConnector>
</jmsBridgeConnectors>
Re: Camel and JMX
Posted by Yari Marchetti <ya...@staff.dada.net>.
Resolved.
I was able to use the JVM Mbean server with:
<camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring">
<jmxAgent id="Camel-JMX-Agent"
usePlatformMBeanServer ="true"
createConnector="true" />
.
.
.
</camel>
Yari Marchetti ha scritto:
> Hi,
> i already enabled the JMX for ActiveMQ, and it's working well, but I'm
> stuck on getting it
> to work under Camel.
> In my activemq.xml i have:
>
> <broker xmlns="http://activemq.apache.org/schema/core"
> brokerName="Test"
> dataDirectory="${activemq.base}/var/"
> useJmx="true" >
> .
> .
> .
> <managementContext>
> <managementContext connectorPort="61611"
>
> jmxDomainName="org.apache.activemq" />
> </managementContext>
> </broker>
>
>
> <camelContext id="camel">
> <jmxAgent id="agent" mbeanObjectDomainName="org.apache.camel"
>
> mbeanServerDefaultDomain="org.apache.camel" />
> <route>
> <from uri="activemq:dadanet.events.incoming"/>
> <to uri="activemq:dadanet.events.GSA_LOG" />
> </route>
> </camelContext>
>
> I have tried several different setups but Camel doesn't seem to
> register to the default JVM
> MBean server, like ActiveMQ does.
>
> any clues?