Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ghost messages #88

Open
daniele-athome opened this issue Feb 7, 2018 · 2 comments
Open

Ghost messages #88

daniele-athome opened this issue Feb 7, 2018 · 2 comments
Assignees
Labels
Milestone

Comments

@daniele-athome
Copy link
Member

daniele-athome commented Feb 7, 2018

This might be the whole cause of missing deliveries that is troubling Kontalk users (and even me).
I found messages being saved again and again (thus refreshing the expiration date) from January 2017 (!!!!) to existing and valid users. What is happening here??

@daniele-athome daniele-athome added this to the 1.0 milestone Feb 7, 2018
@daniele-athome daniele-athome self-assigned this Feb 7, 2018
@daniele-athome
Copy link
Member Author

daniele-athome commented Feb 7, 2018

Ghost messages appear to be saved with full JIDs having non-existing resources. The resource is the device ID, since it isn't connected, Tigase sends the message to offline storage again (and sends a copy to the bare JID, but that doesn't fix the issue itself).

Anyway the problem here is mainly waste of server resources. I need to find a way to properly store the timestamp to the initial value, and not to the time of each storage.

@daniele-athome
Copy link
Member Author

To a more close look at the database, there are messages with a bare JID in to and they are not delivered nonetheless. That is not valid behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant