Re: Slow performance to handle over 60,000 wildcard topics with 2,000msg/s

I set authorizationPlugin plugin as belolw, assign "user" can create & publish any queues and topics. When I publish 2,000 message/sec with 60,000 wildcard topics (E.g. stock.01), whole ActiveMQ server performance is down, CPU usage eat up to 50% and too many topic JMS messages are pending in

Re: Slow performance to handle over 60,000 wildcard topics with 2,000msg/s

Can you provide any details from your root-cause analysis that shed light onto the specific problem and how it might be solved? ActiveMQ is a community project, and I personally trust that all community members are working in good faith to help improve it. I'm not sure I'd say there is a special

Re: Slow performance to handle over 60,000 wildcard topics with 2,000msg/s

Sorry, I isolated the problem the root cause is *authorizationPlugin *not simpleAuthenticationPlugin -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Actively persistentstore is full

I found that the sum of all the .log files sizes is 100G and found that when there is an unprocessed message left in queue, activemq is not going to delete the .log file unless all messages inisde are processed completely. So in my case there are old unprocessed messages in the queues which made

Re: Slow performance to handle over 60,000 wildcard topics with 2,000msg/s

This is bad solution. I figured out that if implemented simpleAuthenticationPlugin for security control, it will cause this problem even standalone ActiveMQ. If removed simpleAuthenticationPlugin from activemq.xml, the problem is solved. simpleAuthenticationPlugin is root cause, ActiveMQ

Network of Brokers + verifyHostName=false

We're unable to get the our network of brokers connector to work without hostname verification. Is there something wrong with this? ``` ``` And it's failing with: ``` javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching

Re: ActiveMQ web console better than Artemis?

Thank you so much. It makes sense. This is what I was looking for :) -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: ActiveMQ version compatibility with Postgresql

Thanks Tim for the Response. Sure, will post here if I come across any compatibility issues. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Camel Routing places KahaDB in an unexpected place

Thank you for all of those explanations. The first solution (increasing the time between retries) didn't make sense to me, but your final explanation fully explains the behavior. Thanks for sharing the information with the list, to help anyone who hits this in the future. Tim On Wed, Feb 6,

Re: Unwanted (unsolicited) messages from ActiveMQ.Advisory.MasterBroker

So wait, I understood you to say that the problem was the trailing .> on the name of your topicName element, but in the working example configuration you gave, the trailing .> is still there. What did I misunderstand? Tim On Thu, Feb 7, 2019, 8:21 AM emw I did some tests and outcome is that it

Re: Actively persistentstore is full

>From memory, I think the limit might also include the space taken by the index file, but if your db.data is only 78 MB, the index won't bring you to 100 GB. Can you post the actual error message, and your activemq.xml? Tim On Wed, Feb 13, 2019, 12:52 PM Shekhar Naidu Hi, > We are getting an

Re: Slow performance to handle over 60,000 wildcard topics with 2,000msg/s

If that plugin doesn't do exactly what you want, it's possible to write a custom plugin that's more tuned for your use case. See http://activemq.apache.org/interceptors.html for more information. Tim On Mon, Feb 18, 2019, 3:11 AM Franco Ng I found the cause is that add

ActiveMQ network bridges disconnect frequently with topic

Hi, I have a set of brokers setup with failover configuration as follows: roker A ---> (failover) --> Broker B1 or Broker B2 Application connected to Broker A send event messages via topic, i.e. MyEventTopic. Snapshot of key activemq Broker A configuration

Re: Slow performance to handle over 60,000 wildcard topics with 2,000msg/s

I found the cause is that add simpleAuthenticationPlugin to control security, the the B Broker connect to A Broker with login (define in "networkConnector"). If large no. of topic message sent, it would slow than whole ActiveMQ server. Anyone can help to solve this, thanks. userName="system"