|
If you were logged in you would be able to see more operations.
|
|
|
Smack
Created: 06/09/06 03:50 PM
Updated: 06/17/06 06:57 PM
|
|
| Component/s: |
Core
|
| Affects Version/s: |
2.0.0,
2.1.0,
2.2.0
|
| Fix Version/s: |
2.2.1
|
|
| Support Plan Customer Issue: |
No
|
| Resolution Date: |
06/12/06 11:38 AM
|
| Acceptance Test - Add?: |
No
|
|
A period exception has been occuring where TLS would mysteriously fail. Syncornization between the main thread and the PacketReader was originally thought to be the culprit but thanks to Skip Dooley's dedication to the problem it was found to be an issue with the Keep Alive thread spinning up before TLS could successfully complete.
|
|
Description
|
A period exception has been occuring where TLS would mysteriously fail. Syncornization between the main thread and the PacketReader was originally thought to be the culprit but thanks to Skip Dooley's dedication to the problem it was found to be an issue with the Keep Alive thread spinning up before TLS could successfully complete. |
Show » |
|
Bug
Closed
Critical
Timing of the Keep Alive Thread Could Break TLS
1) Start keep alive thread after TLS (if available) was negotiated or if server is not xmpp 1.0 compliant then after stream header was received
2) Keep alive thread will initially wait for 15 seconds before starting to work
3) Keep alive thread will send a hearbeat every 30 seconds (by default) since the last packet was sent to the server. In other words, connections that are sending stanzas all the time will no need to send heartbeats to keep the connection alive.