Re: Network of brokers acknowledgments

emq.apache.org/networks-of-brokers.html). > > > Cheers, > Felix > > > > Carlos Quiroz wrote: >> >> Hi >> >> I have been trying to use a network of brokers to get load balancing and >> scale horizantally >> >> Right now I have a single

Network of brokers acknowledgments

;; persistent="true" populateJMSXUserID="true" brokerName="brokerB" advisorySupport="true" useJmx="true"> Thanks for any help Carlos Quiroz -- View this

Sometimes Recovering Durable Subscribers fail

n the next restart the messages reapper. I have tried searching the code and even found this bug which was claimed to be fixed. https://issues.apache.org/activemq/browse/AMQ-1500 Any ideas? Is there recovery always done, should it be forced somehow? Regards Carlos Quiroz -- View this message

Expired messages never disappear

s expired messages so I don't use a DLQ shouldn't they just disappear. If I do send them to the DLQ and process them, should they disappear then? PS- I'm using AMQ 5.1 and the default persistent storage. Regards Carlos Quiroz -- View this message in context: http

Re: User Name and Password Invalid when going to localhost/admin

. Regards Carlos Quiroz mardo wrote: > > Im getting teh following error when trying to browse /admin > > HTTP ERROR: 500 > User name or password is invalid. > RequestURI=/admin/queueBrowse/jcsd > > Caused by: > javax.jms.JMSException: User name or pass

Re: Authentication problem in AMQ 5.1

idea of making it a JMX bean sounds quite sensible Regards Carlos Quiroz ttmdev wrote: > > I think what is happening is that you haven't given everyone all access > rights to the advisory topics. I get a similar stack trace when I don't do > that. Add an ACL with the follow

Re: Authentication problem in AMQ 5.1

t looks like you don't have "myqueue" created, so ActiveMQ tries to do > that > with supplied credentials. Try creating the queue manually if you don't > want > to use "admin" priviledges. > > Regards > -- > Dejan Bosanac > www.scriptinginja

Authentication problem in AMQ 5.1

Hi I have been using AMQ 5.0 for a while and I have created my own authentication plugin. When I switched to AMQ 5.1 my clients cannot connect anymore because somehow they are not authorized to create topics or queues. Apparently now when subscribing to a topic/queue you need to have admin permis

Bug when setting transport.keepAlive

somehow by either change TcpTransport.setKeepAlive or by adding property editors to IntrospectionSupport. Regards Carlos Quiroz -- View this message in context: http://www.nabble.com/Bug-when-setting-transport.keepAlive-tp14314131s2354p14314131.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.