Bug #425

Broken TLS on large roster?

Added by Florian Jensen over 4 years ago. Updated almost 4 years ago.

Status:ClosedStart date:2012-01-25
Priority:NormalDue date:
Assignee:Andrzej Wójcik% Done:

100%

Category:-
Target version:tigase-server-5.1.0
Database:n/a Source Code Disclaimer:
Applicable version:

Description

When trying to log in into my account with Psi 0.14 during "peak" time (when my roster has the most online presences), I get a broken TLS error while it's downloading the roster.
The Tigase server seems to continue streaming the roster even after client TLS error.

Case 2: The N9/N900 have been a lot more sensitive to this issue and failing to log in a lot.

Note: Account details of my account on request.

History

#1 Updated by Artur Hefczyc over 4 years ago

  • Assignee set to Andrzej Wójcik
  • Target version set to tigase-server-5.1.0

#2 Updated by Artur Hefczyc over 4 years ago

This happens on the tigase.im installation. It may happen on tigase.org for mobile client too. Hard to replicate, I suspect some problems with byteBuffers handling for TLS layer.

#3 Updated by Andrzej Wójcik about 4 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Issue already resolved

#4 Updated by Artur Hefczyc almost 4 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF