You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "gaozhangmin (via GitHub)" <gi...@apache.org> on 2025/06/16 03:30:09 UTC
[I] [Bug] Cannot read field mbean because finalML is null #24410 [pulsar]
gaozhangmin opened a new issue, #24411:
URL: https://github.com/apache/pulsar/issues/24411
### Search before reporting
- [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Read release policy
- [x] I understand that [unsupported versions](https://pulsar.apache.org/contribute/release-policy/#supported-versions) don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.
### User environment
version: 3.3.6
### Issue Description
I noticed that PR #14606 attempted to fix this issue but was closed with the note that it had already been addressed in PR #12103. However, after checking the code in Pulsar 3.3.6, I can confirm that the fix from PR #12103 is present, yet the issue still persists. This suggests that the previous fix may not have fully resolved the problem.
### Error messages
```text
```
### Reproducing the issue
It's hard to reproduce it
### Additional information
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] Cannot read field mbean because finalML is null #24410 [pulsar]
Posted by "lhotari (via GitHub)" <gi...@apache.org>.
lhotari commented on issue #24411:
URL: https://github.com/apache/pulsar/issues/24411#issuecomment-2988458844
> I noticed that PR [#14606](https://github.com/apache/pulsar/pull/14606) attempted to fix this issue but was closed with the note that it had already been addressed in PR [#12103](https://github.com/apache/pulsar/pull/12103). However, after checking the code in Pulsar 3.3.6, I can confirm that the fix from PR [#12103](https://github.com/apache/pulsar/pull/12103) is present, yet the issue still persists. This suggests that the previous fix may not have fully resolved the problem.
Your case is different than #14606 or #12103.
https://github.com/apache/pulsar/blob/c1c18d6872bd2e824ed87f7b974191813eb4b987/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/OpAddEntry.java#L334-L346
In your case, the NPE happens on line 339, before the lambda code block that is executed within the executor.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] Cannot read field mbean because finalML is null #24410 [pulsar]
Posted by "zhannao456 (via GitHub)" <gi...@apache.org>.
zhannao456 commented on issue #24411:
URL: https://github.com/apache/pulsar/issues/24411#issuecomment-2989649773
> [@gaozhangmin](https://github.com/gaozhangmin) Have you configured `managedLedgerAddEntryTimeoutSeconds` to some value? If it's non-zero, it's possible that this is a bug in the `managedLedgerAddEntryTimeoutSeconds` feature. It seems that race conditions are possible which could lead to the NPE that you are seeing.
managedLedgerAddEntryTimeoutSeconds is configured in my case。 i need some time, since it's hard to reproduce
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] Cannot read field mbean because finalML is null #24410 [pulsar]
Posted by "lhotari (via GitHub)" <gi...@apache.org>.
lhotari commented on issue #24411:
URL: https://github.com/apache/pulsar/issues/24411#issuecomment-2988490279
@gaozhangmin Have you configured `managedLedgerAddEntryTimeoutSeconds` to some value? If it's non-zero, it's possible that this is a bug in the `managedLedgerAddEntryTimeoutSeconds` feature. It seems that race conditions are possible which could lead to the NPE that you are seeing.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] Cannot read field mbean because finalML is null #24410 [pulsar]
Posted by "gaozhangmin (via GitHub)" <gi...@apache.org>.
gaozhangmin commented on issue #24411:
URL: https://github.com/apache/pulsar/issues/24411#issuecomment-2989650887
> [@gaozhangmin](https://github.com/gaozhangmin) Have you configured `managedLedgerAddEntryTimeoutSeconds` to some value? If it's non-zero, it's possible that this is a bug in the `managedLedgerAddEntryTimeoutSeconds` feature. It seems that race conditions are possible which could lead to the NPE that you are seeing.
managedLedgerAddEntryTimeoutSeconds was configured in my case, i need some time, since it's hard to reproduce
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org