Bumping this up again. I'm sorry but after numerous tests, i still cannot figure out why this does not work. Questions on other boards / sites have not been answered either. Anyone who knows the in's and out's of Advisory.Connection ?
Michel Van Hoof wrote: > > Hi, > > We are implementing a solution where we look at advisory topics to > register logon and logoff of a client. This worked fine in our test setup > but now that we are setting up our production infrastructure, i noticed > that these messages are not forwarded through our network of brokers. Is > this correct? > > Should I set a consumer to every activemq broker we would put in the > network to monitor these messages ? Or work with a camel router to copy > the information to a queue which then can be consumed elsewhere ? > > Can i staticallyIncluded the advisory topics in the networkconnector ? > -- View this message in context: http://old.nabble.com/ActiveMQ.Advisory.Connection-not-forwarded-in-network-of-brokers--tp27852378p29233916.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
