Re: AcativeMQ becomes slow suddenly in 60 minutes after starting a performance test

Hi I faced the same problem with ActiveMQ 5.15.0. Configurations and environments are almost the same with 5.14.3. Hidekazu -- View this message in context: http://activemq.2283324.n4.nabble.com/AcativeMQ-becomes-slow-suddenly-in-60-minutes-after-starting-a-performance-test-tp4728103p4728434

Re: AcativeMQ becomes slow suddenly in 60 minutes after starting a performance test

Dear Tim Thanks for helping me a lot. Let me answer your questions. > Were your IoT processes publishing to queues or topics? Topics > To a single one or to one per client? To a single ActiveMQ broker. > Was anything consuming the messages? Yes, our subscriber consume the topics. > Were

Re: AcativeMQ becomes slow suddenly in 60 minutes after starting a performance test

Thanks! Hidekazu -- View this message in context: http://activemq.2283324.n4.nabble.com/AcativeMQ-becomes-slow-suddenly-in-60-minutes-after-starting-a-performance-test-tp4728103p4728185.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

AcativeMQ becomes slow suddenly in 60 minutes after starting a performance test

08:19:45,059 [eckpoint Worker] ERROR MessageDatabase - Checkpoint failed java.lang.OutOfMemoryError: GC overhead limit exceeded -- Thanks. Hidekazu -- View this message in context: http://activemq.2283324.n4.nabble.com/AcativeMQ-becomes-slow-suddenly-in-60

Re: LifecycleProcessor exception

Dear Tim I can't find a word to thank you!! > In the meantime, did anything actually fail when you did the restart? > Restarting the broker should definitely work without this error, but did > it > have any negative effect other than the scary-sounding message showing up > in the logs? I'm

Re: LifecycleProcessor exception

Thanks Tim! (1) I made sure if my activemq loaded Spring-related JARs by booting activemq with -verbose:class option. There seem to be several Spring-related JARs as follows. /opt/apache-activemq/lib/activemq-spring-5.14.3.jar /opt/apache-activemq/lib/optional/spring-beans-4.1.9.RELEASE.jar

Re: LifecycleProcessor exception

Thanks a lot! I’m sorry for not responding for a while but I don’t forget the feeling of gratitude. In Japan, we had a long holiday called Golden Week and that’s the reason I couldn’t respond to you. Anyway,sorry. I’m running a standalone broker from a clean install. Does my answer make sense?

LifecycleProcessor exception

Hi, Dear All I have an ActiveMQ ver 5.14.3 and had a problem once when restarted it by executing “activemq restart” command. Here are the exceptions in activemq.log. I found there were several posts about this LifecycleProcessor exception in the forum, however, none of them didn’t seem to be the

Re: | WARN | Transport Connection to: tcp://xx.xx.xx.xx:xxxxx failed

Dear Tim Thanks for always helping me understand ActiveMQ. As you told me, it's likely that pollings from an observation server and load balancers would be the reason of a lot of warns. And I'm sorry for not consulting the mailing list beforehand. I'm going to do it from now. Thanks. Hidekazu

| WARN | Transport Connection to: tcp://xx.xx.xx.xx:xxxxx failed

though we have these warnings. However, I'm afraid the warning cause something bad to our system. Can anyone tell me what the warning is? Thanks. hidekazu -- View this message in context: http://activemq.2283324.n4.nabble.com/WARN-Transport-Connection-to-tcp-xx-xx-xx-xx-x-failed-tp4725008

Re: The size of KahaDB doesn't seem to decrease

Dear Tim Thanks for your always help to understand ActiveMQ. I didn't know ActiveMQ first at all but thanks to you , now I became to be confident about it a little. > But let's step back for a second: why are you trying to limit the size of > db.data in the first place? Why is its current size

Re: The size of KahaDB doesn't seem to decrease

Dear Tim Thanks for helping me understand the specification of ActiveMQ. Thanks to you, I understand ActiveMQ more than before. I could delete data.db safely. (Thank you very much!!) By the way, I use ActiveMQ with TOPIC (not queue.) Will I see DLQ in queue tab in ActiveMQ　console when my

Re: The size of KahaDB doesn't seem to decrease

Dear cschneider Thanks to your advice, we could delete data.db safely. I found that activemq.xml had a parameter which limits the cache size. Is the parameter below perhaps for db.data? Or is it different from the limit for db.data because it explains that "cached in memory."

Re: The size of KahaDB doesn't seem to decrease

Dear cschneider Thanks for teaching me a good way to avoid increasing kahaDB. I came to know that dead letter queues are one of keys. By the way, I have two questions. (I'm sorry, I'm ActiveMQ newcomer...) 1. How do I see dead letter queues? I want to make sure whether dead letter queue make

Re: The size of KahaDB doesn't seem to decrease

Dear Tabish121 As you introduced the helpful and fundamental specification of kahaDB to me, the reason of the size of kahaDB kept increasing was really elementary. (I'm sorry) there were a lot of pending queues in ActiveMQ and that was the reason. anyway, your advice was really helpful. thanks a

Re: The size of KahaDB doesn't seem to decrease

Thanks Andreas The article you introduced me was very helpful to understand the specification of kahaDB. I have to say there was a miss-communication among our developer team. I heard that there was no pending queue in ActiveMQ, however, There were a lot of pending queue in ActiveMQ and that

The size of KahaDB doesn't seem to decrease

I use ActiveMQ ver 5.14.3. I thought the size of kahaDB wouldn't get bigger if ActiveMQ could sent data to subscriber. However, the size of kahaDB continues increasing even it can send all the data to subscriber. There is no pending queue in GUI management console. Is there any necessary

Too many PendingQueueSize outoputs compared to the number of DestinationName in activemq query command.

I use activemq 5.9.0 on REDHAT server. I want to use the activemq query command to make sure if messages are sent to a subscriber because we have a trouble with our system that sometimes the broker can't send messages to the subscriber and cause a flow control which stops receiving messages by