Hi,
1: I am using Apche.NMS for subcribing to a topic. My problem is that when i
close the ActiveMQ session and Consumer resources it does it without any
error. But when i next time make a new connection with the same client id it
does not allows as the same client is already in connection.
Plea
I tried setting this on the client side as part of the uri I pass to the
factory. It didn't seem to make any difference. I haven't tried tweaking the
message broker itself.
Timothy Bish wrote:
>
> On Fri, 2009-05-08 at 11:32 -0700, Bruce Brown wrote:
>> I have a activemq-cpp consumer, consuming
For a client failover connection the network: uri is unnecessary (i.e.
network connectors are for broker to broker connections). I think something
like the uri below should work.
failover://(tcp://master1:0,tcp://slave1:0,tcp://master2:0,tcp://slave2:0))?randomize=false
/Dave
On Fri, May 8, 2009
On Fri, 2009-05-08 at 11:32 -0700, Bruce Brown wrote:
> I have a activemq-cpp consumer, consuming from a topic.
> It is using CLIENT_ACKNOWLEDEGE.
> I'm not setting a message listener, and am instead polling via receive(10).
> I ack the message upon receipt.
>
> Everything works well as long as I
I see an expected log output from ActiveMQ when my masters and slaves are up
yet since slave 2 is not making inbound/outbound connections unless its
Master is down, and it is included in my failover, that master 1 keeps
trying to connect to slave 2. Is there a strategy for a master 1 (such as
the
I have a activemq-cpp consumer, consuming from a topic.
It is using CLIENT_ACKNOWLEDEGE.
I'm not setting a message listener, and am instead polling via receive(10).
I ack the message upon receipt.
Everything works well as long as I keep sending messages to the topic. If I
stop sending messages an
