[I] [Bug] Keep-alive timeout when send/receive large message [pulsar-client-cpp]

["TCGOGOGO (via GitHub)" <gi...@apache.org>]

TCGOGOGO opened a new issue, #425:
URL: https://github.com/apache/pulsar-client-cpp/issues/425

   ### Search before asking
   
   - [X] I searched in the [issues](https://github.com/apache/pulsar-client-cpp/issues) and found nothing similar.
   
   
   ### Version
   
   client 3.2
   server 3.2.2
   
   ### Minimal reproduce step
   
   use a producer to send one 300M message to the broker using synchronous mode
   
   ### What did you expect to see?
   
   send successfully
   
   ### What did you see instead?
   
   2024-04-28 16:58:11.157 WARN  [40520] D:\a\pulsar-client-cpp\pulsar-client-cpp\lib\ClientConnection:1158 | [10.214.4.3:49457 -> 8.218.192.194:6650] Forcing connection to close after keep-alive timeout
   2024-04-28 16:58:11.157 ERROR [40520] D:\a\pulsar-client-cpp\pulsar-client-cpp\lib\ClientConnection:1234 | [10.214.4.3:49457 -> 8.218.192.194:6650] Connection closed with ConnectError
   
   ### Anything else?
   
   When I use asynchronous mode in the producer side, this issue is mitigated, while the consumer stuck into it. I find the keepalive interval is hardcoded in ClientConnection.cc and the value is 30 seconds, and I also find it executed by a deadline timer which run in a separated thread, thus I am not sure if this has something to do with the large message sending or receiving
   
   
   ### 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