There appears to be a problem with the roster management if the item contains uppercase characters. The roster item seems to be removed correctly from the protocol point of view but it is still preserved in the database.
Hmmm, OK then I have another quick question that maybe you can take a look at while I collect the other XML data.
This is a roster remove of a user that doesn't exist in the database, but was added to the roster (I don't have the "add" XML but I can re-do and collect).
There appears to be a problem with the roster management if the item contains uppercase characters. The roster item seems to be removed correctly from the protocol point of view but it is still preserved in the database.
Hmmm, OK then I have another quick question that maybe you can take a look at while I collect the other XML data.
This is a roster remove of a user that doesn't exist in the database, but was added to the roster (I don't have the "add" XML but I can re-do and collect).
The "remove" XML:
SEND >>>>>>>>>>>>>>>> : Thu Jan 1 02:43:33 1970
[9813.091552] CALL: [InfoQueryOutTask::ProcessStart] exit
RECV <<<<<<<<<<<<<<<< : Thu Jan 1 02:43:33 1970
RECV <<<<<<<<<<<<<<<< : Thu Jan 1 02:43:33 1970
Here is the database after the remove
mysql> select nid,uid,pkey,pval from tig_pairs where pkey="roster" and uid=TigGetUserUID('cds3@example.com');
+------+-----+--------+----------------------------------------------------------------------------------------+
| nid | uid | pkey | pval | +------+-----+--------+----------------------------------------------------------------------------------------+
| 89 | 67 | roster | | +------+-----+--------+----------------------------------------------------------------------------------------+
1 row in set (0.00 sec)