Spark Connection Error

Two users successfully connected to Openfire and working in Spark. Other users are having difficulty and receiving the following error in error logs.

It appears that spark is having trouble resolving DNS from what I can tell about the error; however, DNS resolves correctly for all users. I have ran pings, and nslookup’s to verify.

Any assistance would be greatly appreciated.

Thanks,

Mar 16, 2017 12:38:18 PM org.jivesoftware.smack.util.DNSUtil resolveDomain
WARNING: Exception while resovling SRV records for im.craighomecare.com. Consider adding ‘_xmpp-(server|client)._tcp’ DNS SRV Records
javax.naming.NameNotFoundException: DNS name not found [response code 3]; remaining name '_xmpp-client._tcp.im.craighomecare.com’
at com.sun.jndi.dns.DnsClient.checkResponseCode(Unknown Source)
at com.sun.jndi.dns.DnsClient.isMatchResponse(Unknown Source)
at com.sun.jndi.dns.DnsClient.doUdpQuery(Unknown Source)
at com.sun.jndi.dns.DnsClient.query(Unknown Source)
at com.sun.jndi.dns.Resolver.query(Unknown Source)
at com.sun.jndi.dns.DnsContext.c_getAttributes(Unknown Source)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes(Unknown Source)
at javax.naming.directory.InitialDirContext.getAttributes(Unknown Source)
at org.jivesoftware.smack.util.dns.javax.JavaxResolver.lookupSRVRecords(JavaxResol ver.java:78)
at org.jivesoftware.smack.util.DNSUtil.resolveDomain(DNSUtil.java:171)
at org.jivesoftware.smack.util.DNSUtil.resolveXMPPDomain(DNSUtil.java:120)
at org.jivesoftware.smack.AbstractXMPPConnection.populateHostAddresses(AbstractXMP PConnection.java:574)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPC onnection.java:564)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection. java:850)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.ja va:364)
at org.jivesoftware.LoginDialog$LoginPanel.login(LoginDialog.java:1107)
at org.jivesoftware.LoginDialog$LoginPanel.access$900(LoginDialog.java:335)
at org.jivesoftware.LoginDialog$LoginPanel$3.construct(LoginDialog.java:894)
at org.jivesoftware.spark.util.SwingWorker.lambda$new$1(SwingWorker.java:138)
at java.lang.Thread.run(Unknown Source)

Mar 16, 2017 12:38:18 PM org.jivesoftware.spark.util.log.Log warning
WARNING: Exception in Login:
org.jivesoftware.smack.SmackException$ConnectionException: The following addresses failed: ‘_xmpp-client._tcp.im.craighomecare.com:5222’ failed because javax.naming.NameNotFoundException: DNS name not found [response code 3]; remaining name ‘_xmpp-client._tcp.im.craighomecare.com’, ‘im.craighomecare.com:5222’ failed because java.net.SocketException: Permission denied: connect
at org.jivesoftware.smack.SmackException$ConnectionException.from(SmackException.j ava:255)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPC onnection.java:612)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection. java:850)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.ja va:364)
at org.jivesoftware.LoginDialog$LoginPanel.login(LoginDialog.java:1107)
at org.jivesoftware.LoginDialog$LoginPanel.access$900(LoginDialog.java:335)
at org.jivesoftware.LoginDialog$LoginPanel$3.construct(LoginDialog.java:894)
at org.jivesoftware.spark.util.SwingWorker.lambda$new$1(SwingWorker.java:138)
at java.lang.Thread.run(Unknown Source)

Is your xmpp domain (as it shows on the Admin Console) craighomecare.com or im.craighomecare.com? What is your server’s FQDN? What do you put into Spark’s Domain field on the login screen?

I ran into a problem like this once . turned out the user had multiple network connections (ethernet and wifi) connected at the same time. ethernet was connected to the lan, while the wifi had connected to our guest network. windows had the wifi as preferred interface. reordering the interfaces resolved the issue for me.

1 Like