You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by rajesha_s <ra...@coreobjects.com> on 2007/10/19 17:18:27 UTC
Using static Transport - messages not reliably reaching consumers
on different machines
I have two brokers configured to use the static transport on two different
machines.
I have producers sending messages on each of the machines sending messages
to specific topics to the local broker.
Also, I have consumers that are configured to recieve messages on each of
these boxes as follows -
Machines - A and B
Producer on A publishes to two topics as follows
message1.A and message2.A
Producer on B publishes to two topics as follows
message1.B and message2.B
Consumer on A listens for following topics
message1.A and message2.* (we want to subscribe to message2 from both the
machines A and B)
Consumer on B listens for the following topics
message1.B and message2.* (we want to subscribe to message2 from both the
machines A and B)
The problem I am facing is the message2 does not get delivered consistently
from the other box. Sometimes it works but sometimes it just does not come
through
Environment -
Active MQ version 4.1.1
JDK 1.5/1.6
the broker configuration is as below
<beans>
<broker xmlns="http://activemq.org/config/1.0" useJmx="false">
<transportConnectors>
<transportConnector uri="tcp://localhost:62002"/>
</transportConnectors>
<networkConnectors>
<networkConnector
uri="static://(tcp://host1:62002,tcp://host2:62002)"/>
</networkConnectors>
</broker>
</beans>
The clients connect using the url tcp://localhost:62002.
Looking forward for a solution here.
Thanks in advance.
--
View this message in context: http://www.nabble.com/Using-static-Transport---messages-not-reliably-reaching-consumers-on-different-machines-tf4653981s2354.html#a13296795
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Using static Transport - messages not reliably reaching
consumers on different machines
Posted by rajesha_s <ra...@coreobjects.com>.
Looks like the problem seems to be with the use of wild cards. This certainly
is a defect and probably needs to be fixed. It took quite sometime to really
identify this issue. For now I am working around by not using wildcards in
the topic names.
I am hoping that this is fixed in the next release.
rajesha_s wrote:
>
> I have two brokers configured to use the static transport on two different
> machines.
> I have producers sending messages on each of the machines sending messages
> to specific topics to the local broker.
> Also, I have consumers that are configured to recieve messages on each of
> these boxes as follows -
>
> Machines - A and B
> Producer on A publishes to two topics as follows
> message1.A and message2.A
> Producer on B publishes to two topics as follows
> message1.B and message2.B
>
> Consumer on A listens for following topics
> message1.A and message2.* (we want to subscribe to message2 from both the
> machines A and B)
>
> Consumer on B listens for the following topics
> message1.B and message2.* (we want to subscribe to message2 from both the
> machines A and B)
>
> The problem I am facing is the message2 does not get delivered
> consistently from the other box. Sometimes it works but sometimes it just
> does not come through
>
> Environment -
> Active MQ version 4.1.1
> JDK 1.5/1.6
>
> the broker configuration is as below
> <beans>
>
> <broker xmlns="http://activemq.org/config/1.0" useJmx="false">
>
> <transportConnectors>
> <transportConnector uri="tcp://localhost:62002"/>
>
> </transportConnectors>
>
> <networkConnectors>
> <networkConnector
> uri="static://(tcp://host1:62002,tcp://host2:62002)"/>
> </networkConnectors>
>
> </broker>
>
> </beans>
>
> The clients connect using the url tcp://localhost:62002.
>
> Looking forward for a solution here.
> Thanks in advance.
>
--
View this message in context: http://www.nabble.com/Using-static-Transport---messages-not-reliably-reaching-consumers-on-different-machines-tf4653981s2354.html#a13699873
Sent from the ActiveMQ - User mailing list archive at Nabble.com.