mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Fondermann <bf_...@brainlounge.de>
Subject Re: Offline stanza storage
Date Wed, 19 Jan 2011 11:57:24 GMT
Do you use a persistent roster, eg. JcrRosterManager? Or in-memory?


On 19.01.11 12:50, Thomas Kratz wrote:
> Hi Bernd,
> it gets even stranger. I have three users: server, admin and nobody.
> server logs in first at startup and adds other users to its roster.
> then i login as admin from the client and add other users to my roster.
> server sees admin become available.
> then i login as nobody and add other users to my roster. server sees
> nobody become available, but querying the roster of nobody tells me
> admin is offline. roster of server sees admin online. must be some
> little detail.
> Regards Thomas
> 2011/1/19 Bernd Fondermann<bernd.fondermann@googlemail.com>:
>> On Wed, Jan 19, 2011 at 11:13, Thomas Kratz<eiswind@googlemail.com>  wrote:
>>> Hi Bernd,
>>> as it defaults to store=false this shouldn't be the point.
>>> I guess its somewhere else, as I came from 0.5 release where
>>> everything worked fine. Has something changed in roster/subscription
>>> management since then ? I used to have a SubscriptionPacketListener
>>> that auto-responds to subscription requests, but that doesnt seem to
>>> work now.  I do built rosters lazy on startup dynamically. From what i
>>> see in debug, the presence available doenst go to offline storage as
>>> subscription packets do, so it should go to my Smack rosterListener. I
>>> think it must be the subscriptions management that's different now?
>> I can't remember any specific changes there, but you'd have to review
>> svn to confirm that, as any smaller change could have broken your
>> setup.
>> Subscription is definitively working on trunk, at least for me. Also,
>> I highly recommend to move to 0.6, to TRUNK even.
>> So the current working thesis is that this is unrelated to offline
>> stanza storage, right?
>> I might figure out what your problem is if you'd share more detailed
>> info, like logs or a simple test scenario.
>>   Bernd

View raw message