SD Device, after registering with RA, and after CP is registered with RA, have two threads that try to insert the same nonce.
The second nonce is ignored, and the flow is correct.
However, maybe there is an elegant way to handle this.
Registering SD with RA..
[SUPnP] [tid 124539291829952] RegistrationCallbackEventHandler(767): SUPnP Device Registered
[SUPnP] [tid 124539291829952] RegistrationCallbackSD(1415): SD registered with RA successfully.
[SUPnP] [tid 124539291829952] SUpnpSendAdvertisement(1038): Secure Service Advertisement: sending..
[SUPnP] [tid 124539302315712] SUpnpSecureServiceDiscoveryVerify(1199): Secure Service Discovery verification..
[SUPnP] [tid 124539302315712] SUpnpSecureServiceDiscoveryVerify(1203): Secure Service Discovery successful.
[SUPnP] [tid 124539151320768] SUpnpSecureServiceDiscoveryVerify(1199): Secure Service Discovery verification..
[SUPnP Error] [tid 124539151320768] .upnp/src/supnp/supnp.c::SUpnpVerifySecureParams(957): nonce already exists. Dropping message..
[SUPnP Error] [tid 124539151320768] .upnp/src/supnp/supnp.c::SUpnpSecureServiceDiscoveryVerify(1205): Secure Service Discovery failed!!! -- -608
[SUPnP] [tid 124539312801472] SUpnpSendAdvertisement(1038): Secure Service Advertisement: sending..
[SUPnP] [tid 124539291829952] SUpnpSecureEventingVerify(1454): Secure Event Subscription verification..
[SUPnP] [tid 124539291829952] SUpnpSecureEventingVerify(1459): Secure Event Subscription successful.
In the run log, the thread 124539151320768 is doing duplicate logics as 124539302315712.
SD Device, after registering with RA, and after CP is registered with RA, have two threads that try to insert the same nonce.
The second nonce is ignored, and the flow is correct.
However, maybe there is an elegant way to handle this.
In the run log, the thread
124539151320768is doing duplicate logics as124539302315712.