-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[pulsar-client] NPE while call getLastMessageId #6561
Comments
sijie
pushed a commit
that referenced
this issue
Mar 19, 2020
### Motivation Fixes #6561 ### Modifications Initialize `BatchMessageAckerDisabled` with a `new BitSet()` Object.
tuteng
pushed a commit
to AmateurEvents/pulsar
that referenced
this issue
Mar 21, 2020
### Motivation Fixes apache#6561 ### Modifications Initialize `BatchMessageAckerDisabled` with a `new BitSet()` Object. (cherry picked from commit 2007de6)
tuteng
pushed a commit
that referenced
this issue
Apr 6, 2020
tuteng
pushed a commit
that referenced
this issue
Apr 13, 2020
jiazhai
pushed a commit
to jiazhai/pulsar
that referenced
this issue
May 18, 2020
### Motivation Fixes apache#6561 ### Modifications Initialize `BatchMessageAckerDisabled` with a `new BitSet()` Object. (cherry picked from commit 2007de6)
huangdx0726
pushed a commit
to huangdx0726/pulsar
that referenced
this issue
Aug 24, 2020
### Motivation Fixes apache#6561 ### Modifications Initialize `BatchMessageAckerDisabled` with a `new BitSet()` Object.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Meet NPE while call getLastMessageId as below:
The reason is that
BatchMessageIdImpl
use a defaultBatchMessageAcker
with null value.Expected behavior
getLastMessageId
should be successful like below:The text was updated successfully, but these errors were encountered: