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

[Bug] scheduled tasks exiting because of OutOfDirectMemoryError #8124

Closed
3 tasks done
colin719 opened this issue May 13, 2024 · 1 comment · Fixed by #8121
Closed
3 tasks done

[Bug] scheduled tasks exiting because of OutOfDirectMemoryError #8124

colin719 opened this issue May 13, 2024 · 1 comment · Fixed by #8121

Comments

@colin719
Copy link
Contributor

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

OS: ubuntu lts 22.04

RocketMQ version

branch 4.9.x / develop

JDK Version

jdk8 later

Describe the Bug

If a memory overflow error occurs when DeliverDelayedMessageTimerTask executes executeOnTimeUp, the task cannot continue to be registered for execution. As a result, delayed messages, retrieval messages, etc. will no longer be distributed.

Steps to Reproduce

Modify the jvm parameters, set a smaller direct-memory memory, and continuously send delay or retry messages. If the accumulation reaches a certain level, similar errors may occur.

What Did You Expect to See?

Print error log, but do not exit DeliverDelayedMessageTimerTask

What Did You See Instead?

DeliverDelayedMessageTimerTask exit forever

Additional Context

image
image
image

@colin719
Copy link
Contributor Author

please merge ##8132 for 4.9.x @RongtongJin

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

Successfully merging a pull request may close this issue.

1 participant