WoW Classic Stress Test 1

WoW Classic WoW Classic General Discussion
1580

I would say this stress test is a success stressing everyone out.

4 Likes
1581

Started trying at 4 pm… never did make it to the point of actually connecting to the realm. Servers gone. I give the stress test a failing grade since I couldn’t even participate… Was more stress for me to get disconnected 974 times. :stuck_out_tongue:

1 Like
1582

You still have until tomorrow.

1583

My experience was similar to other users. I did manage to make it to character creation twice in the dozen or so times that I sat in queue. My initial place in queue averaged 800 to 2700. No bugs from what I could tell.

1584

I feel your pain

1585

Surely you can’t be this goofy. The servers can handle more players online and playing 1-5, Blizzards aim is not to test this exceedingly so. They would simply source more racks and processing power if they wanted to test any more people running 1-5. The aim is queue, priority process, stress and simulation which is being accurately tested as you return to the beginning of the process again and again.

Your knowledge in this area is lacking at best. What you think Blizzard told you was to aid you into logging in with an expectation. They were successful in this feat. You’re knowledge of testing queues might have the opposite effect, you wouldn’t want to participate in the test or help Blizzard collect this data.

You getting levels 1-5 is infinitesimally less valuable and not what they need in these first hours of stress test. Come back later or tomorrow if you don’t want to assist blizzard in testing and just want the 1-5 incentive/carrot.

2 Likes
1586

We expect to put a lot of people in the starting zones, though, and we’re looking forward to seeing what you all do as we test the servers under crowded conditions.

Tell me please…which part of this you don’t understand? LOGIN SERVERS ARE NOT GAME SERVERS

Blockquote

2 Likes
1587

I saw a 3700 que once, but on avg 2500. Got to character selection a few times but never got to play.

2 Likes
1588

I mean, I get it. They wanted as many people on to test the login server as possible, and not nearly as many people would have helped out if they there transparent that most of us would not be getting past character creation. And it’s pretty clear from how some people are very visibly able to get in after DCs while most of us can’t even log in now that this is how it is.

I get it … still pretty scummy move, tho.

1 Like
1589

We expect to put a lot of people in the starting zones, though, and we’re looking forward to seeing what you all do as we test the servers under crowded conditions.

Tell me please which part of this u dont understand?? Login servers are not game servers.

1 Like
1590

I am having the same issue, when I log in I either get disconnected, or it says “No realm listed”

1591

----------------Connection log------------------------------------
5/22 18:58:12.850 Connection Initialize
5/22 18:58:16.139 Glue Start Login
5/22 18:58:16.139 BattleNet Attempt Logon
5/22 18:58:16.332 BattleNet Front Connected
5/22 18:58:16.456 BattleNet Logon Queue Update
5/22 18:58:16.734 BattleNet Logon Complete
5/22 18:58:16.780 BattleNet Game Account Name
5/22 18:58:16.863 BattleNet Game Account Name
5/22 18:58:16.863 BattleNet Attempt Complete Login
5/22 18:58:17.459 BattleNet Realm List Ticket
5/22 18:58:17.505 BattleNet Sub Region List
5/22 18:58:37.059 BattleNet Last Played Char
5/22 18:58:57.082 BattleNet Realm List
5/22 18:58:57.082 Glue Fatal Error: 2147483957
5/22 18:58:57.082 BattleNet Defer Disconnect
5/22 18:58:57.082 BattleNet Front Disconnecting
5/22 18:58:57.121 BattleNet Front Disconnected
5/22 18:59:02.959 Connection Destroy

-----------------------------Agent Log---------------------------------------------
5/22 19:00:24.724 AgentCommunicator::Initialize(): uid = ‘wow_classic_beta’
5/22 19:00:24.724 Reading agent.dat file to determine agent port.

5/22 19:00:24.724 Reading agent.dat file to determine agent port.

5/22 19:00:24.724 Agent communicator initialized. Agent path: ‘C:/ProgramData/Battle.net/Agent/Agent.exe’ URL: ‘127.0.0.1’
5/22 19:00:26.196 Connecting to agent on port 1120
5/22 19:00:26.338 Successfully sent message 1 to agent
5/22 19:00:26.363 Received response. MSG 1, response code 200
5/22 19:00:26.363 Connecting to agent on port 1120
5/22 19:00:26.370 Successfully sent message 16 to agent
5/22 19:00:26.370 Received response. MSG 16, response code 200
5/22 19:00:26.370 Connecting to agent on port 1120
5/22 19:00:26.370 Successfully sent message 10 to agent
5/22 19:00:26.370 Received response. MSG 10, response code 200
5/22 19:00:26.370 Successfully sent message 12 to agent
5/22 19:00:26.381 Connecting to agent on port 1120
5/22 19:00:40.881 AgentCommunicator::Shutdown()
5/22 19:00:41.884 AgentCommunicator::DetachFromAgent(): Timeout. Request took more than 1000ms.

----------------------Client Log------------------------------------------------------
5/22 19:11:00.242 Client Initialize.
5/22 19:14:07.480 Initial Hotfixes: Received
5/22 19:14:07.480 Initial Hotfixes: Fake Connect
5/22 19:14:07.480 Initial Hotfixes: Requested
5/22 19:14:07.490 Initial Hotfixes: Applied

4 Likes
1592

Stress test seemed like it went well so far they are probably just fixing up the servers and then gonna open them up again for another test to see how much they can handle that’s what these things are about

1593

I played for over an hour after starting late, was part of a mad rush of horde racing to silithus. arrived and made it halfway across the zone before a crash, now the realms are all gone it seems. had a lot of fun, even ran past an undead warrior named asmongold, Im as amazing as a streamer for “magically” getting in. Does this make me famous also? or just lucky enough to not crash during a test meant to crash the test. Oh, and he is also offline it looks like if you check so maybe he isn’t getting preference?

1594

For those thinking that folks with closed beta invites were able to connect smoothly and without issue, I can state that this was not the case for me.

It took approx 45 minutes of doing the “queue/disconnect” cycle to get to a character generation screen the first time, and another 10 minutes of “queue/disconnect” cycle to get into the game with a character. After a while of waiting for a guildmate to make it into the game, I played for a bit before the server disconnected me again, and since have not been able to reconnect.

No complaints here, as this is the purpose of a stress test, but wanted folks to be aware that closed beta invitees also experienced the same issues as others.

1 Like
1595

Yeah, I tried logging in for the last two hours as well. Made it to character creation twice but kept getting “Character creation timed out”. Oh well, I hope to provide some good feedback when I do make it on.

1596

I only made it to Tanaris :frowning:

1 Like
1597

Tried for two hours and the furthest I got was the character creation screen which would not authenticate after trying for ~15 minutes. The rest of the time I either received no servers available or the realm list as locked or offline.

1 Like
1598

spent roughly more than an hour bouncing from log in q to character creation time out, another 30 min on character creation timing out over and over to the last bit staring at a server offline screen.

1 Like
1599

O sh*t son, can get to the server screen again. Still offline.

1 Like