ServiceStack.Redis 无法连接:sPort:0,在 Windows 服务器的 IIS 上部署时
ServiceStack.Redis Unable to Connect: sPort: 0, when deploying at IIS in a Windows Server
我正在使用 IIS 构建在 Windows 服务器上发布的 .Net Core 应用程序后端。在这种情况下,用户可以创建一个会话并接收发送给它的消息。会话和消息存储在数据库中,但为了使其更快,我将 Redis 与 PubSub 工具一起使用,该工具处理消息而不是实际对应的 REST 请求。
明确地说,创建会话时,也会创建对 Redis 通道的订阅,并将消息发布到该通道,然后处理程序将消息存储在数据库中。
我使用的是 ServiceStack.Redis 的许可版本,并且在 Visual Studio (Kestrel) 的开发服务器中一切正常,但是一旦我将它部署到 IIS,我大部分时间都会遇到这个错误时代:
Unable to Connect: sPort: 0, Error: Object reference not set to an instance of an object.
at ServiceStack.Redis.RedisNativeClient.Connect()
at ServiceStack.Redis.RedisNativeClient.SendReceive[T](Byte[][] cmdWithBinaryArgs, Func`1 fn, Action`1 completePipelineFn, Boolean sendWithoutRead)
这有点随机,因为也许可以订阅几个频道,然后又开始失败一段时间,或者从一开始就失败。服务器的防火墙被禁用,Redis 已通过 msi 安装程序作为默认配置的服务安装,并且 redis-cli 工作正常。事实上,我可以从 redis-cli 订阅一个频道,并通过后端向该频道发送消息,没有任何问题。
正如 this question's answer 所建议的那样,我已尝试向 Redis 客户端添加更大的超时,但仍然失败。
这是代码,如果它有帮助的话:
private void CreateRedisSubscription(string channelName)
{
_log.LogInformation("Creating subscription to channel " + channelName);
using (RedisClient redisClient = new RedisClient(Globals.REDIS_HOST, Globals.REDIS_PORT)){
// Too big timeout to make sure the error it's not because of a timeout.
redisClient.ConnectTimeout = 30000;
using (subscription = redisClient.CreateSubscription())
{
subscription.OnSubscribe = channel =>
{
Console.Write("Subscribed to channel: " + channel);
};
subscription.OnUnSubscribe = channel =>
{
Console.Write("Unsubscribed from channel: " + channel);
ThreadsMember threadMember = subscriptionThreads.Find(t => t.ThreadName.Equals(channel));
if(threadMember != null)
{
threadMember.subscriptionThread.Abort();
subscriptionThreads.Remove(threadMember);
}
};
subscription.OnMessage += (channel, message) => ProcessMessage(channel, message);
Thread thread = new Thread(() =>
{
try{
subscription.SubscribeToChannels(channelName);
_log.LogInformation("Subscribed to channel " + channelName);
}catch (Exception e)
{
Console.WriteLine(e.Message);
_log.LogWarning("Can not subscribe to channel " + channelName);
_log.LogError(e.Message);
_log.LogTrace(e.StackTrace);
if(e.InnerException != null)
_log.LogError(e.InnerException.Message);
}
});
thread.IsBackground = true;
//Add the thread to a list for future management (unsubscribe from that channel)
subscriptionThreads.Add(new ThreadsMember(channelName, thread));
thread.Start();
}
}
}
提前致谢。
应避免使用 Thread.Abort()
,因为它会使中止的实例处于不一致的状态。
我建议改用 ServiceStack.Redis managed subscription,它负责管理订阅并让您实现回调来处理不同的订阅事件:
var clientsManager = new PooledRedisClientManager();
var redisPubSub = new RedisPubSubServer(clientsManager, "channel-1", "channel-2") {
OnMessage = (channel, msg) => "Received '{0}' from '{1}'".Print(msg, channel)
}.Start();
我正在使用 IIS 构建在 Windows 服务器上发布的 .Net Core 应用程序后端。在这种情况下,用户可以创建一个会话并接收发送给它的消息。会话和消息存储在数据库中,但为了使其更快,我将 Redis 与 PubSub 工具一起使用,该工具处理消息而不是实际对应的 REST 请求。 明确地说,创建会话时,也会创建对 Redis 通道的订阅,并将消息发布到该通道,然后处理程序将消息存储在数据库中。
我使用的是 ServiceStack.Redis 的许可版本,并且在 Visual Studio (Kestrel) 的开发服务器中一切正常,但是一旦我将它部署到 IIS,我大部分时间都会遇到这个错误时代:
Unable to Connect: sPort: 0, Error: Object reference not set to an instance of an object.
at ServiceStack.Redis.RedisNativeClient.Connect()
at ServiceStack.Redis.RedisNativeClient.SendReceive[T](Byte[][] cmdWithBinaryArgs, Func`1 fn, Action`1 completePipelineFn, Boolean sendWithoutRead)
这有点随机,因为也许可以订阅几个频道,然后又开始失败一段时间,或者从一开始就失败。服务器的防火墙被禁用,Redis 已通过 msi 安装程序作为默认配置的服务安装,并且 redis-cli 工作正常。事实上,我可以从 redis-cli 订阅一个频道,并通过后端向该频道发送消息,没有任何问题。
正如 this question's answer 所建议的那样,我已尝试向 Redis 客户端添加更大的超时,但仍然失败。
这是代码,如果它有帮助的话:
private void CreateRedisSubscription(string channelName)
{
_log.LogInformation("Creating subscription to channel " + channelName);
using (RedisClient redisClient = new RedisClient(Globals.REDIS_HOST, Globals.REDIS_PORT)){
// Too big timeout to make sure the error it's not because of a timeout.
redisClient.ConnectTimeout = 30000;
using (subscription = redisClient.CreateSubscription())
{
subscription.OnSubscribe = channel =>
{
Console.Write("Subscribed to channel: " + channel);
};
subscription.OnUnSubscribe = channel =>
{
Console.Write("Unsubscribed from channel: " + channel);
ThreadsMember threadMember = subscriptionThreads.Find(t => t.ThreadName.Equals(channel));
if(threadMember != null)
{
threadMember.subscriptionThread.Abort();
subscriptionThreads.Remove(threadMember);
}
};
subscription.OnMessage += (channel, message) => ProcessMessage(channel, message);
Thread thread = new Thread(() =>
{
try{
subscription.SubscribeToChannels(channelName);
_log.LogInformation("Subscribed to channel " + channelName);
}catch (Exception e)
{
Console.WriteLine(e.Message);
_log.LogWarning("Can not subscribe to channel " + channelName);
_log.LogError(e.Message);
_log.LogTrace(e.StackTrace);
if(e.InnerException != null)
_log.LogError(e.InnerException.Message);
}
});
thread.IsBackground = true;
//Add the thread to a list for future management (unsubscribe from that channel)
subscriptionThreads.Add(new ThreadsMember(channelName, thread));
thread.Start();
}
}
}
提前致谢。
应避免使用 Thread.Abort()
,因为它会使中止的实例处于不一致的状态。
我建议改用 ServiceStack.Redis managed subscription,它负责管理订阅并让您实现回调来处理不同的订阅事件:
var clientsManager = new PooledRedisClientManager();
var redisPubSub = new RedisPubSubServer(clientsManager, "channel-1", "channel-2") {
OnMessage = (channel, msg) => "Received '{0}' from '{1}'".Print(msg, channel)
}.Start();