powered by Jive Software

Timeouts and errors on login after upgrading to smack 4.4.4

Smack Smack Support
#1

Hi,
I upgraded to smack 4.4.4.
After the upgrade, I’m experiencing a number of warnings and timeouts at the point of login.
Below is the stack trace;

2022-01-09 11:37:59.423 23259-23324/ W/DataFormProvider: The Field 'os' from FORM_TYPE 'urn:xmpp:dataforms:softwareinfo' is not registered. Field type is unknown, assuming text-single.
2022-01-09 11:37:59.423 23259-23324/ W/DataFormProvider: The Field 'os_version' from FORM_TYPE 'urn:xmpp:dataforms:softwareinfo' is not registered. Field type is unknown, assuming text-single.
2022-01-09 11:37:59.423 23259-23324/ W/DataFormProvider: The Field 'software' from FORM_TYPE 'urn:xmpp:dataforms:softwareinfo' is not registered. Field type is unknown, assuming text-single.
2022-01-09 11:37:59.423 23259-23324/ W/DataFormProvider: The Field 'software_version' from FORM_TYPE 'urn:xmpp:dataforms:softwareinfo' is not registered. Field type is unknown, assuming text-single.
2022-01-09 11:37:59.423 23259-23324/ W/DataFormProvider: The Field 'admin-addresses' from FORM_TYPE 'http://jabber.org/network/serverinfo' is not registered. Field type is unknown, assuming text-single.
2022-01-09 11:37:59.424 23259-23324/ W/hrowingCallbackWithHint: Parsing exception encountered. This exception will be re-thrown, leading to a disconnect. You can change this behavior by setting a different ParsingExceptionCallback using setParsingExceptionCallback(). More information an be found in AbstractXMPPConnection's javadoc.
2022-01-09 11:38:18.595 23259-23323/ D/SMACK: SENT (0): 
    <iq to='server' id='994CJ-2' type='get'>
      <query xmlns='http://jabber.org/protocol/disco#info'>
      </query>
    </iq>
2022-01-09 11:38:29.610 23259-23323/ D/SMACK: SENT (0): 
    <iq to='server' id='994CJ-3' type='get'>
      <ping xmlns='urn:xmpp:ping'/>
    </iq>
2022-01-09 11:38:38.610 23259-23302/ W/HttpFileUploadManager: Error during discovering HTTP File Upload service
    org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 20000ms (~20s). StanzaCollector has been cancelled. Waited for response using: IQReplyFilter: iqAndIdFilter (AndFilter: (OrFilter: (IQTypeFilter: type=error, IQTypeFilter: type=result), StanzaIdFilter: id=994CJ-2)), : fromFilter (OrFilter: (FromMatchesFilter (full): testzimbavm)).
        at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:281)
        at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:228)
        at org.jivesoftware.smackx.disco.ServiceDiscoveryManager.discoverInfo(ServiceDiscoveryManager.java:606)
        at org.jivesoftware.smackx.disco.ServiceDiscoveryManager.discoverInfo(ServiceDiscoveryManager.java:578)
        at org.jivesoftware.smackx.disco.ServiceDiscoveryManager.findServicesDiscoverInfo(ServiceDiscoveryManager.java:813)
        at org.jivesoftware.smackx.disco.ServiceDiscoveryManager.findServicesDiscoverInfo(ServiceDiscoveryManager.java:781)
        at org.jivesoftware.smackx.disco.ServiceDiscoveryManager.findServicesDiscoverInfo(ServiceDiscoveryManager.java:761)
        at org.jivesoftware.smackx.httpfileupload.HttpFileUploadManager.discoverUploadService(HttpFileUploadManager.java:193)
        at org.jivesoftware.smackx.httpfileupload.HttpFileUploadManager$2.authenticated(HttpFileUploadManager.java:130)
        at org.jivesoftware.smack.AbstractXMPPConnection.callConnectionAuthenticatedListener(AbstractXMPPConnection.java:1710)
        at org.jivesoftware.smack.AbstractXMPPConnection.afterSuccessfulLogin(AbstractXMPPConnection.java:795)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection.afterSuccessfulLogin(XMPPTCPConnection.java:371)
        at org.jivesoftware.smack.tcp.XMPPTCPConnection.loginInternal(XMPPTCPConnection.java:469)
        at org.jivesoftware.smack.AbstractXMPPConnection.login(AbstractXMPPConnection.java:641)
        at org.jivesoftware.smack.AbstractXMPPConnection.login(AbstractXMPPConnection.java:615)
#2

That is fixed with

which will be includes in the upcoming Smack 4.4.5 release.

The actual exception, that should probably terminate the connection, is missing here. Hence I can’t comment further on it.

That is a remote enitty not responding to a disc#info request. Something the remote entity is expected to do and should be looked into. But nothing fatal.

#3

Thanks @Flow for the timely response, I’ll surely upgrade to Smack 4.4.5 once it’s out.

Regarding the actual exception that terminates the connection, It doesn’t get registered in the stack trace. Let me reverify if this is the case.

So for the timeout it’s a problem on Openfire 4.5.3, here I would rule out server resources, and too much traffic.
I hope it’s looked into in the next versions

#4

This is Smack reporting that a remote entity does not respond to its requests. Unless the initial request by Smack is in error, which I don’t think is the case, there is nothing that Smack can do to fix it.