This fixes a regression where a successful response to /meta/connect message caused a resubscription of pending subscriptions (the ones waiting for the response to the /meta/subscribe request) -- this caused unexpected number of channel subscribers. To remedy that:
only failed subscriptions are processed as a result of /meta/connect message
subscribe method is synchronized and there is a check if subscribing channel was already subscribed with the same handlers
There are also:
new integration tests for realtime operations
a test for this specific regression with duplicate subscriptions
some cleanup: disconnecting subscribers in integration tests after the tests so the threads are not hanging and we don't have weird messages logged
This fixes a regression where a successful response to
/meta/connectmessage caused a resubscription of pending subscriptions (the ones waiting for the response to the/meta/subscriberequest) -- this caused unexpected number of channel subscribers. To remedy that:/meta/connectmessageThere are also: