Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Solved] EventSessionUpnp::Run, ReaderError handling - Endless subscription loop
21-11-2016, 04:40 PM
Post: #2
RE: EventSessionUpnp::Run, ReaderError handling - Endless subscription loop
I've seen this type of issue a couple of times previously. In these cases, a device on the network was sending an evented update that the control point viewed as invalid. When this happens, ohNet unsubscribes from the problem device/service then creates a new subscription.

Creating a new subscription is exactly the right thing to do in cases where a control point has missed one or more updates from a device. It's the wrong thing to do in cases where the device always sends invalid updates. Unfortunately ohNet does not currently distinguish between these two cases.

Assuming you have a test setup that demonstrates the problem fairly reliably, I'd add some custom logging to ohNet to print all HTTP traffic received by its UPnP eventing server. If you want to try this, add the line
Code:
LogVerbose(true);
at the top of EventSessionUpnp::Run() in ohNet/OpenHome/Net/ControlPoint/Upnp/Event.cpp

After this, rebuild ohNet then re-run your test. All UPnP eventing traffic will be logged to console (or wherever you have re-directed logging to). Look out for events from the device that fails and conpare them to UPnP/HTTP specs or events from devices that work.
Find all posts by this user


Messages In This Thread
RE: EventSessionUpnp::Run, ReaderError handling - Endless subscription loop - simonc - 21-11-2016 04:40 PM

Forum Jump: