You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using 2.7.1, I've got one publisher and one subscriber that are statically configured. Both publisher and subscriber are reporting that the domain participants are discovered, and that the listeners on both side are reporting a match via on_publication/subscription_matched().
The problem is that, while the publisher is writing data, the subscriber's on_data_available is not being called. It's on_subscription_matched() did get called. And if I stop the publisher, the match goes down on the subscriber side and loses the participant, as expected.
I've double checked the info in the XML files and all looks well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Using 2.7.1, I've got one publisher and one subscriber that are statically configured. Both publisher and subscriber are reporting that the domain participants are discovered, and that the listeners on both side are reporting a match via
on_publication/subscription_matched()
.The problem is that, while the publisher is writing data, the subscriber's
on_data_available
is not being called. It'son_subscription_matched()
did get called. And if I stop the publisher, the match goes down on the subscriber side and loses the participant, as expected.I've double checked the info in the XML files and all looks well.
Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions