BewareMyPower commented on issue #324:
URL: 
https://github.com/apache/pulsar-client-cpp/issues/324#issuecomment-1751640518

   I also observed a similar segfault recently. It happened randomly.
   
   A failed case:
   
   ```
   2023-10-07 15:46:10.026 INFO  [0x16f587000] ClientConnection:1340 | 
[127.0.0.1:60762 -> 127.0.0.1:6650] Connection disconnected
   2023-10-07 15:46:10.026 INFO  [0x16f587000] ConnectionPool:122 | Remove 
connection for pulsar://127.0.0.1:6650
   2023-10-07 15:46:10.026 INFO  [0x16f587000] HandlerBase:141 | 
[persistent://public/default/my-topic, standalone-11-18] Schedule reconnection 
in 0.1 s
   2023-10-07 15:46:10.026 INFO  [0x16f587000] ClientConnection:268 | 
[127.0.0.1:60762 -> 127.0.0.1:6650] Destroyed connection to 
pulsar://127.0.0.1:6650
   zsh: segmentation fault  ./examples/SampleProducer
   ```
   
   A successful case:
   
   ```
   2023-10-07 15:46:46.771 INFO  [0x16f997000] ClientConnection:1340 | 
[127.0.0.1:60787 -> 127.0.0.1:6650] Connection disconnected
   2023-10-07 15:46:46.771 INFO  [0x16f997000] ConnectionPool:122 | Remove 
connection for pulsar://127.0.0.1:6650
   2023-10-07 15:46:46.771 INFO  [0x16f997000] HandlerBase:141 | 
[persistent://public/default/my-topic, standalone-11-26] Schedule reconnection 
in 0.1 s
   2023-10-07 15:46:46.771 INFO  [0x16f997000] ClientConnection:268 | 
[127.0.0.1:60787 -> 127.0.0.1:6650] Destroyed connection to 
pulsar://127.0.0.1:6650
   2023-10-07 15:46:46.872 INFO  [0x16f997000] HandlerBase:81 | 
[persistent://public/default/my-topic, standalone-11-26] Getting connection 
from pool
   2023-10-07 15:46:46.872 INFO  [0x16f997000] ClientConnection:188 | [<none> 
-> pulsar://127.0.0.1:6650] Create ClientConnection, timeout=10000
   ```
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to