15 Second Delay Connecting to XMPP Server in 4.2.0

Flow · January 9, 2017, 11:07am

AbstractXMPPConnection has a method called populateHostAddresses, which we tried to pass in Host Address from the config. However, that tried to create a HostAddress with an empty string as the fqdn, which resulted in a StringIndexOutOfBoundsException on line 48: if (fqdn.charAt(fqdn.length() - 1) == '.')
That is fixed in 4.2.0-rc2-SNAPSHOT. The MiniDNS version got also bumped in 4.2.0-rc1, so the overall behavior should have improved.

Resolved by removing reliance on MiniDNS. We have found DNSJavaResolver to be much quicker, and doesn’t produce resolution failures.

I don’t recommend using dnsjava on Android, for various reasons. For example dnsjava’s mechanism to detect the system’s DNS server are not ideal on Android. And that is me, who did - Improve the name server detection code for Android. · dnsjava/dnsjava@563aae1 · GitHub , saying it.

Nick32 · January 9, 2017, 11:26am

Can you say when rc2 will be available on maven?

Flow · January 9, 2017, 12:22pm

Can you say when rc2 will be available on maven?
The snapshots are already available in Maven Centrals snapshot repository.

Grigory_Fedorov · January 14, 2017, 9:28pm

We’re also very worried about long connection time (sometimes).

I’m not an expert in DNS client, but problem seems to be there (there was nothing similar on previous versions of MiniDnsClient).

I adjusted logging to catch Smack and MiniDns log on Android, hope it can help:

2017-01-14_16-12-28 <<< android network down >>>

2017-01-14_16-12-28 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ PacketWriter shutdown()

2017-01-14_16-12-28 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ Reporting shutdownDone success in writer thread

2017-01-14_16-12-28 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ PacketWriter has been shut down

2017-01-14_16-12-28 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ PacketReader shutdown()

2017-01-14_16-12-28 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ PacketReader has been shut down

2017-01-14_16-12-28 W/org.jivesoftware.smack.AbstractXMPPConnection: Connection XMPPTCPConnection[] (0) closed with error

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ javax.net.ssl.SSLException: Read error: ssl=0x68b588f8: I/O error during system call, Connection timed out

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ com.android.org.conscrypt.NativeCrypto.SSL_read(Native Method)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ com.android.org.conscrypt.OpenSSLSocketImpl$SSLInputStream.read(OpenSSLSocketIm pl.java:705)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ java.io.InputStreamReader.read(InputStreamReader.java:233)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ java.io.BufferedReader.read(BufferedReader.java:325)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ org.jivesoftware.smack.util.ObservableReader.read(ObservableReader.java:41)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ org.kxml2.io.KXmlParser.fillBuffer(KXmlParser.java:1515)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ org.kxml2.io.KXmlParser.peekType(KXmlParser.java:992)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ org.kxml2.io.KXmlParser.next(KXmlParser.java:349)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ org.kxml2.io.KXmlParser.next(KXmlParser.java:313)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPC onnection.java:1227)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPCon nection.java:980)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnecti on.java:995)

2017-01-14_16-12-28 E/org.jivesoftware.smack.AbstractXMPPConnection﹕ java.lang.Thread.run(Thread.java:818)

2017-01-14_16-12-28 W/org.jivesoftware.smackx.ping.PingManager: Exception while pinging server of XMPPTCPConnection[] (0)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.lang.InterruptedException

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInt erruptAfterWait(AbstractQueuedSynchronizer.java:1988)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNano s(AbstractQueuedSynchronizer.java:2063)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.util.concurrent.ArrayBlockingQueue.poll(ArrayBlockingQueue.java:372)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ org.jivesoftware.smack.StanzaCollector.nextResult(StanzaCollector.java:185)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:2 47)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ org.jivesoftware.smackx.ping.PingManager.ping(PingManager.java:170)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ org.jivesoftware.smackx.ping.PingManager.pingMyServer(PingManager.java:253)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ org.jivesoftware.smackx.ping.PingManager.pingMyServer(PingManager.java:234)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ org.jivesoftware.smackx.ping.PingManager.pingServerIfNecessary(PingManager.java :377)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ org.jivesoftware.smackx.ping.PingManager$4.run(PingManager.java:407)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.util.concurrent.FutureTask.run(FutureTask.java:237)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201 (ScheduledThreadPoolExecutor.java:154)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Schedu ledThreadPoolExecutor.java:269)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)

2017-01-14_16-12-28 E/org.jivesoftware.smackx.ping.PingManager﹕ java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)

2017-01-14_16-12-28

2017-01-14_16-12-28 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-12-28 D/de.measite.minidns.AbstractDNSClient﹕ IOException {0} on {1} while resolving {2}: {3}

2017-01-14_16-12-28 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-12-30 <<< android mobile network connected (HSPA) >>>

2017-01-14_16-12-31 <<< android wifi connected >>>

2017-01-14_16-12-33 D/de.measite.minidns.AbstractDNSClient﹕ IOException {0} on {1} while resolving {2}: {3}

2017-01-14_16-12-33 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-12-33 D/de.measite.minidns.AbstractDNSClient﹕ Response from {0} on {1} for {2}:

{3}

2017-01-14_16-12-33 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-12-43 D/de.measite.minidns.AbstractDNSClient﹕ IOException {0} on {1} while resolving {2}: {3}

2017-01-14_16-12-43 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-12-43 D/de.measite.minidns.AbstractDNSClient﹕ Response from {0} on {1} for {2}:

{3}

2017-01-14_16-12-43 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-12-53 D/de.measite.minidns.AbstractDNSClient﹕ IOException {0} on {1} while resolving {2}: {3}

2017-01-14_16-12-53 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-12-53 D/de.measite.minidns.AbstractDNSClient﹕ Response from {0} on {1} for {2}:

{3}

2017-01-14_16-12-53 D/org.jivesoftware.smack.util.DNSUtil﹕ Resolved SRV RR for _xmpp-client.: :5222 prio:10:w:5

2017-01-14_16-12-54 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-13-04 D/de.measite.minidns.AbstractDNSClient﹕ IOException {0} on {1} while resolving {2}: {3}

2017-01-14_16-13-04 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-13-04 D/de.measite.minidns.AbstractDNSClient﹕ Response from {0} on {1} for {2}:

{3}

2017-01-14_16-13-04 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-13-14 D/de.measite.minidns.AbstractDNSClient﹕ IOException {0} on {1} while resolving {2}: {3}

2017-01-14_16-13-14 D/de.measite.minidns.AbstractDNSClient﹕ Asking {0} on {1} for {2} with:

{3}

2017-01-14_16-13-14 D/de.measite.minidns.AbstractDNSClient﹕ Response from {0} on {1} for {2}:

{3}

2017-01-14_16-13-14 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ Trying to establish TCP connection to / at port 5222

2017-01-14_16-13-14 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ Established TCP connection to / at port 5222

Flow · January 14, 2017, 11:22pm

Thanks Grigory. Unfortunately your JUL handler does not format the log messages. That makes it hard to tell which DNS server does cause the exception. We also don’t see the exception message which would be very helpful. In order to format the log messages, try something like JUL: Format the log message · ProjectMAXS/maxs@d48b072 · GitHub , i.e. use Formatter.formatMessage(LogRecord).

When it’s formated, we should not only see the used DNS servers but also the message of the IOException. It would be great if you could show us a formatted log when you have one.

I do believe that the culprit is in your and OP’s case a lame or faulty DNS server, like “::1” without having a DNS resolver listening on the IPv6 localhost.

Grigory_Fedorov · January 16, 2017, 9:59am

Thanks for help, Flow!

I use log formatting now, here is a sample. But in this particular case it seems that android hanged network for two minutes (Android 6)… But the application is in battery white list. I will add logs with other cases as soon as I get them.

2017-01-16_14-32-39 <<< Android LTE connected >>>

2017-01-16_14-32-40 <<< Starting connection… >>>

2017-01-16_14-32-40 D/de.measite.minidns.AbstractDNSClient﹕ Asking /10.10.30.118 on 53 for _xmpp-client._tcp.redsolution.com. IN SRV with:

DNSMessage(24664 QUERY NO_ERROR query[qr=0] rd)

[Q: _xmpp-client._tcp.redsolution.com. IN SRV]

[X: EDNS: version: 0, flags:; udp: 1024]

2017-01-16_14-32-40 D/de.measite.minidns.AbstractDNSClient﹕ Response from /10.10.30.118 on 53 for _xmpp-client._tcp.redsolution.com. IN SRV:

DNSMessage(24664 QUERY NO_ERROR resp[qr=1] rd ra)

[Q: _xmpp-client._tcp.redsolution.com. IN SRV]

[A: _xmpp-client._tcp.redsolution.com. 24466 IN SRV 10 5 5222 raven.redsolution.ru.]

[N: redsolution.com. 24466 IN NS ns5.linode.com.]

[N: redsolution.com. 24466 IN NS ns4.linode.com.]

[N: redsolution.com. 24466 IN NS ns1.linode.com.]

[N: redsolution.com. 24466 IN NS ns2.linode.com.]

[N: redsolution.com. 24466 IN NS ns3.linode.com.]

[X: raven.redsolution.ru. 25195 IN A 188.226.175.57]

[X: ns1.linode.com. 9997 IN A 162.159.27.72]

[X: ns1.linode.com. 57170 IN AAAA 2400:cb00:2049:1:0:0:a29f:1a63]

[X: ns2.linode.com. 106294 IN A 162.159.24.39]

[X: ns2.linode.com. 106294 IN AAAA 2400:cb00:2049:1:0:0:a29f:1827]

[X: ns3.linode.com. 106294 IN A 162.159.25.129]

[X: ns3.linode.com. 106294 IN AAAA 2400:cb00:2049:1:0:0:a29f:1981]

[X: ns4.linode.com. 137673 IN A 162.159.26.99]

[X: ns4.linode.com. 137673 IN AAAA 2400:cb00:2049:1:0:0:a29f:1b48]

[X: ns5.linode.com. 144650 IN A 162.159.24.25]

[X: ns5.linode.com. 144650 IN AAAA 2400:cb00:2049:1:0:0:a29f:1819]

[X: EDNS: version: 0, flags:; udp: 4096]

2017-01-16_14-32-40 D/de.measite.minidns.AbstractDNSClient﹕ Asking /10.10.30.118 on 53 for raven.redsolution.ru. IN A with:

DNSMessage(48154 QUERY NO_ERROR query[qr=0] rd)

[Q: raven.redsolution.ru. IN A]

[X: EDNS: version: 0, flags:; udp: 1024]

2017-01-16_14-32-40 D/de.measite.minidns.AbstractDNSClient﹕ Response from /10.10.30.118 on 53 for raven.redsolution.ru. IN A:

DNSMessage(48154 QUERY NO_ERROR resp[qr=1] rd ra)

[Q: raven.redsolution.ru. IN A]

[A: raven.redsolution.ru. 25195 IN A 188.226.175.57]

[N: redsolution.ru. 40869 IN NS ns2.linode.com.]

[N: redsolution.ru. 40869 IN NS ns3.linode.com.]

[N: redsolution.ru. 40869 IN NS ns5.linode.com.]

[N: redsolution.ru. 40869 IN NS ns4.linode.com.]

[N: redsolution.ru. 40869 IN NS ns1.linode.com.]

[X: ns1.linode.com. 9997 IN A 162.159.27.72]

[X: ns1.linode.com. 57170 IN AAAA 2400:cb00:2049:1:0:0:a29f:1a63]

[X: ns2.linode.com. 106294 IN A 162.159.24.39]

[X: ns2.linode.com. 106294 IN AAAA 2400:cb00:2049:1:0:0:a29f:1827]

[X: ns3.linode.com. 106294 IN A 162.159.25.129]

[X: ns3.linode.com. 106294 IN AAAA 2400:cb00:2049:1:0:0:a29f:1981]

[X: ns4.linode.com. 137673 IN A 162.159.26.99]

[X: ns4.linode.com. 137673 IN AAAA 2400:cb00:2049:1:0:0:a29f:1b48]

[X: ns5.linode.com. 144650 IN A 162.159.24.25]

[X: ns5.linode.com. 144650 IN AAAA 2400:cb00:2049:1:0:0:a29f:1819]

[X: EDNS: version: 0, flags:; udp: 4096]

2017-01-16_14-32-40 D/de.measite.minidns.AbstractDNSClient﹕ Asking /10.10.30.118 on 53 for raven.redsolution.ru. IN AAAA with:

DNSMessage(5738 QUERY NO_ERROR query[qr=0] rd)

[Q: raven.redsolution.ru. IN AAAA]

[X: EDNS: version: 0, flags:; udp: 1024]

2017-01-16_14-32-40 D/de.measite.minidns.AbstractDNSClient﹕ Response from /10.10.30.118 on 53 for raven.redsolution.ru. IN AAAA:

DNSMessage(5738 QUERY NO_ERROR resp[qr=1] rd ra)

[Q: raven.redsolution.ru. IN AAAA]

[N: redsolution.ru. 6000 IN SOA ns1.linode.com. webmaster.redsolution.ru. 2017011212 14400 14400 1209600 86400]

[X: EDNS: version: 0, flags:; udp: 4096]

2017-01-16_14-32-40 D/org.jivesoftware.smack.util.DNSUtil﹕ Resolved SRV RR for _xmpp-client._tcp.redsolution.com: raven.redsolution.ru:5222 prio:10:w:5

2017-01-16_14-32-40 D/de.measite.minidns.AbstractDNSClient﹕ Asking /10.10.30.118 on 53 for redsolution.com. IN A with:

DNSMessage(24218 QUERY NO_ERROR query[qr=0] rd)

[Q: redsolution.com. IN A]

[X: EDNS: version: 0, flags:; udp: 1024]

2017-01-16_14-32-40 D/de.measite.minidns.AbstractDNSClient﹕ Response from /10.10.30.118 on 53 for redsolution.com. IN A:

DNSMessage(24218 QUERY NO_ERROR resp[qr=1] rd ra)

[Q: redsolution.com. IN A]

[A: redsolution.com. 25804 IN A 178.79.128.253]

[N: redsolution.com. 24465 IN NS ns4.linode.com.]

[N: redsolution.com. 24465 IN NS ns2.linode.com.]

[N: redsolution.com. 24465 IN NS ns5.linode.com.]

[N: redsolution.com. 24465 IN NS ns1.linode.com.]

[N: redsolution.com. 24465 IN NS ns3.linode.com.]

[X: ns1.linode.com. 9996 IN A 162.159.27.72]

[X: ns1.linode.com. 57169 IN AAAA 2400:cb00:2049:1:0:0:a29f:1a63]

[X: ns2.linode.com. 106293 IN A 162.159.24.39]

[X: ns2.linode.com. 106293 IN AAAA 2400:cb00:2049:1:0:0:a29f:1827]

[X: ns3.linode.com. 106293 IN A 162.159.25.129]

[X: ns3.linode.com. 106293 IN AAAA 2400:cb00:2049:1:0:0:a29f:1981]

[X: ns4.linode.com. 137672 IN A 162.159.26.99]

[X: ns4.linode.com. 137672 IN AAAA 2400:cb00:2049:1:0:0:a29f:1b48]

[X: ns5.linode.com. 144649 IN A 162.159.24.25]

[X: ns5.linode.com. 144649 IN AAAA 2400:cb00:2049:1:0:0:a29f:1819]

[X: EDNS: version: 0, flags:; udp: 4096]

2017-01-16_14-32-40 D/de.measite.minidns.AbstractDNSClient﹕ Asking /10.10.30.118 on 53 for redsolution.com. IN AAAA with:

DNSMessage(12865 QUERY NO_ERROR query[qr=0] rd)

[Q: redsolution.com. IN AAAA]

[X: EDNS: version: 0, flags:; udp: 1024]

2017-01-16_14-32-44 <<< Android WiFI connected >>>

2017-01-16_14-34-52 <<< Android Screen is on >>>

2017-01-16_14-34-56 D/de.measite.minidns.AbstractDNSClient﹕ IOException /10.10.30.118 on 53 while resolving redsolution.com. IN AAAA: de.measite.minidns.util.MultipleIoException: null, failed to connect to /10.10.30.118 (port 53) after 5000ms: isConnected failed: ENETUNREACH (Network is unreachable)

2017-01-16_14-34-56 D/de.measite.minidns.AbstractDNSClient﹕ Asking /10.10.30.122 on 53 for redsolution.com. IN AAAA with:

DNSMessage(12865 QUERY NO_ERROR query[qr=0] rd)

[Q: redsolution.com. IN AAAA]

[X: EDNS: version: 0, flags:; udp: 1024]

2017-01-16_14-35-01 D/de.measite.minidns.AbstractDNSClient﹕ IOException /10.10.30.122 on 53 while resolving redsolution.com. IN AAAA: de.measite.minidns.util.MultipleIoException: null, failed to connect to /10.10.30.122 (port 53) after 5000ms: isConnected failed: ENETUNREACH (Network is unreachable)

2017-01-16_14-35-01 D/de.measite.minidns.AbstractDNSClient﹕ Asking /8.8.8.8 on 53 for redsolution.com. IN AAAA with:

DNSMessage(12865 QUERY NO_ERROR query[qr=0] rd)

[Q: redsolution.com. IN AAAA]

[X: EDNS: version: 0, flags:; udp: 1024]

2017-01-16_14-35-02 D/de.measite.minidns.AbstractDNSClient﹕ Response from /8.8.8.8 on 53 for redsolution.com. IN AAAA:

DNSMessage(12865 QUERY NO_ERROR resp[qr=1] rd ra)

[Q: redsolution.com. IN AAAA]

[N: redsolution.com. 1799 IN SOA ns1.linode.com. webmaster.redsolution.ru. 2016122205 14400 14400 1209600 86400]

[X: EDNS: version: 0, flags:; udp: 512]

2017-01-16_14-35-02 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ Trying to establish TCP connection to /188.226.175.57 at port 5222

2017-01-16_14-35-02 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ Established TCP connection to /188.226.175.57 at port 5222

Grigory_Fedorov · January 16, 2017, 10:37am

And here are better examples. Both using Android 7.1, LTE, Screen is on. Connection to XMPP server creep.im took long time:

Smack 4.2.0-rc2 long time reconnection on Android · GitHub

Flow · January 16, 2017, 12:08pm

What we see is that MiniDNS tries to use the IPv6 localhost for resolution, which does not answer after the default 5 second timeout, and then another IP is used. This is similar to @Nick.

The question now is: Where does that faulty entry come from? The most promising candidates are MiniDNS’s AndroidUsingExec and AndroidUsingReflection DNSServerLookupMechanims. Could you set a break point in their getDnsServerAddresses() and see if the returned string array contains “::1”?

Grigory_Fedorov · January 16, 2017, 1:58pm

I found out that AndroidUsingExec returns [::1, 83.149.33.203, 83.149.33.196].

It get ::1 from “[net.r_rmnet_data0.dns1]: []” and “[net.r_rmnet_data0.dns2]: []”

Flow · January 16, 2017, 6:15pm

So you are saying the ‘value’ in AndroidUsingExec is the empty String? And that InetAddress.getByName(value); returns the localhost if it’s called with the empty string? In that case we can fix AndroidUsingExec by filtering the empty string (in value).

Grigory_Fedorov · January 16, 2017, 6:34pm

Yes, I also think that filtering empty string can help.

Flow · January 16, 2017, 8:14pm

I’ve uploaded Filter out empty values in AndroidUsingExec · Flowdalic/minidns@f46491a · GitHub to my github repo. Can you copy the improved version of AndroidUsingExec into your codebase, then install that version using DNSClient.addDnsServerLookupMechanism(), removing the old one using removeDNSServerLookupMechanism() and report back if it fixes the issue?

Adekunle_Valentine_O · January 16, 2017, 9:31pm

I am also having the exact issue… still persistent in 4.2.0 r2

Flow · January 16, 2017, 9:56pm

Then try what I wrote here: https://community.igniterealtime.org/message/262585#comment-262585

Grigory_Fedorov · January 17, 2017, 7:08am

Thanks! Works perfectly now! Will continue testing.

Adekunle_Valentine_O · January 17, 2017, 11:11am

How Exactly do I go about doing this again? I can’t seem to find the directory since I’m pulling using mavern. I will try to look harder
Also Can you hopefully add it to the next build as (as a quick fix ) if you don’t mind?

EDIT: I just grabbed 4.2.0-rc3-SNAPSHOT , but changes isn’t reflected

Grigory_Fedorov · January 17, 2017, 12:09pm

You should copy modified AndroidUsingExec class from minidns/AndroidUsingExec.java at f46491a029b270b9f56101882ee400c6d0afc7ea · Flowdalic/minidns · GitHub to your project and call following lines before connecting:

DNSClient.removeDNSServerLookupMechanism(de.measite.minidns.dnsserverlookup.AndroidUsingExec.INSTANCE); DNSClient.addDnsServerLookupMechanism(AndroidUsingExec.INSTANCE);

Luca5 · January 26, 2017, 7:43am

Will we still need to use the modified AndroidUsingExec once 4.2.0-rc3 is released?

Flow · January 26, 2017, 11:31am

This is unrelated to the Smack release: The issue is within MiniDNS. We will release MiniDNS 0.2.1 in the coming weeks, which will fix the issue. And since Smack uses a ranged version in the declaration of the MiniDNS dependency, and Smack 4.2 release candidate will eventually pick up the fix.

P_Afzal_Khan · April 6, 2017, 11:02am

I am still having the exact issue… still persistent in 4.2.0, pulling using mavern for android. Is this issue fixed in smack 4.2.0 release.