-
Notifications
You must be signed in to change notification settings - Fork 86
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] Segmentation Fault when using Pulsar Consumer batchReceive #390
Comments
@rafael-polakiewicz What is the env in which the consumer is running? can you try this version: |
#389 can resolve batch_recieve crash issue when the consumer running on |
The version Node.js version:
v18.13.0
npm version:
8.19.3
Operating System details:
Linux [hostname redacted] 6.5.0-41-generic #41~22.04.2-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 3 11:32:55 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
LSB release information:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
Package versions:
[email protected] /[path redacted]/projects/winston/test-pulsar
└── [email protected] |
v1.11.1 has been released, I think it can resolve this issue. |
Description
I encountered a segmentation fault using pulsar consumer batch receive method. The consumer process terminates unexpectedly with a segmentation fault.
Node and pulsar-client info
Steps to Reproduce
1. Start a local instance of Pulsar
Use the following docker-compose file to start a Pulsar instance:
2. Create a simple consumer script
Save the following code in a file named consumer.js:
3. Run the consumer script
Execute the script using the following command:
4. Create a producer script
Save the following code in a file named producer.js:
5. Populate the topic
Execute the producer script using the following command:
Expected Behavior
The consumer should process and acknowledge messages without errors.
Actual Behavior
The consumer process ends with the following message:
Additional Information
I found that the feature request to support batch receive was closed. Am I doing something wrong here, or is this a bug?
Please let me know if you need any further information.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered: