Maybe my wording was not correct, responses to clients are handled fine
when connection is achieved. The issue is only about the time before the
connection is made and the initial client message shows up in the server
handler. When this happens I will push the message to a queue and return
On Mon, Jun 6, 2022 at 2:17 PM Arjee Jacob wrote:
> Does that mean I have to close the socket after sending each message?
> This is basically running in one device between 2 processes, and messages
> come every 15-60 seconds.
>
No. I think what Gordon was suggesting is that this has nothing
Does that mean I have to close the socket after sending each message?
This is basically running in one device between 2 processes, and messages
come every 15-60 seconds.
On Mon, 6 Jun 2022 at 13:50, Gordon Sim wrote:
> On a server, that log suggests that something is opening a socket to
> the
Personally from the original mail I think its as likely issue lies in
just how the messages are being handled and responses generated. If
adding threads is not helping any, it would only reinforce that view
for me.
Note is made that a single thread is being used, and that messages are
only queued
On a server, that log suggests that something is opening a socket to
the 5672 port, but then not actually transmitting anything over it.
E.g. it could be some kind of L4 probe.
On Mon, Jun 6, 2022 at 8:35 AM Arjee Jacob wrote:
>
> Hey there,
>
> I am getting a message in my logs that says
>
Hey there,
I am getting a message in my logs that says
"[System] error Connection qpid.5672-No protocol received after 60s,
closing"
Any idea what this means? How to rectify it?
Warm Regards,
Jacob
