Wojtek

Thanks for the update. I'm not really thrilled by the AWS response, and not sure if it's exactly accurate... They could simply avoid making instance available again after failover before...

As I said - we will probably add support for that, but in your case you can use suggested JDBC driver to mitigate the issue - either by swapping with...

Unfortunately, it turns out, we do have driver classes hardcoded, so the swapping won't work. I filed a ticket to remove it in the next version.

Thank you for analysing this and the comments. Indeed, in this case the distribution may be sub-optimal. What's more, in mobile environments stream opening may be more frequent than actual...

We do have https://github.com/tigase/tigase-tts-ng (and also older, legacy and not maintained https://github.com/tigase/tigase-testsuite) which could catch those. Though, in this case, using packetFrom should still maintain correct ordering of packets as...

Simple test statistics: # 2500 connections, plain connect/disconnect ## before change: ``` c2s/Processed packets thread IN=[783, 804, 749, 737, 758, 779, 814, 791, 852, 864, 911, 840, 875, 909, 959,...

@karapirinc Yes, please

Merged

After merging TTS tests started to fail with missing packets, which would indicated concurrency issues. For how I reverted the change.

In your code you have: `@Repository.Meta(isDefault = true, supportedUris = {"jdbc:[^:]+:.*"})` (note `supportedUris`!) while your datasource is mongodb: ( `uri = 'mongodb://tigase:…`).