User Name: Password:
New User Registration
Moderator: Hrqls , coan.net , rod03801 
 BrainKing.com

Board for everybody who is interested in BrainKing itself, its structure, features and future.

If you experience connection or speed problems with BrainKing, please visit Host Tracker and check "BrainKing.com" accessibility from various sites around the world. It may answer whether an issue is caused by BrainKing itself or your local network (or ISP provider).

World Of Chess And Variants (videos from BrainKing): YouTube
Chess blog: LookIntoChess.com


Messages per page:
List of discussion boards
You are not allowed to post messages to this board. Minimum level of membership required for posting on this board is Brain Pawn.
Mode: Everyone can post
Search in posts:  

9. July 2003, 13:39:45
Fencer 
To make it clear - when a deadlock occurs, it simply means that one "thread" is consuming all CPU resources, most likely due to an infinite loop or similar problem. In such case, redirecting non-paying members to the Server Down page does not help. What I would like to implement is some reliable framework for "killing" such offending thread after it was consuming more than 90% of CPU resources for, say, one minute. This task is more related to Linux than Java and has almost nothing to do with the BrainKing.com application.

9. July 2003, 13:47:12
The Rat 
Subject: Re: deadlocks
Correct me if I'm wrong, but I seem to recall that you had two processors in your servers, and any java thread would run on only one of them... Is all of the processing done on one thread or does downtime only happen when two (or more) threads are maxed out?

Anyway, killing those threads after given time-out is probably not a good idea, as there might be other reasons for 100% cpu usage (like: a lot of users - killing the thread would only make things worse). Of course if that's all that can be done, then that's what must be done... :(

I'd really love to try and help you out, but:
a) I don't have the time
b) I don't know enought of your system
c) you seem quite competent your self :D

Thanks for the site anyway. Maybe some day I'll even pay something (for the record, the reason I'm not a paying member is that I don't like to pay on the net with anything except Nordeas "button payment" - and that's only implemented here in Finland, possibly in some other northern european countries too). :)

9. July 2003, 13:53:04
Fencer 
Subject: Re: deadlocks
Nope, only one of them. But thanks to the second processor I am able to handle the deadlock without hard restart of the whole server - which could take up to one hour.
There are no other reasons for 100% CPU usage. I've been monitoring it each day during several months and I know where the problem lies. But, of course, killing threads is only one possibility that can be tried, there are more options, I simply cannot test them all at once :-) You know, this site is not my full-time job.

Date and time
Friends online
Favourite boards
Fellowships
Tip of the day
Copyright © 2002 - 2024 Filip Rachunek, all rights reserved.
Back to the top