Beagle looses connection (after sleep?) and doesn't notice (#621)

Closed

Activities

wojciech.kapcia@tigase.net opened 3 months ago

The issue happens for a long time already. In a nutshell - for some reason quite often beagle looses connection on one account and doesn't notice that the connection is lost. Only way to notice it is:

muc rooms have yellow dot instead of green one
send messages don't get "received" stamp.

In the XML console I see continuous ping request without response (should trigger re-connect?):

<!--   2024-06-29T15:44:44Z   >>>>   -->
<iq to='wojtek@tigase.org' id='AA262C23-878F-4098-A3CA-4F000B537B20' type='get'>
<ping xmlns='urn:xmpp:ping'/>
</iq>

<!--   2024-06-29T15:44:44Z   >>>>   -->
<r xmlns='urn:xmpp:sm:3'/>

<!--   2024-06-29T15:47:39Z   >>>>   -->
<iq type='get' to='wojtek@tigase.org' id='6A0F1B85-8BDA-4773-932A-4A0F4ADD8BB4'>
<ping xmlns='urn:xmpp:ping'/>
</iq>

<!--   2024-06-29T15:47:39Z   >>>>   -->
<r xmlns='urn:xmpp:sm:3'/>

<!--   2024-06-29T15:50:34Z   >>>>   -->
<iq type='get' to='wojtek@tigase.org' id='3B167D83-E43C-4BFD-88F4-5FBF4B6B817A'>
<ping xmlns='urn:xmpp:ping'/>
</iq>

<!--   2024-06-29T15:50:34Z   >>>>   -->
<r xmlns='urn:xmpp:sm:3'/>

<!--   2024-06-29T15:53:29Z   >>>>   -->
<iq to='wojtek@tigase.org' id='6667749B-19EA-4A2E-B134-AD0DF6155C42' type='get'>
<ping xmlns='urn:xmpp:ping'/>
</iq>

<!--   2024-06-29T15:53:29Z   >>>>   -->
<r xmlns='urn:xmpp:sm:3'/>

<!--   2024-06-29T15:56:24Z   >>>>   -->
<iq type='get' to='wojtek@tigase.org' id='5E651A79-403B-4C94-9F58-399B724376D3'>
<ping xmlns='urn:xmpp:ping'/>
</iq>

<!--   2024-06-29T15:56:24Z   >>>>   -->
<r xmlns='urn:xmpp:sm:3'/>

Captura de pantalla 2024-06-29 a las 17.59.41.png

wojciech.kapcia@tigase.net commented 3 months ago

Stacktrace:

Muestra de BeagleIM.txt

wojciech.kapcia@tigase.net commented 3 months ago

Disconnecting wifi resulted in majority of contacts getting offline but those from problematic accounts stayed "green". After reconnecting wifi two problematic accounts git gray dot in settings and main account stopped sending XMPP ping.

Andrzej Wójcik (Tigase) commented 3 months ago

I've adjusted TCP keepalive configuration (it was using default macOS values) and I've prepared a new build (now in DropBox) for testing this issue.

wojciech.kapcia@tigase.net commented 3 months ago

So far the connections stays open and if it's dropped it seems to be detected correctly and Beagle reconnects shortly afterwards.

wojciech.kapcia@tigase.net changed state to 'In Progress' 2 months ago

Previous Value	Current Value
Open	In Progress

wojciech.kapcia@tigase.net changed state to 'Closed' 2 months ago

Previous Value	Current Value
In Progress	Closed

wojciech.kapcia@tigase.net commented 2 months ago

I haven't noticed any problems with connections after a couple of days. I think that properly setting (again) TCP parameters solved the issue.

Type	Bug
Priority	Normal
Assignee	Andrzej Wójcik (Tigase) wojciech.kapcia@tigase.net
Version	none
Sprints	n/a
Customer	n/a

Issue Votes (0)

Watchers (3)

Reference

tigase/_clients/beagle-im#621