OK
same experiment today, nothing changed
All my brokers cannot see anymore messages from the other network :)
What kind of behavior is this? How can this be explained? It's confusing!
anybody there?
--
View this message in context:
http://old.nabble.com/Pls-help%21-Making-two-networks-working
So I'm still waiting for an answer.
Is there a better solution for what I need, or at least a way to get read of
these duplicate messages?
Thank you!
Roxana
--
View this message in context:
http://old.nabble.com/Pls-help%21-Making-two-networks-working-together-tp28015144p28038920.html
Sent from
I don't know id I've mentioned that I work with topics not with queues
--
View this message in context:
http://old.nabble.com/Pls-help%21-Making-two-networks-working-together-tp28015144p28026720.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Good and bad news
If I increase networkTTL on the multicast network connector on every broker
(=3 in my example) everybody receives messages from everybody. This is good.
Bad: lots of duplicate messages!
roxanac wrote:
>
> Another experiment that I've tried:
>
> 3 br
Another experiment that I've tried:
3 brokers in network1 (discovering each other through multicast)
3 brokers in network2 (discovering each other through multicast)
I choose one broker from each network to be central point having a static
network connector
to the central point from the other
One of the configuration I've tried looks like this:
Broker1, Broker2 (3) are discovering each other through multicast and
have a static network connector to BrokerOUT. Also each has two
transportConnectors-one for the connections created trought multicast and
another for BrokerIN to connect
ur central brokers having static network
connectors, duplex or simple, to each network, increasing networkTTL,
different combinations of values for network parameters etc etc etc )
So any advice would be welcomed & greatly appreciated because I'm out of
ideas right now!
Thank you
RoxanaC
--
there are durable subscribers the pendingMessageLimitStrategy kicks in
> and first does message expiry, then does message discarding.
>
> On 17 March 2010 09:38, roxanac wrote:
>
>>
>> Hello!
>> I have a problem or at least a thing that is not very clear for me.
>> I am publishing
Hello!
I have a problem or at least a thing that is not very clear for me.
I am publishing non-persistent messages in a topic, having TimeToLive set to
5 seconds for producer and for message also ( I have a C# producer but this
is not that relevant since I get the same behavior with a Java produce
