Stop - Unsubscribe

Stop Unsubscribe Unless stated otherwise above: Kyndryl España, S.A.U. Calle Albacete, 5 28027 Madrid Registro Mercantil de Madrid; Folio 160; Tomo 41674; Hoja M-738231 CIF A-04975934

Info about versions of ActiveMQ Classic and End of Life/End of Support

Hello everyone. Can someone tell me what versions of ActiveMQ Classic have been released to date and the End of Life/End of Support dates for each of those versions? Thank you very much in advance. Carlos Barrie Aladrén T&T Project Manager carlos.barrie.alad...@kyndryl

Re: Network of brokers acknowledgments

Hi Thanks for the tip. I'll try this next it seems that at least in paper this should do what I want Carlos fehm wrote: > > Hi, > > > you may want to try to enable dynamicOnly=true in the NetworkConnector > properties. > please check here (http://activ

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

Hi and thanks for your response Maybe I should add that the queue is in the startup set and that in the logs appears as it has been created This worked fine in AMQ 5.0 Carlos Dejan Bosanac wrote: > > Hi Carlos, > > i

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.

[no subject]

How can I send 1G of information using JMS , Java

Re: Cannot create destinations at startup when they have authorization requirements

SHOT/ I'm checking out the trunk using svn instead, but I thought maybe you'd like to know that it looks like it's been a while since the SNAPSHOT repository has been updated. Carlos James.Strachan wrote: > > Ah good catch. We need to fix that. > > I've raised the fo

Re: Cannot create destinations at startup when they have authorization requirements

I will, thanks. Carlos James.Strachan wrote: > > Ah good catch. We need to fix that. > > I've raised the following JIRA... > http://issues.apache.org/activemq/browse/AMQ-1157 > > I've checked in a patch which should work to trunk if you fancy giving it

Cannot create destinations at startup when they have authorization requirements

apshot from some days ago, but the same thing happens. Thanks, Carlos The exception stack trace: 2007-02-07 12:10:04,000 [main ] ERROR BrokerService - Failed to start ActiveMQ JMS Message Broker. Reason: java.lang.SecurityException: User is not authenticated. java.lan