We are experiencing issues maintaining communication with Solace using AMQP. The base code is an example from Solace's GitHub<https://github.com/SolaceSamples/solace-samples-amqp-qpid-proton-python>. Sometimes, we are encountering the following error: [A close up of a text Description automatically generated] Additionally, there are situations where even when the application pods are down, Solace continues to indicate that the client is connected. Another scenario is that at times the pods are connected to Solace, but no messages from the queue are being consumed. The only solution to fix this is to restart manually, which would be a critical problem in a production environment. After a lot of research, we found this similar issue on your Jira: https://issues.apache.org/jira/browse/PROTON-2098. The solution for it was commited as showed in the picture bellow: [https://lh7-us.googleusercontent.com/YWu1utXdvCFdkDI9-3P9BC8xzRx7kijImJScggAYncgSl3kVaBPAcZ1RUL395yt5rWcYheKNz4ZQp5wttDBZ6fmza-b2c8p5DdTw2mIpBbYoilNrZaVa9ymDbLrQ6AwlSIPKHIPC5C5TG4XcTXwoiEI] But looking in the code of 0.38.0 version, we noticed more changes in those lines: [https://lh7-us.googleusercontent.com/hwGRkzNZCvRFqcbcHn0VZwGMjoAZrSxvhw-FW1lsigk-VkWLmc_4vULenDL0pco5t4XNqWnvtDXKfAjjnu-jSunzXFIyp6TqP7QAQW25qy0ymfOx42mUDOHzRjPhgjQO753aMixxziF3oxznX-Ckncs]
As this issue was already solved before, maybe some changes on newer versions brought that bug again. So, we're counting with you to assist us with diagnosing and resolving this matter.
