Log in

No account? Create an account
LiveJournal Client Discussions [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

unexpected server behavior... [Jan. 28th, 2003|10:07 pm]
LiveJournal Client Discussions


I've been working on getting my livejournal client to be more resilliant to errors and such, and this error has been coming up recently. (I even got this from the web-based LJ update thingy, and it had the same result.)
HTTP/1.1 200 OK
Date: Wed, 29 Jan 2003 03:05:06 GMT
Server: Apache
Content-length: 74
Content-Type: text/plain
X-Cache: MISS from www.livejournal.com
Connection: close

Server error: Error obtaining necessary database lock
The thing that's really strange about this one is that it posts the message anyway. Even though the success response is FAIL, the post is still accepted into the database.

Is there some addendum to the protocol docs that I seem to have missed about the true meaning of "FAIL"?

And what's up with the "X-Cache" line... just curious on that one...


From: ex_wantedma
2003-01-28 08:14 pm (UTC)


I have seen this error a lot on vision, where it says the update was incomplete, but my livejournal was still updated....I believe it has something to do with how overloaded the lj serves have become.

I think what is happening, is that the database cannot get a lock on that user's database table,(that table is being used by another client) but decides to update the database anyways...(there is an admin setting in MYSQL, I believe, that allows you to set that as default)

So the error is more of a "check you post, it may be garbage / incomplete", because there isn't a guarenteed that your update happened correctly.

heh, I got nothing
(Reply) (Thread)
[User Picture]From: benzado
2003-01-28 09:36 pm (UTC)

Re: humm...

I want a guarantee that if postevent returns FAIL, then the event was not posted. I would consider this a bug on the server.

Let me know if you (jerronimo) don't want to submit this as a bug (http://zilla.livejournal.org/), because if not I will. I just haven't run into that problem myself before.
(Reply) (Parent) (Thread)
[User Picture]From: jerronimo
2003-01-28 09:51 pm (UTC)

Re: humm...

well, i don't have an account with 'zilla, so if you can do it, that would be great. :)
(Reply) (Parent) (Thread)
[User Picture]From: benzado
2003-01-28 11:17 pm (UTC)

Re: humm...

I need an account? D'oh!

Well, if I can get one and submit the bug, I will, but not now, because I'm trying to write an all important application essay and I want it finished before the sun comes up.

If you get an account and submit it before I do, I won't complain. :-)
(Reply) (Parent) (Thread)
[User Picture]From: simonb
2003-01-29 03:07 am (UTC)

Re: humm...

Oh ick - I never knew that mysql would allow you to do something as broken as that. IHMO this is another reason not to use mysql for anything which requires a real RDBMS.

(okay, so I've been spoiled by playing with large sybase and oracle RDBMSs :)
(Reply) (Parent) (Thread)