Projects tigase _server server-core Issues #496
S2S Reset Bad State Connections (#496)
Eric Dziewa opened 10 years ago
Due Date
2015-09-29

Does not work.

Daniel Wisnewski commented 9 years ago

Lists current connections, never changes after reset is made.

Andrzej Wójcik (Tigase) commented 9 years ago

This is correct behavior of adhoc command as it closes only S2S connections in bad state and then lists remaining connections.

So if all connections are not in bad state then, this will only list all S2S connections

Daniel Wisnewski commented 9 years ago

I don't have an adequate way to test this, Eric, do we have a clustered server we can test this with? Sever a connection and see it if shows?

Eric Dziewa commented 9 years ago

I can't seem to find a command labeled "S2S Reset Bad State Connections". Has it been removed? I can stop a node and see it removed from "Get list of all connected cluster nodes" .

You can log in as tigase@c01.xmpp-test.net through tigase@c04.xmpp-test.net. The domain is cluster-c.xmpp-test.net. Please don't log in between 8pm through 12am because cluster tests run at this time. Please don't upgrade because the nodes upgrade automatically every day.

Eric Dziewa commented 9 years ago

That was 8pm through 12am EST.

Daniel Wisnewski commented 9 years ago

I am unable to create a bad S2S connection, the server seems to cut those connections before I can see anything on this screen. I am assuming everything works okay and will change this issue to resolved. %andrzej.wojcik if you have any suggestions to force these connections to go bad (and stay bad) please let me know, if you do not, please close the issue.

Andrzej Wójcik (Tigase) commented 9 years ago

I'm closing this task as I have no idea how we can get bad S2S connection.

issue 1 of 1
Type
Bug
Priority
Normal
Assignee
RedmineID
3112
Version
tigase-server-7.1.0
Spent time
28h 30m
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#496
Please wait...
Page is in error, reload to recover