There's really not enough information in this email to let us help you find the problem!
- Firstly: please don't use screenshots to send textual information - many people (myself included) do not load images from unknown sources in emails for security reasons, also many mailing lists will just strip images. In your emails some of the images did arrive but the one with the purported errors did not. So please, if you want help make it easy for us and send an email and just paste the messages using a simple copy and paste (feel free to format though). - Secondly: If you could run the client with debug frame logging turned on then we could see what the client sees at the protocol level and that would tell us if this could be the same bug as the one you mention. You can do this by setting the environment variable PN_LOG to frame when you run your client, so at the command line (on a Unix shell) this will look like: PN_LOG=frame client_cmd ... This information should help us help you. Andrew On Thu, May 9, 2024 at 9:34 AM Uiseman Miranda Araujo <uiseman.miranda.ara...@sherwin.com.invalid> wrote: > 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: > [image: 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: > But looking in the code of 0.38.0 version, we noticed more changes in > those lines: > > 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. >
