BeagleIM just trying lowest DNS SRV entry #40
Comments
|
BeagleIM jumps to the next DNS entry if it is not able to connect to the remote server. In your logs you have following entries: which means that remote server was available and accepted TCP connection and due to that BeagleIM decided that connection to that endpoint is valid. Subsequent disconnection was assumed as an issue on the server - ie. some timeout, so BeagleIM backed of and retried with DNS entries assuming that all entries are still valid (as TCP connection to the server was possible). Due to that I do not think that is an error in BeagleIM. It is a valid mechanism jumping to the next entry if TCP connection would not be possible. |
|
Don't think so... I can of course revert the DNS change of priority and retry... But I had it running like 5 mins without success before I did the DNS change. And only after that change, Beagle was able to connect. |
|
But BeagleIM was still able to connect to the TCP port, even with your initial configuration so it was not retrying any other connection option. BeagleIM even was sending stream initiation over TCP connection and then it was closed (by the remote server?). |
|
It still didn't work. I was not online... I can do a screencast to show it... :) |
|
Either way, connection was accepted, so why the client should try any other connection options? It is the same as if we would try to establish a connection and server would decide to stop it. Then it should just retry and not try another host. |
|
Nope, negative... there was no connection at all... I can provide you a video where you can see the timing of the events (just message me in the Tigase MUC)... the log hangs for quite a long time at this point: Then, the next lines are this: And as you can see from this screenshot of the company firewall, the access to port 5222 has been denied: So, definitely there is no established connection to port 5222 in this case and I think the message |
|
Actually "connected" is written only if TCP connection was established - (if TCP socket connection was established). Looking at the screen from your firewall I'm convinced that the connection was established. There is an |
Hi!
For me it seems as if BeagleIM just tries to connect to the first DNS SRV entry for _xmpp-client._tcp.domain.tld, that is: the one with the lowest priority, and not trying other entries, although they are listed in the result set of DNS query.
Below you can see the console output after starting BeagleIM 4.0b97. You can see the resolver result includes the entry for port 443 with priority 15 first. While Beagle was running, I changed DNS zone to have port 443 priority of 1. After that change was done Beagle was able to connect successfully.
I believe this is an error and Beagle should try other DNS entry than just the first one with lowest priority. Basically I want to have port 443 as a fallback port in case some restrictive firewalls are blocking standard XMPP ports 5222 and 5223.
The text was updated successfully, but these errors were encountered: