중형서버에서 톰캣 8개를 띄워놓고, 제대로 동작되는지 확인하고 싶었다.
mod_jk.conf 에서 debug 레벨을 debug로 수정하고, 아파치 restart 하였다.
그리고, 로그를 확인한다. 워커가 정상적으로 선택되는지 알 수 있당~
tail -f mod_jk.log | grep "found best worker"
[Thu Apr 17 17:17:28 2008] [15701:9920] [debug] get_most_suitable_worker::jk_lb_worker.c (600): found best worker tomcat8010 (tomcat8010) using method 'Request'
[Thu Apr 17 17:17:30 2008] [15701:9920] [debug] get_most_suitable_worker::jk_lb_worker.c (600): found best worker tomcat8011 (tomcat8011) using method 'Request'
[Thu Apr 17 17:17:30 2008] [15700:9920] [debug] get_most_suitable_worker::jk_lb_worker.c (600): found best worker tomcat8012 (tomcat8012) using method 'Request'
[Thu Apr 17 17:17:30 2008] [15702:9920] [debug] get_most_suitable_worker::jk_lb_worker.c (600): found best worker tomcat8013 (tomcat8013) using method 'Request'
[Thu Apr 17 17:17:31 2008] [15702:9920] [debug] get_most_suitable_worker::jk_lb_worker.c (600): found best worker tomcat8014 (tomcat8014) using method 'Request'
[Thu Apr 17 17:17:31 2008] [15700:9920] [debug] get_most_suitable_worker::jk_lb_worker.c (600): found best worker tomcat8015 (tomcat8015) using method 'Request'
[Thu Apr 17 17:17:33 2008] [15700:9920] [debug] get_most_suitable_worker::jk_lb_worker.c (600): found best worker tomcat8016 (tomcat8016) using method 'Request'
[Thu Apr 17 17:17:33 2008] [15704:9920] [debug] get_most_suitable_worker::jk_lb_worker.c (600): found best worker tomcat8014 (tomcat8014) using method 'Request'
[Thu Apr 17 17:17:33 2008] [15702:9920] [debug] get_most_suitable_worker::jk_lb_worker.c (600): found best worker tomcat8015 (tomcat8015) using method 'Request'
[Thu Apr 17 17:17:33 2008] [15702:9920] [debug] get_
'web' 카테고리의 다른 글
| 웹에서 Dos 공격 막아보기.. (0) | 2008.04.22 |
|---|---|
| Connection reset by peer, Connection reset, Broken Pipe 이런 에러. (0) | 2008.04.19 |
| Webwork(스트러츠2)에서의 Value stack 개념 (0) | 2008.04.05 |
| Webwork(스트러츠 2) ActionContext 사용하기 (0) | 2008.04.05 |
| webwork(스트러츠2)에서의 chain과 redirect (type) 사용하기 (0) | 2008.04.05 |
