Re: Problem with embedded broker
Perfect! This works that I expected. Thanks. Juan Manuel -- View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-embedded-broker-tp4687370p4687404.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with embedded broker
You can specify that messages should be forwarded even if no consumer is connected by using the staticallyIncludedDestinations element on the networkConnector. See https://access.redhat.com/documentation/en-US/Fuse_ESB_Enterprise/7.1/html/Using_Networks_of_Brokers/files/FMQNetworksMessagePropagation.html for an explanation of static propagation as well as a good illustration of why dynamic propagation is the typical configuration. On Nov 13, 2014 6:12 AM, "juanmanuel.romeraferrio" < juanmanuel.romerafer...@gmail.com> wrote: > This is by default? Can I change that? > What's the best architecture for a system that need send message to a > remote > broker all the time and if the remote broker is offline, need to save this > message in a local queue and send when the connection is established again > ? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Problem-with-embedded-broker-tp4687370p4687401.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
Re: Problem with embedded broker
This is by default? Can I change that? What's the best architecture for a system that need send message to a remote broker all the time and if the remote broker is offline, need to save this message in a local queue and send when the connection is established again ? -- View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-embedded-broker-tp4687370p4687401.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with embedded broker
That's expected behavior. By default, brokers only forward messages when there's a currently-connected consumer somewhere in the network. If there's no consumer, the message will hang out on the producing broker, waiting for the consumer to connect. When it does connect, the broker that holds the message will find out about the consumer and forward the message towards the broker it's connected on. This makes sense when you think about a more-complicated network of brokers where a consumer could reconnect to any broker, not just the one it last connected to; if you forward the message to the last broker the consumer was on, you might find that it's reconnected to a different broker somewhere else (maybe even the one the producer is on!), and now you've got to forward the messages a second time, resulting in wasted network traffic. On Wed, Nov 12, 2014 at 2:02 PM, juanmanuel.romeraferrio < juanmanuel.romerafer...@gmail.com> wrote: > Hi, I'm having a problem in my system. > > In my producer, I have the next configuration. > > > > class="org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter"> > > /> > > > > > > class="org.apache.activemq.broker.BrokerService" > init-method="start" destroy-method="stop" > > > > value="vm://localhost:61617" /> > > > class="org.apache.activemq.network.DiscoveryNetworkConnector"> > value="static:failover:(tcp://queue1-r35-01.desa.emp.com:61616,tcp:// > queue1-r35-02.desa.emp.com:61616)" > /> > > > > ref="kahaDBPersistenceAdapter" /> > > > > class="org.apache.activemq.ActiveMQConnectionFactory"> > > > > > > class="org.springframework.jms.connection.CachingConnectionFactory"> > ref="amqConnectionFactory" /> > > > > > And the problem that I found is that if my consumer is not running, when I > send a message to the remoteBroker this message is showed in the Apache > ActiveMQ Console of the remoteBroker, but when I start the consumer the > message appear and is consumed. > > Why this occur? The message is storage in my localBroker and is not sended > if the consumer is not running? > > Thanks, > Juan Manuel > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Problem-with-embedded-broker-tp4687370.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
Problem with embedded broker
Hi, I'm having a problem in my system. In my producer, I have the next configuration. And the problem that I found is that if my consumer is not running, when I send a message to the remoteBroker this message is showed in the Apache ActiveMQ Console of the remoteBroker, but when I start the consumer the message appear and is consumed. Why this occur? The message is storage in my localBroker and is not sended if the consumer is not running? Thanks, Juan Manuel -- View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-embedded-broker-tp4687370.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.