We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
async write message to broker with sendAsync, when client can't connect broker, run producer.Flush() raise panic.
sendAsync
producer.Flush()
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1004f487d] goroutine 135 [running]: sync.(*Once).Do(...) /usr/local/go/src/sync/once.go:63 github.com/apache/pulsar-client-go/pulsar.(*partitionProducer).failTimeoutMessages(0xc00018a6c0) /Users/ruifengyun/go/pkg/mod/github.com/apache/pulsar-client-go@v0.11.0/pulsar/producer_partition.go:993 +0x6dd created by github.com/apache/pulsar-client-go/pulsar.newPartitionProducer in goroutine 134 /Users/ruifengyun/go/pkg/mod/github.com/apache/pulsar-client-go@v0.11.0/pulsar/producer_partition.go:200 +0x97f FAIL gitlab.planetmeican.com/titan/logclick-fluentbit/pkg/pulsar 195.365s
First use write some data, and then kill pulsar. When producer.flush is called, this problem will occur.
I see you have solved the problem, please release a new version?
pulsar-client-go: v0.11.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected behavior
async write message to broker with
sendAsync
, when client can't connect broker, runproducer.Flush()
raise panic.Actual behavior
Steps to reproduce
First use write some data, and then kill pulsar. When producer.flush is called, this problem will occur.
I see you have solved the problem, please release a new version?
System configuration
pulsar-client-go: v0.11.0
The text was updated successfully, but these errors were encountered: