Issue #24395 broke "user" destinations

[alienisty]

Affects: 5.3

User destinatinations are registered using the subscription-id and therefore they get ignored in SessionInfo in case the related "topic" destination has been registered before.
The optimisation performed in #24395 has removed such support by trying to optimise cache lookup, expecting that the subscription-id was unique for a destination, which is not. The same submission-id can be used for multiple destination, that is.

[nkavtur]

Having same problem. One ws connection establishes two subscriptions to my app.
Both of them having same sessionId and subscriptionId. DefaultSubscriptionRegistry registers only first one.

[alienisty]

Hi @nkavtur try reading #26986, specifically #26986 (comment) and following comments should help you solve your problem.

This issue should probably by closed.