Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receive frequency #345

Open
the01 opened this issue Feb 11, 2021 · 0 comments
Open

Receive frequency #345

the01 opened this issue Feb 11, 2021 · 0 comments

Comments

@the01
Copy link

the01 commented Feb 11, 2021

I am using a ActiveMQ instance as broker and have long running tasks (1-2 Minutes), so I have set high heartbeat values (~5m).
Also, "activemq.prefetchSize" is set to 1 and the messages are fairly big (one image per message).
It processes the first task fine (and it is ack'd), but then idles for always the same amount of time (I think around 230s) doing nothing, before continuing.
It might be related to the heartbeat as I don't notice this for faster tasks.

Does anybody have an idea how it can continue processing after the completion of the message if there are still messages in the queue?
(I want the prefetchSize low to spread the workload evenly)

p.s.: Usually I have the consumers already running, when I submit the work load which results in this behavior. Coincidentally, this time I happened to start them after filling the queue and now it just ran through.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant