OK,
ive got some more information here, I forgot that I updated my JK2
configuration file for httpd a little, I wonder if there's anything in
it that's wrong?
# Alternate file logger
[logger.file:0]
level=ERROR
file=${serverRoot}/logs/jk2.log
[workerEnv:]
info=Global server options
logger=logger.file:0
[config:]
file=${serverRoot}/conf/workers2.properties
debug=0
debugEnv=0
[shm:]
file=/etc/httpd/logs/jk2.shm
size=1048576
[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
port=8009
host=127.0.0.1
tomcatId=localhost:8009
[ajp13:localhost:8009]
channel=channel.socket:localhost:8009
[status:status]
[uri:/jkstatus/*]
[uri:/monster/*]
worker=ajp13:localhost:8009
Also, I noticed something. So there's currently 9 CLOSE_WAITs when I
run netstat. There are no webpages currently accessing the server, BUT,
if I then open a webpage, one of the CLOSE_WAITs disappear, and then if
I close the window, the CLOSE_WAIT reappears
What is going on??
S
Sam Seaver wrote:
Dear all,
Im running
Httpd 2.0.48
Tomcat 4.1.24
Connect by JK2 (unfortunately, I have no record of the version number)
on RH9
This set-up has worked really well, up till recently, where I found
that after a couple of visits to the JSP pages compiled by my tomcat
server caused a couple of CLOSE_WAIT connections to persist:
tcp1 0 127.0.0.1:42567 127.0.0.1:8009
CLOSE_WAIT
The JK2 connector is running at port 8009, and this is the connection
between a spawned httpd process and the JK2 connector, or so I believe.
I recently did a massive cut down on my server.xml file, (backing it
up of course) to all the essentials I thought I needed and nothing
more. So I'm posting it below:
Server port=8005 shutdown=SHUTDOWN debug=0
Service name=Monster
!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 --
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
port=8009 minProcessors=5 maxProcessors=75
enableLookups=true redirectPort=8443
acceptCount=10 debug=99 scheme=http
connectionTimeout=6000
useURIValidationHack=false
protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/
!-- Define the top level container in our container hierarchy --
Engine name=Standalone defaultHost=localhost debug=0
Valve className=org.apache.catalina.valves.RequestDumperValve/
!-- Global logger unless overridden at lower levels --
Logger className=org.apache.catalina.logger.FileLogger
prefix=catalina_log. suffix=.txt
timestamp=true verbosity=4/
Host name=monster.northwestern.edu debug=99
appBase=/home/monster/web unpackWARs=false
autoDeploy=false
Context path= docBase= debug=99 reloadable=false/
Valve className=org.apache.catalina.valves.AccessLogValve
directory=logs prefix=monster_access_log.
suffix=.txt
pattern=common resolveHosts=false/
/Host
/Engine
/Service
/Server
my website is not going to be used a lot, maybe more in July, but I
really need to make sure I can keep it running for months on end, and
there's no way its doing that, it keeps getting 'blocked' by these
CLOSE_WAITs im getting, any insight?
By the way, when I shut down Catalina, the CLOSE_WAITs persist, but
they go away if I restart httpd.
Cheers
Sam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
