3
My application is crashing and I don’t know exactly why. The only thing that repair is that when there are many users accessing, or making requests it happens.
When it happens I have to restart the application pool and raise the application again.
My question is, how should I investigate this?
I don’t know how to simulate many users accessing.
1
There may be several factors and it is difficult to determine without knowing your environment. What I would recommend to do is the following:
Try to check the performance of your application’s queries and if it doesn’t let you query large tables entirely (e.g., query screens where you don’t specify anything and it returns all the table records at once). Several of these occurring at the same time will stop the bank.
Check if there is any case where the database gets locked (locked) when inserting or updating a table for a long time, as it may occur that you insert or update a table without commiting or rollback, perform a lengthy query before committing and in the meantime another user would try to do the same process by locking the database.
Always after running an application script, make sure the connection is closed before closing it. Usually MVC already takes care of this, but in applications where you need to open the connection manually, they should be closed when exiting the application, avoiding leaving blocked tables
Browser other questions tagged c# asp.net-mvc oracle session iis
You are not signed in. Login or sign up in order to post.
One more detail, if you or someone uses some tool to test the database (PL/SQL, MYSQL Workbench, etc), check if you leave any tables blocked, forgetting to give the commit or rollback in any of this database
– jefissu