使用SignalR槽Azure(ASP .NET)时出现问题。我已经设置了服务器中心,并且生成的js客户端中心从服务器中心获取了所有服务器功能,但是当我在客户端上调用服务器功能时,不会在服务器上调用它们。
在websocket的Chrome的“消息”选项卡上,我可以将消息通过打开的连接发送到azure,但是在从azure到服务器消失的途中。
其他任何人都有相同的问题,并且知道可能是什么问题?
日志:
Microsoft.Azure.SignalR Information: 0 : [Microsoft.Azure.SignalR.Connections.Client.Internal.WebSocketsTransport]Starting transport. Transfer mode: Binary. Url: 'wss://xxxx.service.signalr.net/aspnetserver/?hub=testing.startup_testing.startup&cid=xxxxc'.
Microsoft.Azure.SignalR Information: 0 : [Microsoft.Azure.SignalR.Connections.Client.Internal.WebSocketsTransport]Starting transport. Transfer mode: Binary. Url: 'wss://xxxx.service.signalr.net/aspnetserver/?hub=testing.startup_negguhub&cid=xxxx'.
Microsoft.Azure.SignalR Information: 0 : [Microsoft.Azure.SignalR.Connections.Client.Internal.WebSocketsTransport]Starting transport. Transfer mode: Binary. Url: 'wss://xxxx.service.signalr.net/aspnetserver/?hub=testing.startup_xxxx&cid=xxxx'.
Microsoft.Azure.SignalR Information: 0 : [Microsoft.Azure.SignalR.StrongServiceConnectionContainer]Hub 'NegguHub' is now connected to '(Primary)https://xxxx.service.signalr.net'.
Microsoft.Azure.SignalR Information: 0 : [Microsoft.Azure.SignalR.StrongServiceConnectionContainer]Hub 'xxxx' is now connected to '(Primary)https://xxxx.service.signalr.net'.
Microsoft.Azure.SignalR Information: 0 : [Microsoft.Azure.SignalR.StrongServiceConnectionContainer]Hub 'Testing.Startup' is now connected to '(Primary)https://xxxx.service.signalr.net'.
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c
Microsoft.Azure.SignalR Error: 0 : [Microsoft.Azure.SignalR.AspNet.ServiceConnection]Error when processing messages. Id: dea3a65d-3785-4a49-9821-73eb6552306c