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
That would completely consistent with a process doing:
create writer A (seq# 1)
create writer B (seq# 2)
delete writer B (seq# 3)
create writer C (seq# 4)
create writer D (seq# 5)
create writer E (seq# 6)
and then looking at the capture of messages sent to a second process started after writer E was created.
Seq# 3 is sent to all processes that exist at the time of deleting writer B (but that's not what we're looking at), then seq# 2 and seq# 3 are dropped from the history because they are no longer relevant and don't get sent to this second process. The presence of INFO_DST and readerEntityId ≠ 0 are also consistent with this scenario.
It can be seen from the packet capture results that the serial number jumps directly from 1 to 4. How to troubleshoot this problem?
The text was updated successfully, but these errors were encountered: