Is there any information we could provide to help find a conclusion?

From: Doug Whitfield <dwhitfi...@perforce.com.INVALID>
Date: Friday, 8 December 2023 at 14:27
To: users@activemq.apache.org <users@activemq.apache.org>
Subject: Messages stuck in schedule queue on ActiveMQ 5.16.3
Hi Team.

I found 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F76438427%2Fpersistent-scheduling-of-activemq-to-disk-leads-to-disk-space-growth&data=05%7C01%7Cdwhitfield%40perforce.com%7Ce473b90fcc9d4b173c6508dbf82c1299%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638376640417734519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=kSGw07Mbd5LMMgqkhWZEMMj2tlPO7fe4bRGXnghlw2Q%3D&reserved=0<https://stackoverflow.com/questions/76438427/persistent-scheduling-of-activemq-to-disk-leads-to-disk-space-growth>

And it makes sense that these would be stuck if something was not acknowledged, 
but how do we go about discovering what has not been acknowledged. Normally, I 
would go to the console, but this is an embedded app without the console. We 
are in the process of testing turning on JMX in the embedded application, but 
what query would be used to find this information?

Also, is there any chance that 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FAMQ-7340&data=05%7C01%7Cdwhitfield%40perforce.com%7Ce473b90fcc9d4b173c6508dbf82c1299%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638376640417734519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Roic6rMW6atIom1xdRucsXVGD2D%2Bs3%2BGIod4Y5LAEh4%3D&reserved=0<https://issues.apache.org/jira/browse/AMQ-7340>
 could be related to these messages getting stuck?

Best Regards,

Douglas Whitfield | Enterprise Architect


This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

Reply via email to