hantu85
commented
4 years ago 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:
SocketConnector sending stanza: <stream:stream to='domain.tld' from='ij@domain.tld' version='1.0' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'>
WriteBuffer sent 138 bytes 138 of 138
SocketConnector stream event: HasSpaceAvailable
SocketConnector stream event: HasBytesAvailable
SocketConnector stream event: EndEncountered
connection state changed: connectedwhich 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.
ghost
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.