我有一个没有问题的工作在我的开发环境中SignalR项目,但一旦它被转移到生产几乎所有的通话将失败与错误SignalR给予“的的ConnectionId是格式不正确”
的ConnectionId格式不正确。
我在StackOverflow上看到了一些关于同样的错误信息的其他项目,但是没有一个有帮助的解决方案。
我使用SignalR 2.0.2和SignalR Scaleout with SQL Server,这是一个有效的负载均衡器。
事件代码:3005事件消息:发生未处理的异常。 事件时间:2014/2/11 9:11:27事件时间(UTC):2/12/2014 3:11:27 AM事件ID:cff1fd93fa6d4b83b1848078a905371c事件序列:73 事件发生:10事件详细信息代码: 0应用程序信息:
Application domain: /LM/W3SVC/2/ROOT-3-130366479327251392 Trust level: Full Application Virtual Path:/ Application Path: C:\inetpub\wwwroot\<remvoved> Machine name: BSDUSHC1WW09 Process information: Process ID: 7088 Process name: w3wp.exe Account name: <remvoved> Exception information: Exception type: InvalidOperationException Exception message: The ConnectionId is in the incorrect format. at
Microsoft.AspNet.SignalR.PersistentConnection.GetConnectionId(HostContext 上下文,字符串connectionToken)在 Microsoft.AspNet.SignalR.PersistentConnection.ProcessRequest(HostContext 上下文)在 Microsoft.AspNet。 SignalR.Hubs.HubDispatcher.ProcessRequest(HostContext 上下文)在 Microsoft.AspNet.S ignalR.PersistentConnection.ProcessRequest(IDictionary`2 environment)at Microsoft.Owin.Mapping.MapMiddleware.d__0.MoveNext() ---从以前位置抛出异常的堆栈跟踪结束---在 System.Runtime .ExceptionServices.ExceptionDispatchInfo.Throw()在 Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext.EndFinalWork(IAsyncResult的 AR)在 System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 在System.Web.HttpApplication.ExecuteStep(IExecutionStep步骤中, 布尔型&同步完成)
请求信息: 请求URL:http:/// signalr /连接运输= serverSentEvents & connectionToken = GZlhDBCjkD1/bL1rc4Rlq2PVKYRs0B9nN7b71cU/E6x7sCsFvR1DqM/rBnDhg + URwkYyBlGmrczV59XIn/goyt9x0xXOd8Gs3Qswo1oXqSttH2QPO548C0fbdBvvlUupzS4S0Rl + aShoQwnj + qFDpA == & connectionData = [{ “名称”:” “}]
Request path: /signalr/connect User host address: 10.240.14.26 User: <remvoved> Is authenticated: True Authentication Type: Negotiate Thread account name: <remvoved> Thread information: Thread ID: 23 Thread account name: <remvoved> Is impersonating: False Stack trace: at Microsoft.AspNet.SignalR.PersistentConnection.GetConnectionId(HostContext
上下文,字符串connectionToken)在 Microsoft.AspNet.SignalR.PersistentConnection.ProcessRequest(HostContext 上下文)在 Microsoft.AspNet.SignalR.Hubs.HubDispatcher.ProcessRequest(HostContext 上下文)在Microsoft.AspNet.S。 ignalR.PersistentConnection.ProcessRequest(IDictionary`2 environment)at Microsoft.Owin.Mapping.MapMiddleware.d__0.MoveNext() ---从以前位置抛出异常的堆栈跟踪结束---在 System.Runtime .ExceptionServices.ExceptionDispatchInfo.Throw()在 Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext.EndFinalWork(IAsyncResult的 AR)在 System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep。在System.Web.HttpApplication.ExecuteStep执行() (IExecutionStep一步, 布尔& completedSynchronously)