Tested several cases :
My app in chrome is using longPolling My app in edge is using foreverFrame Demo app in aspnetzero server and chrome is using serverSentEvents
I noticed quite same behaviors and delays : sometimes very fast, sometimes very long...
So I tested this URL : http://{your-server}/signalr/negotiate?
And you will notice that : "TryWebSockets":false Which means that WebSockets are not being used or even started on server side
Look at this link :[https://github.com/aspnet/SignalR/issues/435])
A workaround has been found to activate SignalR WebSockets on CORE projects.
Would it be possible to add this workarround to next release of aspnetzero template ?
I'm using latest template version 5.1.0. Abp.Web.SignalR v3.4.0 which has a dependency to package Microsoft.AspNet.SignalR.Core 2.2.2
If I'm not wrong, this is the latest SignalR version.
WebSockets are activated on my azure settings.
I've tested a demo on your server and I have same behavior. URL is <a class="postlink" href="http://elevensoft.demo.aspnetzero.com">http://elevensoft.demo.aspnetzero.com</a>
I have captured this issue on a MP4 file (not allowed has attachment on this forum), I can send it to you by mail if you provide one. With this video you can have an idea of the delays.
It's same behavior on my Azure server. On my dev machine I didn't notice such big delays.
Hi,
My app is running on Azure for several month now. I've an Azure Standard subscription (S1) : CPU usage is about 2/3% and Memory usage arround 45%. When trying to chat to an other user, the message sent takes some seconds to be displayed in the chat list (4s to 10s sometimes) Also, when pressing Enter key, the chat message remains in the input field before being displayed in the chat list. In some cases, one message sent can be displayed twice (??)
This behavior is very frustrating when trying to chat with an other user.
Do you have an idea how to improve this ?
Hi,
Just to give a feedback on this. @ismcagdas : you were right ! It was an Azure issue.
After a lot of tests with microsoft support, we ended up by creating a completly new serviceplan and after a fresh deploy, everything was working again.
I didn't had precise explanation of this issue with them but it seems that all Azure ressources should be located in the same region (was not the case before for my app)
Yes support with Azure is on going. The stange thing is that the App was working well and I did not deploy a new version or something else. And this morning not working ?!
I will give a feedback when this issue will be solved
Hi,
My application is down since yesterday. Application is deployed in an Azure App Service since december 2017. I never had a problem with it ; everything was working well since yesterday.
Today, my customers can't connect to the app with error IIS 502.5.
Host is not able to start.
I have following error in azure log : Application 'MACHINE/WEBROOT/APPHOST/NAME-APP' with physical root 'D:\home\site\wwwroot' failed to start process with commandline 'D:\home\site\wwwroot\ELEVEN_SOFT.NAME.Web.Host.exe ', ErrorCode = '0x80004005 : e0434352.
And on latest application log, I found following exception ; this exception points out that a file is not found but it is present in file system (no change has been done) it also mentioned an error on startup.cs line 141 which is code line
await next();
I googled these errors and it could be link with a .NETCORE version issue on server... but I didn't change anything on Azure portal.
Can you please help me to solve this ?
ERROR 2018-01-30 14:24:14,807 [7 ] Microsoft.AspNetCore.Server.Kestrel - Connection id "0HLB7J78B0JHR", Request id "0HLB7J78B0JHR:00000005": An unhandled exception was thrown by the application. System.IO.FileNotFoundException: Could not find file: /Common/Images/logo.png File name: '/Common/Images/logo.png' at Microsoft.AspNetCore.Mvc.Internal.VirtualFileResultExecutor.ExecuteAsync(ActionContext context, VirtualFileResult result) at Microsoft.AspNetCore.Mvc.VirtualFileResult.ExecuteResultAsync(ActionContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.<InvokeResultAsync>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.<InvokeNextResultFilterAsync>d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResultExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.<InvokeNextResourceFilter>d__22.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.<InvokeFilterPipelineAsync>d__17.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.<InvokeAsync>d__15.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Owin.Mapping.MapMiddleware.<Invoke>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Owin.WebSocketAcceptAdapter.<>c__DisplayClass6_0.<<AdaptWebSockets>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.<Invoke>d__4.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at ELEVEN_SOFT.Logisav.Web.Startup.Startup.<>c.<<Configure>b__4_1>d.MoveNext() in C:\Users\ricar\source\repos\Logisav_AspnetZero\aspnet-core\src\ELEVEN_SOFT.Logisav.Web.Host\Startup\Startup.cs:line 141 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.AspNetZeroCore.Web.Authentication.JwtBearer.JwtTokenMiddleware.<>c__DisplayClass0_0.<<UseJwtTokenMiddleware>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.<Invoke>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.<Invoke>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Server.IISIntegration.IISMiddleware.<Invoke>d__11.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Hosting.Internal.RequestServicesContainerMiddleware.<Invoke>d__3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Frame`1.
I agree, Offline management is a must have for a mobile app. I definitly vote for it ! Actually, I've implemented it in 2 different ways (but not on aspnetzero project) : 1 - with Azure web services 2 - with ServiceProxy and Repository classes > data is stored in simple file system
SignalR integration would be very nice also to support notifications and chat.
Good to know :) I will have a try and give a feedback !
Thanks for your replies. I will not spend that time for it. My main goal was to change the purple color and glow effects by the blue color used on demo6.
From your experience, is it easy to do ? any advice would be welcome.