2009/12/11 ant elder
> Ok, i'll have to think about that option. Going back to what you said
> earlier about statically configured destinations on the network
> connector, is it right that the static destination only needs to be
> configured at the remote end of the network connector?
yea. a ne
Oh, i also meant to ask about retroactive consumers which i stumbled
across on the website -
http://activemq.apache.org/retroactive-consumer.html. That sounded
useful but with a very quick try it looks like the remote broker needs
to be connected before the topic publish happens, does that sound
ri
Ok, i'll have to think about that option. Going back to what you said
earlier about statically configured destinations on the network
connector, is it right that the static destination only needs to be
configured at the remote end of the network connector? Eg without
changing the put code i tried r
interesting... this could work but would have some limitations. If you use a
regular consumer, client ack with prefetch=0 and don't ack, by using a
blocking receive(timeout) - the demand will have time to propagate and the
messages will be visible.
However, because the network is store and forward,
Heh, well its probably not a very valid use case of ActiveMQ - I was
toying with using an ActiveMQ broker network for a sort of simple
distributed storage, with clients able to put a message on a queue and
have other clients read the message nondestructively. None of the
other technologies for that
fraid not. What is your use case?
2009/12/11 ant elder
> I see, thanks for the explanation.
>
> The statically configured destination isn't really an option as the
> queue names aren't known till runtime. Are there any other options
> that might help get the messages forwarded irrespective of de
I see, thanks for the explanation.
The statically configured destination isn't really an option as the
queue names aren't known till runtime. Are there any other options
that might help get the messages forwarded irrespective of demand?
...ant
On Fri, Dec 11, 2009 at 12:40 PM, Gary Tully wro
This is expected. A queue browser takes a shapshot of the queue through a
short lived consumer. The network bridge is by default a demand forwarder,
such that messages are only forwarded when there are consumers on other
brokers.
With the browser, the consumer (and hence demand) is transient, so i
I should have mentioned that this is using ActiveMQ 5.3.0.
...ant
On Fri, Dec 11, 2009 at 12:11 PM, ant elder wrote:
> I'm trying to track down an problem where a queue browser on a VM
> connection to one AMQ broker is sometimes not seeing messages put on a
> queue from a VM connection to ano
I'm trying to track down an problem where a queue browser on a VM
connection to one AMQ broker is sometimes not seeing messages put on a
queue from a VM connection to another broker in the same network. The
code below can recreate the problem, running the put() on JVM and the
browse() on another JV
10 matches
Mail list logo
