Dear Dombiak,
thanks for your response.
The problem in my case was, that the client did not escape the first @ in the JID.
Which caused the server to stop sending contact lists to the client.
the clients send this like normal:
{/code}
but then the server responds nothing.
here is what i did to discover the problem:
i tried to delete the user which caused the problem.
wildfire told me, that there is an illegal jid, but deleted the user anyway.
BUT: it did not delete the users roster.
i added a user with the same account name again… and tried to delete it again.
got the same illegal JID error. this was the point where i knew that i had to look into
the roster database, as this was obviously not deleted… i am using the mysql variant.
in the roster database i found a jid with two @ which i changed to something else…
and voila wildfire send the roster contacts to the clients again.
just a sidenote:
in the situation where the “double @ jid” was in the database even the user import/export plugin
delivered just a blank page when trying to export the user database to screen.
so there really has to be a problem which causes wildfire to stop accessing the roster database when there is an illegal jid in it… (at least under some conditions, maybe just when using mysql?)
best regards & greetings from germany.