Reconnection after receiving <stream:error/> fails (#158)

Activities

Andrzej Wójcik (Tigase) opened 2 weeks ago

Reconnection after receiving <stream:error/> fails leaving connector in incorrect state making it impossible to stop or reconnect.

Andrzej Wójcik (Tigase) changed state to 'In Progress' 2 weeks ago

Previous Value	Current Value
Open	In Progress

Referenced from commit 2 weeks ago

Fixed deadlocks and issues with reconnection after <stream:error/> #158

Andrzej Wójcik (Tigase) committed 2 weeks ago

958ee643

Andrzej Wójcik (Tigase) commented 2 weeks ago

I've found an issue which resulted in responding on </stream:stream> received after stream <stream:error/> on a newly opened connection (after reconnection) instead of ignoring it if TCP connection was already closed or replaced.

Additionally, I've found a case in which <stream:error/> not fully reset connector state (ie. left TLS/ZLIB features enabled even after reconnection was triggered).

Andrzej Wójcik (Tigase) added "Related" tigase/_clients/beagle-im#639 2 weeks ago

Referenced from commit 2 weeks ago

Fixed reference cycle and locking issues #158

Andrzej Wójcik (Tigase) committed 2 weeks ago

496b25ba

Andrzej Wójcik (Tigase) changed state to 'In QA' 2 weeks ago

Previous Value	Current Value
In Progress	In QA

Referenced from commit 1 week ago

Andrzej Wójcik (Tigase) committed 1 week ago

b4810fda

Type	Bug
Priority	Normal
Assignee	Andrzej Wójcik (Tigase)
Version	none
Sprints	n/a
Customer	n/a

tigase/_clients/beagle-im#639 In QA

Update source code to use development branch of Martin

Issue Votes (0)

Watchers (3)

Reference

tigase/_libraries/Martin#158