Spark shows offline roster after reconnecting

Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.6.0
  • Fix Version/s: 2.6.0 RC2
  • Component/s: General
  • Labels:
    None

Description

If Spark looses connection (e.g. logged of by another user with the same jid/resource) and then reconnects, then it shows all users offline. So one have to relogin to get correct roster.

Issue Links

is related to

Sub-task - The sub-task of the issue SPARK-764 Auto-reconnect does not send available presence or ask for roster

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
wroot added a comment -

Reproduce scenario (11985):

1) Login with user "user1" in some client, can be Spark, and stay online with it
1) Login with user "user2@server/Spark" in Spark, it can see user1 online
2) Login with user "user2@server/Spark" in another client
3) Spark is being disconnected due to resource conflict and stays offline showing Reconnect button
4) Press Reconnect button in Spark, it will login with user2 again
5) user1 can see user2 online, but user2 in Spark can't see user1 online (and probably can't see anybody online)

Show
wroot added a comment - Reproduce scenario (11985): 1) Login with user "user1" in some client, can be Spark, and stay online with it 1) Login with user "user2@server/Spark" in Spark, it can see user1 online 2) Login with user "user2@server/Spark" in another client 3) Spark is being disconnected due to resource conflict and stays offline showing Reconnect button 4) Press Reconnect button in Spark, it will login with user2 again 5) user1 can see user2 online, but user2 in Spark can't see user1 online (and probably can't see anybody online)
Hide
Permalink
wroot added a comment -

It does seem to work fine with reconnection caused by connection loss. But doesnt work when reconnection is manual due to being previously kicked because of resource conflict.

Show
wroot added a comment - It does seem to work fine with reconnection caused by connection loss. But doesnt work when reconnection is manual due to being previously kicked because of resource conflict.
Hide
Permalink
wroot added a comment -

There are additional reports from users, who sees not complete roster after reconnection after network switching http://community.igniterealtime.org/message/207689#207689

Show
wroot added a comment - There are additional reports from users, who sees not complete roster after reconnection after network switching http://community.igniterealtime.org/message/207689#207689
Hide
Permalink
Walter Ebeling added a comment -

Please review the open issues and familiarize yourself with the code.

Show
Walter Ebeling added a comment - Please review the open issues and familiarize yourself with the code.
Hide
Permalink
Holger Bergunde added a comment - - edited

couldn't reproduce especially this error using build 2.6.0 RC1

only recognized that spark did't load the roster properly after a reconnection (caused of connection abort)

Show
Holger Bergunde added a comment - - edited couldn't reproduce especially this error using build 2.6.0 RC1 only recognized that spark did't load the roster properly after a reconnection (caused of connection abort)
Hide
Permalink
Nihad Perva added a comment -

it is the same thing that happens when you resume from standby (other open issue)

Show
Nihad Perva added a comment - it is the same thing that happens when you resume from standby (other open issue)
Hide
Permalink
Nihad Perva added a comment -

it's fixed for me with the latest release

Show
Nihad Perva added a comment - it's fixed for me with the latest release

People

  • Assignee:
    Holger Bergunde
    Reporter:
    wroot
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: