[Update: Trouble is gone - sorry for the downtime!]Looks like something went wrong. You may have trouble accessing your games. We are looking into it but might need a while to activate the right people on a Friday night. Really sorry for the interruption!
About this blog
This blog features news and updates for Weewar.com, the online multiplayer strategy game.
Recent Comments
19 Comments
i’ll be patiently hitting command-R all day :)
good luck fixing it!
Seriously – how does your app go from working great to not working great so quickly? Is the app that brittle or are you guys deploying code before testing it? Simply a curiosity to me, since things were going so good for weeks now – what gives?
Well, you *did* write this in Java, so I guess that is part of the problem.
;)
I am no coding genius but i think this is a pretty big database recording a s&#t-ton of events. i was amazed at the size of the transfer Alex and Bert did in December when they migrated to the new servers. I’m guessing the errors of the complexities of dealing with such large amounts of data.
I would be curious to hear more about what happened too.
I’d just like these blog posts to have a time associated with them, too.
It might be interesting, for those of us that are developers, to understand what happened – just for the sake of learning something and satisfying our curiosity!
Cause and effect ??
things were working fine – the tournament started – things are not working fine
hmm… that is suspicious Plato… hopefully it was just bad luck though…
BTW, is the post-down time effect kind of going to be like when you guys are updating and all clocks are reset?
Good luck devs! Hope to see the game up and running again shortly.
I place my bets on an overflow of some sort. Too much old data? Filled up log files?
Being that weewar runs on a distributed architecture, I bet there was some sort of concurrency problem between the servers.
Can we put some type of a “time-hold” on ongoing games so opponents can’t use the downtime as an advantage to remove us for going over the limit?
We’re on it and have figured out what it was that caused weewar to break. It’s got to do with the update process and the way things are deployed to the live system. Some premature lines of code have somehow found a way out of the testing sandbox.
Will be resetting the round times once we are back so to not affect tournament and other games negatively (or more negatively as this downtime already has).
An ETA is difficult to give at this point but under the circumstance we have some hope to be back in about 30 minutes.
Time’s up! :-)
“Alex (weewar team) on 11 January, 2008 at 10:10 pm……….hope to be back in about 30 minutes.”
ok futureman! :) it’s currently 6:51pm, 11 Jan., 08, where i am – US east coast. so that means it won’t be back until 10:40pm tonight your time, but how does that relate to my time? ;)
ok.. we did not make the 30 minutes.. and it was not overly clever to not also post a time zone. But what I really meant is that we would be back just about now. Because we are ;)
Really sorry for the downtime. We’ll do some further monitoring to make sure things stay. Btw it is 1.16 am (GMT+1) over here.
I don’t think the trouble is gone yet. The following happens when I try to click on a community game:
An Error Occurred:
/splitChat.xhtml: /join.xhtml @104,66 value=”#{startGameBean.chatId}”: Error reading ‘chatId’ on type com.weewar.web.jsfbeans.StartGameJSFBean
same result here.
The three games that I think were started when there was that bug do not work and generate the error stated above. New games on the community page seem to work fine though.
Looks like spadequack’s assessment was correct. Those games had been started when the site was broken and were subsequently ill-formated. We have removed them now. The same might apply to invite only games you have started during the time. Let us know if it happened to one of your game and we’ll sort it out.