웹서버가 답을 없을 때, mod_status를 보면 WWW가 엄청 납니다.

뭔가 파업중이란 이야기죠. =..=

이때 해당 웹서버는 apache가 떠 있어도 죽은거처럼 행동 합니다.

 

첨부는 W가 한개인데, 저게 20쯤 뜨면 apache 꼼짝 안해요.

 

   Scoreboard Key:
   "_" Waiting for Connection, "S" Starting up, "R" Reading Request,
   "W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup,
   "C" Closing connection, "L" Logging, "G" Gracefully finishing,
   "I" Idle cleanup of worker, "." Open slot with no current process

 

 

 

We have more information now, so we need to add a few more possibilities to our diagnosis
1. PHP Sessions may be locking: It appears that if you have an ajax site that makes multiple connections, and each connection sets a value for a session variable specific to that brower, each connection has to wait for the previous one to close before they start "writing" to the session. For example, say we set $_SESSION['last_connect_time'] = $timestamp; on scriptA.php and scriptB.php. If scriptA.php is called and runs for a very long time (image processing for example), if scriptB.php is called before scriptA.php finishes, it will be queued by PHP until scriptA.php finishes.

Wow, but there is a simple solution. Please put session_write_close(); when you are done writing all the session variables in every script. This will allow the session to be available to the next script even if the current script has finished executing.

So, with scriptA.php, put session_write_close(); close to the top of script before it starts image processing.

 

==

위에꺼로 조치가 안됨...

 

 

구글링...