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.

Sign up for GitHub

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

Jump to bottom

Severe network outage tests #74

Open
daniele-athome opened this issue Jan 4, 2017 · 2 comments
Open

Severe network outage tests #74

daniele-athome opened this issue Jan 4, 2017 · 2 comments
Assignees
@daniele-athome
Labels
bug
Milestone
1.0

Comments

@daniele-athome
Copy link
Member

daniele-athome commented Jan 4, 2017 •
edited
Loading

Message delivery loss is still an issue with very faulty client connections. We need a way to test those scenarios.
Special cases to test are message delivery during reconnections, especially resource conflicts. Tigase seems to go crazy when it happens.

https://projects.tigase.org/issues/4262
https://projects.tigase.org/issues/4380
@daniele-athome daniele-athome added this to the 1.0-beta1 milestone Jan 4, 2017
@daniele-athome daniele-athome self-assigned this Jan 4, 2017
@daniele-athome daniele-athome mentioned this issue Jan 4, 2017
Closed
@daniele-athome
Copy link
Member Author

daniele-athome commented Nov 9, 2017 •
edited
Loading

Tools:

https://github.com/tylertreat/comcast (via iptables)
https://github.com/Shopify/toxiproxy (via proxy)

Low-level: https://wiki.linuxfoundation.org/networking/netem (used by comcast)

@daniele-athome
Copy link
Member Author

Aggressive delivery in kontalk/tigase-server@5ae20c5 seems to have fixed all message delivery issues.
However, delivery receipts delayed by CSI are sometimes lost. Opened #89.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daniele-athome daniele-athome

Labels
bug
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@daniele-athome