Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
So apparently your front page is cached
I did something retarded today. I spam refreshed this site ALL day from work (on my phone) and then when I got back on my computer in an attempt to get one of these VIP keys. Every 10 seconds I hit F5, it was painful but I figured it would be worth it since I would probably get a key.
Not the case.
How did I see the keys come up? It wasn't on the front page in recent news, it was in the recent forum replies box. By the time I clicked on it it was over 7 pages+ long. Thats terrible, you would think that when something this major gets posted it would show up in the news section of the site, not on the forums where it gets delayed before shown on the front site.
I am so disappointed, what a waste of time. All day refreshing only to end up 116th because the first time I submitted my post I got an error. Sigh
---Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
MMORPG.COM has just experienced an error
The details for this error are:
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Template: /discussion2.cfm
To report this error pleasMMORPG.COM has just experienced an error
The details for this error are:
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Template: /discussion2.cfm
To report this error pleasMMORPG.COM has just experienced an error
The details for this error are:
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Template: /discussion2.cfm
To report this error pleas
MMORPG.COM has just experienced an error
The details for this error are:
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Template: /discussion2.cfm
To report this error pleasMMORPG.COM has just experienced an error
The details for this error are:
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Template: /discussion2.cfm
To report this error pleasMMORPG.COM has just experienced an error
The details for this error are:
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Template: /discussion2.cfm
To report this error pleas
MMORPG.COM has just experienced an error
The details for this error are:
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Template: /discussion2.cfm
To report this error pleas
MMORPG.COM has just experienced an error
The details for this error are:
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Template: /discussion2.cfm
To report this error pleasMMORPG.COM has just experienced an error
The details for this error are:
Details: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. The error occurred on line 330.
Template: /discussion2.cfm
To report this error pleas
Comments
Nimec, it wasn't just you, the rush caused (or seemed to on my end) a ddos like effect - site wasn't accesible at all to me foir a good 2 minutes after I posted, and the lag in posting was epic.
I honestly think the guys in charge had no idea how much of a hosing their server was going to take over this.
No idea what number my post was, but considering it took a good minute and a half to let me post, I probably missed out too.
2 days left...
erm ... why exactly are you telling us that?
Would you tell people you know that you refreshed a website the whole day to get in the TEST of a computergame? and then failed?
whatever, i got my key^^
that sucks
Lol, not only that but over a 60 sec. delay in loading once you get to "Reply" and then further delay in it getting posted; assures you will lose this race. Way too much lag in response caused by the all the refreshing I guess.
I am wondering why this particular Beta key distribution is varying from the usual way, which is a post with a larger header and all the keys grouped, where one usually just enters the 'get' key box and gets directed to the key with instructions?
Cant beat em??? Join em.
Of course it's cached, what do you expect on a popular site like this? At the very least objects, template etc will be disc cached on their server and headers set to tell your browser how long to hold caches for before rebuilding.
This is why you should always do a hard refresh but pressing CTRL+F5 when waiting for something time sensitive to appear.