Good Day everyone
We created a Blazor Server application and deployed in on our web server (windows 2019) with IIS as our host, now the site is okay when deployed but, sometimes if there are too many users accessing the site of if few members are requesting too much,the site does not working properly,or it does not,the fix we are doing for this is to stop and start the app on the IIS, and this is not a best practice as we have to this again everytime the app is not working,we check the event log, but we did not see any errors, this scenario always happen on both of our staging and production, what do you think is the cause of this problem?? And how to fix it?
Edit: I have to clarify, according to our team they are only 10 people who is using the app, both prod and staging is encountering the issue, and I'm on dead end
we put an Idisposable on our application, to dispose of resourcers, and we are currently checking if the application will still experience unresponsiveness after a number of people accessing the application, we also fix the javascript errors, that might be the cause of unresponsiveness
thank you for your comments and suggestions
Related
I have some Web API applications that uses OWIN for authentication. Currently they are hooked up to Google and Facebook. I have them installed in multiple environments (local, dev, test, etc). Recently ALL of my applications in my development environment started failing. When trying to authenticate I would get a response back "access_denied". The URL would look like this:
https://{mydevserver}/{mywebapiapp}/#error=access_denied
The same code base works locally as well as in my test environment.
I tried using the same project (just adding redirect uris and orgins) as well as creating a new project.
I also updated my test environment to use the dev project (id and secret).
Nothing seems to have changed on the server recently. But it seems to be environment specific (because multiple applications are affected as well as multiple providers).
Are there any logging techniques I can use to drill down to a more detailed error message? Any tips or hints for what to try next?
The fix was a bit of an odd one. I had to log into my server, open up a browser and connect to a web page (any page). After doing so it started working again.
I'm using Jelastic with Flow AppEngine in Switzerland to host some applications and just recently after changing a configuration file (and hitting Save) the environment became unresponsive from an admin panel perspective. It loads all fine from the front-end but I don't think my configuration took place as I didn't have a chance to reload the service (NGINX) after having touched the config.
The behavior I see is that right after logging in to the administration panel, the loader keeps on spinning with the "Loading user data..." message and never finishes. The panel I login to is: https://app.appengine.flow.ch which seems to be using the latest Jelastic release.
UPDATE:
After a long time waiting, it's now moved to "Get environments..." and it's currently stuck there.
Seems like a platform error. Recommend that you contact your hosting provider for help to resolve it.
On that day (29.Dec 2013), there was a routing issue wich caused that.
It has been (already) fixed at the same day.
For future requests, feel free to contact us directly via help # innofield.com
Cheers,
Bojan
I've published my project on my VPS server (MVC 3 project). Now, is it somehow possible to debug the code during the project is being runned on the server ? The same way when it's running on the localhost.
There might be but I believe the fact that you're trying to is a bad sign. By the time you deploy your app you should have proper logging and error handling which should allow you to track down any bugs that occur and reproduce them in your development environment.
I generated a self-signed cert, exported and uploaded to the subscription. When I deploy to staging, all works well when I navigate to the app (MVC) it redirects to https appropriately, I get the warning but all works perfect when I continue to the site. When I deploy same package to production, none of my roles responds, to web requests or tcp, I can't even RDP into the VMs.
Any ideas?
EDIT: I'm going to say this is closed. I gave it an hour (watched tv to clear my head).. and it started functioning correctly. Perhaps it just took an extra long time to spin up the VMs.
Some time it take longer then expected for the role to start and if you are interested to know why I have explained in the following SO question:
Is there a way to reduce time between Azure deployment start and role OnStart() code being invoked?
Want to know more let me know and I would love to explain in much finer details.
I have implemented Continuous Integration using TFS Version Control and TFS Build 2010. The compiled website project gets dropped in a shared folder with a version number.
Now I have a very basic question and may be a stupid question. When we normally deploy a website project from VS 2010 to a webserver it uploads App_Offline.htm file to the website folder so no requests are served to the user. After publish is completed that App_Offline.htm file is removed. During that period of time users see outage.
If we use CI on a live website then how can we eliminate that outage which appears to a user. I believe the whole point of CI is that users get to see newer features and the site is never down.
How is this accomplished? If we deploy website project to root folder then existing users will be affected and that is certainly no advisable.
I wanted to know what is the recommended practice with VS2010, TFS2010 Build & Version Control.
There's no real foolproof method for this, service up-time is never 100%, that's why people usually define it in 'nines'
But, if you had multiple web servers (Backup, fail-over, mirror etc.), you could roll out the update across them, so that as you update some servers, others will still be online (albeit with the old version) to serve users.
In general, only some of the largest websites have to worry so meticulously about being down for a few short minutes, so make sure you're focusing your energy in the right place ; )
Regarding taking down the site for the shortest time possible, the only way I've seen this done successfully is using multiple sites - either load balancing, or 2 sites on the same machine + swapping host headers after the release/warm up. But in most cases it's not worth the effort, releases shouldn't take down the site for more than a few seconds in which time there should be relatively few requests. You're better off trying a few things you can do to help your users live through a site release.
Move session out of proc.
If the users session lives in the app pool it will be lost when a new version is released, change the config to move it into a session server or the database.
Specify a machine key for the website
Viewstate (and cookies?) are encrypted using a key that is generated when a site starts, if a site restarts due to a release any users filling out a form will receive a invalid viewstate exception on postback. (Note: this may have other security implications)