Home Community Forums Digital Republic SERVER BUSY !!!!!!!!!!!!!!!! (F*CK IT !)

Dates

· UTC

SERVER BUSY !!!!!!!!!!!!!!!! (F*CK IT !)

Archived

11 replies · 302 views

This is an archived legacy thread. Replies are closed, but the discussion is preserved.

← Back to Digital Republic

12 posts

10 Feb 2005, 12:09

Server Error in '/' Application.

Server Too Busy Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Server Too Busy

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Server Too Busy] System.Web.HttpRuntime.RejectRequestInternal(HttpWorkerRequest wr) +148

Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032

10 Feb 2005, 12:13

Apparently, too many people are visiting the site at the current moment.

I'd be curious to look at the stats.

I fear our friendly neighbour googlebot is roaming the site as we speak.

10 Feb 2005, 12:30

UHUHUHUHUHUHOHOHOHOHOHOHOHOHOHOAHAHAHAHAHAHAHAHAHA!!!! :evil2:

10 Feb 2005, 14:45

Bl..dy newbies again.
Sorry , Welcome all

11 Feb 2005, 13:16

This busy period is eating replies too. Received error message when submitting a post and it just disappeared after resubmitting.... :computer2:

11 Feb 2005, 13:19

Relax and have a beer! :nod:

11 Feb 2005, 13:25

Originally posted by NObabe Relax and have a beer!

Had 2 already - care to join me in a glass of Slivovice? :beer2:

11 Feb 2005, 13:27

Just so you understand this problem. The web server received requests from users and queue them.

So when the queue is full, you get a "server too busy" error.

The queue is either 100 or 500 requests, I've seen both numbers. 100 seems more accurate. I could increase it, but it would probably piss the host.

This means that there are more than 100 people on the website waiting for an action...

Best way to fix this is to try to avoid calls to the server, but that's the problem, NOOL is entirely based as "server side"...

Now I understand why in the businesses, they put those type of websites on 4 servers... we are on 1 server shared with probably 40 other websites, and by being busy, we cause problems to the other too... (our queue is only for us, those sites have no impact)

Problem is... upgrading the website is not cheap.. going from 20$/month to 80$/month... and the only difference you'll see is a faster site, nothing else will change!

I'll have to check what can be enhanced, but the site could be put offline by our host any day now...

11 Feb 2005, 13:38

Originally posted by Jeff The Chef Had 2 already - care to join me in a glass of Slivovice? :beer2:

Beer's ok with me. I don't like sljivovica. :beer:

11 Feb 2005, 13:39

Originally posted by Jeff The Chef Had 2 already - care to join me in a glass of Slivovice? :beer2:

Beer's ok with me. I don't like sljivovica. :beer:

11 Feb 2005, 14:34

Originally posted by NObabe > Originally posted by Jeff The Chef> > Had 2 already - care to join me in a glass of Slivovice? :beer2:

Beer's ok with me. I don't like sljivovica. :beer:

Got half a bottle of Becherovka here - goes great with a Budvar! :beer:

11 Feb 2005, 14:35

IT'S BEEN ALMOST IMPOSSIBLE TO BROWSE THIS SITE DURING THE WHOLE DAMN DAY !!!!!!!!

IT'S STUCK !!!!!!!

If it's gonna be like that, better close it!!!!!!!