08/30/11
Charm just had a nest fail to coax. The CSR claims it was a duplicate and that she (Charm) transferred the nest to someone else. That did NOT happen.
I'm becoming concerned that Malevay is claiming problems due to sim crash/rollback far too often.
I went to the sim where the nest was obtained. It has NOT reset recently, and there are NO other duplicates anywhere there.
The error MUST have occurred after 22:00 last night since the sequence number is greater than last night's number at that time.
So, we're forced to accept the extremely unlikely event that a sim, which has not reset recently, underwent a rollback earlier today without resetting, and the ONLY duplicate object created was Charm's nest.
I've seen a number of other complaints recently about duplicates. To me, the problem seems to be occurring FAR too often to be explained by sim crashes.
It causes me concern that the problem is with transactional reliability between SL and the Mothership. It seems far more likely that the Mothership did not properly record the sequence number being assigned and assigned it again.
With the abnormally high number of sequence numbers being assigned yesterday and today, a race condition would be FAR more likely to occur now than, say, last week.