带有AWS ElastiCache Redis的信号机背板出现故障

Question

我有AWS EC2的信号服务。我想用Redis引擎Elasticache设置背板。我可以使用redis cli工具成功连接到Signal服务器中的Easticache。

C:\>redis-cli -h server.cache.amazonaws.com -p 6379 ping
PONG

但当我输入backpalne设置代码时，信号器返回

SignalR： webSocket传输在尝试连接时超时。

没有背板设置代码

GlobalHost.DependencyResolver.UseRedis(server, port, string.Empty, appName);

效果很好。

错误信息如下

[03:31:21 GMT+0000 (Coordinated Universal Time)] SignalR: Negotiating with 'http://server.elb.amazonaws.c…Protocol=1.5&connectionData=%5B%7B%22name%22%3A%22notificationhub%22%7D%5D'.VM47 jquery.signalR-2.2.0.min.js:8  

[03:31:28 GMT+0000 (Coordinated Universal Time)] SignalR: webSockets transport starting. VM47 jquery.signalR-2.2.0.min.js:8

[03:31:28 GMT+0000 (Coordinated Universal Time)] SignalR: Connecting to websocket endpoint 'ws://server.elb.amazonaws.com/signalr/connect?transport=webSockets&clientProtocol=1.5&connectionToken=xSWImxTslxzzk4toiMzjuNod56GaOF27NaT1t1ZkACbNqMC%2BhVRvEFtc2MesygYDRY1ULm%2BtFSo4djNegjcNtuD6lpk1pQQ7ecVZoLFr6aPJ%2FP0HHhUmAjgOVs1FyqQt&connectionData=%5B%7B%22name%22%3A%22notificationhub%22%7D%5D&tid=9'. VM47 jquery.signalR-2.2.0.min.js:8  

[03:31:28 GMT+0000 (Coordinated Universal Time)] SignalR: webSockets transport starting. VM47 jquery.signalR-2.2.0.min.js:8  

[03:31:33 GMT+0000 (Coordinated Universal Time)] SignalR: webSockets transport timed out when trying to connect. VM47 jquery.signalR-2.2.0.min.js:8  

[03:31:33 GMT+0000 (Coordinated Universal Time)] SignalR: Closing the Websocket.
 index.html#/intro:1 WebSocket connection to 'ws://server.elb.amazonaws.com/signalr/connect?transport=webSockets&clientProtocol=1.5&connectionToken=xSWImxTslxzzk4toiMzjuNod56GaOF27NaT1t1ZkACbNqMC%2BhVRvEFtc2MesygYDRY1ULm%2BtFSo4djNegjcNtuD6lpk1pQQ7ecVZoLFr6aPJ%2FP0HHhUmAjgOVs1FyqQt&connectionData=%5B%7B%22name%22%3A%22notificationhub%22%7D%5D&tid=9' failed: WebSocket is closed before the connection is established. VM47 jquery.signalR-2.2.0.min.js:8

[03:31:33 GMT+0000 (Coordinated Universal Time)] SignalR: Websocket closed.

使现代化

当我在服务器本地安装redis后，也出现了同样的问题。看起来不是AWS弹性问题。

Answer 1

原来ELB问题，我增加了SignalR服务器中的TransportConnectionTimeout值。

GlobalHost.Configuration.TransportConnectTimeout = TimeSpan.FromSeconds(1);

问题解决了。