-
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).
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Version |
none
|
Sprints |
n/a
|
Customer |
n/a
|
Issue Votes (0)
Reconnection after receiving
<stream:error/>
fails leaving connector in incorrect state making it impossible to stop or reconnect.