https://bz.apache.org/bugzilla/show_bug.cgi?id=66169
Bug ID: 66169
Summary: concurrent missed behavior
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: All
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Apache can handle up to 150 concurrent connections. is it possible to my app
logic work wrong for this?
for example: my app in one route check user's point then if user point is upper
than 100 do some stuff and make user point zero
if($user->point>100){
//some stuff take one second
$user->point=0;
}
s is it possible when doing stuff another request pass if statement?
UPDATE: i need more discuss on this question. i do an experiment on Apache
behavior:
$count=Count::find(1);
if($count->number<10){ //$count->number is 0 on database first;
sleep(10);
$count->number++;
$count->save;
}
then i send 100 request concurrent to Apache, i think as Apache handle requests
concurrent then $count->number can goes upper than 10 and reach 100
but it doesn't, why? and what happens if we have two servers with load balance?
still will work correct? please provide information. thanks
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
