Hi Bryan, The Virtual Host Housekeeping checks on the Broker-J server handle various maintenance tasks, such as checking file system space, checking the status of messages, processing delayed messages, purging expired ones, firing age-related alerts, etc..
Reducing the Virtual Host Housekeeping check period to 3 seconds will cause these tasks to be performed more frequently. If the broker has a large volume of messages in its queues, this increased frequency could lead to higher CPU and memory utilization. While this may not be an issue for most systems, it may be beneficial to monitor the broker’s performance, particularly under heavy (peak) load conditions. Best regards, Tomas On 2024/08/14 13:37:04 Bryan Dixon wrote: > We have an application using qpid-jms-client 2.5 and JMS 2.x Delivery Delay > feature. Our application delays are fairly quick - 5 to 10 seconds. > Broker-J was delivering messages after around 20+ seconds instead of 5-10 > seconds. After enabling debug logging on the Broker-J server, I found that > a Housekeeping thread appeared to deliver these delayed messages. So I > changed the Virtual Host House keeping check period (ms) setting to 3 seconds > (3000 milliseconds) and that seemed to fix the delivery of messages to be > more timely, and messages were delivered close to the delay of 5 to 10 > seconds the application needed. I wanted to make sure this change to the > Housekeeping setting was the appropriate change to make since 3 seconds is > quite a bit shorter than the default of 30 seconds. Will this setting > change cause any adverse effects on the Broker-J server itself? > > We are running Broker-J 9.0.0 with Java 11 on Windows Server 2019. > > Bryan > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
