Not getting contacts presence at startup
I am starting to test some mobile xmpp clients and desktop clients together, and it seems presence is not being retrieved at startup. When I connect with Pidgin, user contacts are loaded, but they all remain offline until I send a presence change from the mobile client. I have read about presence probe at startup, and set all contacts to BOTH_SUBSCRIPTION, but it still doesn't work. All roster contacts are being loaded through a custom DynamicRosterIfc implementation. My server initialization is the following:
config-type=--gen-config-def --virt-hosts=my-notebook --vhost-tls-required = true --domain-filter-policy=ALL --debug=server,xmpp.impl,muc --user-db=pgsql --user-db-uri=jdbc:postgresql://localhost/tigasedb?user=*****&password=*****&useUnicode=true&characterEncoding=UTF-8&autoCreateUser=true --vhost-anonymous-enabled=false --sm-plugins =+msgoffline,+my-vcard,-vcard-temp sess-man/plugins-conf/urn\:ietf\:params\:xml\:ns\:xmpp-sasl/factory=com.my.tigase.auth.OAuthSaslServerFactory sess-man/plugins-conf/urn\:ietf\:params\:xml\:ns\:xmpp-sasl/callbackhandler-PLAIN=com.my.tigase.auth.MyPlainAuthCallbackHandler sess-man/plugins-conf/urn\:ietf\:params\:xml\:ns\:xmpp-sasl/callbackhandler-OAUTH=com.my.tigase.auth.MyOAuthCallbackHandler sess-man/plugins-conf/urn\:ietf\:params\:xml\:ns\:xmpp-sasl/mechanism-selector=com.my.tigase.auth.AuthMechanismSelector sess-man/plugins-conf/jabber\:iq\:roster/dynamic-roster-classes=com.my.tigase.roster.MyDynamicRoster sess-man/plugins-conf/presence/dynamic-roster-classes=com.my.tigase.roster.MyDynamicRoster sess-man/plugins-conf/presence/skip-offline=false sess-man/plugins-conf/presence/skip-offline-sys=false sess-man/plugins-conf/presence/disable-roster-lazy-loading=false sess-man/plugins-conf/amp/msg-offline=true
Added by Artur Hefczyc about 4 years ago
I am sorry for delayed response. I was away for last few days, hence slow response.
After quick investigation it looks there is indeed something wrong with processing contacts in DynamicRoster. I have added a bug report for you: #2439.
Please add yourself to watchers list to receive updates about resolution progress.