Missing tokens in Client Liveliness Subscriber with .history(true)

[fuzzypixelz]

Describe the bug

There are cases when a client application asking for liveliness subscribers from the network will receive all known tokens correctly. But an identical client application won't receive the same answer after.

To reproduce

Start two routers (R1 and R2), one peer-to-peer peer (P) and and client (C) in the following topology:

The routers and the client each declare a liveliness token: R1 declares x/r1, R2 declares x/r2 and P declares x/p.

The client declares a liveliness subscriber on x/* with .history(true). The first time this client application connects to P, it receives x/r1, x/r2 and x/p. If the client application is restarted (by closing & reopening the session) then it only receives x/p.

System info

• ref: 965e905

[fuzzypixelz]

Fixed in #1485.