Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Subscription initial event gets NetworkTimeout
07-04-2017, 10:34 AM (This post was last modified: 07-04-2017 10:35 AM by simoncn.)
Post: #1
Subscription initial event gets NetworkTimeout
I have been investigating a problem where a client subscribes to a service and the service's attempt to send initial property states and the initial event message to the client fails with a NetworkTimeout error after 3 seconds.

After this, the service takes no further action. The client has not received the initial property states and waits (forever) for this to happen. There are no property updates on the service side, so the service doesn't try to send any more messages to the client. The client continues to renew the subscription successfully, so there is connectivity in this direction.

Would it be possible/reasonable for ohNet to detect at the client end that the initial event was not received and return an error to the application? Or should the client application wait 3 seconds and take action if the initial event has not been received in that time? Where does the 3 second timeout come from and will this be the same on all platforms?
Find all posts by this user


Messages In This Thread
Subscription initial event gets NetworkTimeout - simoncn - 07-04-2017 10:34 AM

Forum Jump: