Re: Network of Brokers - publishing on broker x - consuming on broker 1...n

Hello, might be - but should a "strictOrderDispatchPolicy" not just simply ensure the order of the received messages to be consumed also in that order no matter whether it's one or more consumers? - C. elliottjf wrote: > > any chance that this issue could be related to the behavior of "exclu

Re: Network of Brokers - publishing on broker x - consuming on broker 1...n

Ok, this is aboutthe forward on demand bridge, or? So is there an ALWAYS FORWARD bridge? - C. Marlon Santos wrote: > > HI, > > The message will not be available to consumers on other brokers mainly > because messages are forwarded based on demand.. so it will be forwarded > only to other brok

Re: problem with Master/Slave and Persistence

Thank you for you reply. I am sure the Master and Slave broker name is different. but both Master and Slave is trying to access the same resource. Master Config: == http://activemq.org/config/1.0";> =

Re: problem with Master/Slave and Persistence

I think the first thing to try is to ensure that your master broker and slave broker have different broker names. It looks like they are on the same box, with the same name, both trying to access the same resource Rob Davies http://rajdavies.blogspot.com/ On 1 Feb 2007, at 04:17, richo w

Re: activemq cms stomp - creating a topic from message->getCMSReplyTo() does not work

Hi Nathan- Requesting to reopen the issue given at https://issues.apache.org/activemq/browse/AMQCPP-64 I had already tried the solution you have provided ... it throws a StompException It is some kind of a inconsistency between how activemq uses stomp ... http://www.nabble.com/file/6142/S

problem with Master/Slave and Persistence

I am sorry to trouble you,but I had some problem can not solve by reading document. 1、I'm run activeMQ in Master/Slave Mode,and run successful. Persistence configuration: I'am start one Master broker and two Slave broker. but a)the Slave broker will auto shutdown after about 3

Re: Network of Brokers - publishing on broker x - consuming on broker 1...n

HI, The message will not be available to consumers on other brokers mainly because messages are forwarded based on demand.. so it will be forwarded only to other brokers when there are consumers for the message. Regards cbu wrote: > > Hi, > > both brokers named differently. It seems it wa

Re: Use jencks to async receive message, there are always some messages are left in the queue

Attachment is our code, "src" directory is our jms client lib, it's required libs is in "lib.txt"; "test" is our test case gnodet wrote: > > If you could set up a reproducible test case against activemq > trunk, please raise a JIRA and attach your test. > > On 1/31/07, Waves <[EMAIL PROTECTED]>

list moved

This list has moved to [EMAIL PROTECTED] The old address still works, but from this point forward you should use the new one. -- Joe Schaefer

Re: Network of Brokers - publishing on broker x - consuming on broker 1...n

any chance that this issue could be related to the behavior of "exclusive consumer" queues on a distributed network? i'm still trying to figure out if that is supported or not. - joe cbu wrote: > > NEW FINDING! > > if you set this policy - queue messages are not distributed on a network: