It’s VERY important to notice that ServiceStack is a commercially-supported product. See the free-quotas on servicestack.net. Also this question mentions the same. The ServiceStack.Redis NuGet package include the following limitations: 10 Operations in ServiceStack (i.e. Request DTOs) 10 Tables in OrmLite 20 Different Types in JSON, JSV and CSV Serializers * 20 Different Types in … Read more
There are 3 parts to a lock: the key (the unique name of the lock in the database) the value (a caller-defined token which can be used both to indicate who “owns” the lock, and to check that releasing and extending the lock is being done correctly) the duration (a lock intentionally is a finite … Read more
It looks like in most cases this exception is a client issue. Previous versions of StackExchange.Redis used Win32 socket directly which sometimes has a negative impact. Probably Asp.net internal routing somehow related to it. The good news is that StackExchange.Redis’s network infra was completely rewritten recently. The last version is 2.0.513. Try it and there … Read more
These are the workarounds I’ve found to this deadlock problem: Workaround #1 By default StackExchange.Redis will ensure that commands are completed in the same order that result messages are received. This could cause a deadlock as described in this question. Disable that behavior by setting PreserveAsyncOrder to false. ConnectionMultiplexer connection = …; connection.PreserveAsyncOrder = false; … Read more