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

The timed task that cleans up messages consumed over time unexpectedly exits #1097

Closed
ssssssnake opened this issue Mar 19, 2019 · 0 comments
Closed

Comments

@ssssssnake
Copy link
Contributor

image

If the previous message in msgTreeMap has been removed and is still being consumed, (imagine a situation in which consumption takes a very long time), then the first message in msgTreeMap will not have a "CONSUME_START_TIME" property, which causes a null pointer exception when Long.parseLong is invoked

@yuz10 yuz10 added the type/bug label Dec 20, 2021
@yuz10 yuz10 closed this as completed Dec 20, 2021
@yuz10 yuz10 added this to the 4.9.3 milestone Dec 20, 2021
tianliuliu pushed a commit to tianliuliu/rocketmq that referenced this issue Dec 21, 2021
devfat pushed a commit to devfat/rocketmq that referenced this issue Mar 3, 2022
GenerousMan pushed a commit to GenerousMan/rocketmq that referenced this issue Aug 12, 2022
carlvine500 pushed a commit to carlvine500/rocketmq-apache that referenced this issue Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants