GetServerRole got Issue

[Xtremax]

@layoric

Are you referring to this previous forum post? We would still need a way to reproduce the error. It’s hard when the issue is transient and possibly environment specific. You could try a sample application in a docker environment maybe if you need multiple servers/clients?

No, cases are different, we have 2 projects that use our same Redis Cache but they use different Environment, one uses kubernetes and redis sentinel (see this issue) and one uses IIS Windows and not redis sentinel. The problem with GetServerRole() is from a project that uses IIS and doesn’t use redis sentinel
And as for the issue from the previous forum post we still don’t know why it’s only happening in the production env and currently the issue never appears again and also in the dev env we never find that issue.

@layoric

Looking at the code path it looks like there is a possibility that if the network response is null the resolving of the base.Role method in GetServerRole could result in a null reference which we could throw a seperate/specific error or alternate response for, but this will still fail to resolve the server role, so your application would also need to handle that. One option would be wrap that line in a try catch if you can’t upgrade. In the latest version of ServiceStack we are now handling this to return an unknown role, updated in this commit.

Thank you for your recommendation