Closed rafael-polakiewicz closed 4 months ago
@rafael-polakiewicz What is the env in which the consumer is running?
can you try this version: npm i pulsar-client@1.11.1-rc.2 --pulsar_binary_host_mirror=https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/
Debian
system.The version pulsar-client@1.11.1-rc.2
works for me. Environment details:
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:
test-pulsar@1.0.0 /[path redacted]/projects/winston/test-pulsar
└── pulsar-client@1.11.1-rc.2
Thank you, @shibd !! Using v1.11.1 fixed the problem
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.