Hello,
I'm having an issue when sending a number of messages that starts producer
flow control between two brokers and when the networkConnector between the
two is setup as duplex. The setup I have is I have two brokers, A and B. I
also have two consumers on B subscribed to two topics, topic1 a
I tried that last suggestion and it appears as though
the allowTempAutoCreationOnSend is not working. The client keep receiving a
"cannot send to a deleted destination" error.
Chris
On Mon, May 14, 2012 at 4:19 PM, Gary Tully wrote:
> this is expected, but the flooding impact should be minimal
Gary wrote:
> ... you may need to configure keep alive on the broker transport connector ...
I had tried setting that on the broker transport that the client uses, but saw
zero traffic between the client and the broker. I'm guessing that it is only
useful when set on the broker's end, which is w
the client sees the disconnect due to the firewall, but does the
broker see the same disconnect? you may need to configure keep alive
on the broker transport connector to ensure that it sees the client
disconnect.
You can check via jmx (jconsole), to verify that the consumer goes
away. If it remain
One of the two issues has been resolved. The connection being reset was due to
a firewall, between the broker and consumer, closing port 61616 due to
inactivity. We've had the folks who maintain the firewall change its
configuration so that it no longer does that.
I'm still very troubled by the
I am using similar set up as described by jessezbj in the earlier post.
I am having four brokers on the same machine.
All the brokers have same brokername, but listen on different ports.
I am not using multi-cast and auto-discovery.
The problem is, if one of the broker hangs, rest of the broke
