1 Mar
2012
1 Mar
'12
4:55 p.m.
Hi Peter,
So the cause was bad data in the db? Was that data corrupted by an
external application, or did presence module insert bad data?
I would really like to investigate this problem thoroughly to be sure
there isn't a bug in the new code.
Regards,
Anca
On 03/01/2012 04:45 PM, Peter Dunkley wrote:
Hi,
I've been doing more investigation myself. It seems that even with
old presence module I can get it to crash here if the records in the
DB are "broken" enough. So I think it was just a co-incidence that I
first spotted the crash with the new code. I suspect that with the
two errors coming out of the new presence code (and the state things
are in when they come out) it is just easier to get the DB records
broken in the right way.
The error messages are actually the bigger issue as they are stopping
presence and RLS working together.
Thanks,
Peter
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd