[certi-dev] Fwd: Unsubscribing objectclasses on run causes problems

[Timi Tuohenmaa]

Hi,

I just noticed a problem when some federate executes unsubscribe to
objectclass that it has had subscribed earlier.

If that objectclass had named objects when unsubscribe were executed
it never heard that object was removed and therefore thinks that
selected name was still reserved for later use.

Interestingly creating object with such (mistakenly) reserved name
causes creation of such object to federation but that single federate
thinks create failed.

I had pretty complex program where I noticed this, but from logs it
looked like it missed removes even internally. Obviously I can't be
sure if this was exactly the problem behind, but it helped that I
changed logic that program only unsubscribed on quit.

(using new 3.4.2, but problem existed in 3.4.1 too)

Kind regards,
Timi Tuohenmaa

(note! I already sent this, but I wonder if it actually ended to
post-list as I send address was something I did not use when I
subscribed. Also nobody answered)