Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: 28 Oct 2004 14:17:07 -0000
Message-ID: <20041028141707.20915.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 31938] New:  -
    Apache2 + mod_jk2 on FreeBSD - default socket timeout

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31938>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31938

Apache2 + mod_jk2 on FreeBSD - default socket timeout

           Summary: Apache2 + mod_jk2 on FreeBSD - default socket timeout
           Product: Tomcat 5
           Version: 5.0.0
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Native:JK
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: mdxyz@gmx.de


I've got a problem with mod_jk2 and Apache2 under FreeBSD 5.x. I configured
mod_jk2 for two Tomcat 5.0 servers. If one of these machines is down (unplugging
the network cable), mod_jk2 should send all requests to the server that kept
running. That is working 80 percent of the time, but sometimes forwarding the
request takes about 75 seconds. I found out that this is the default socket
timeout of FreeBSD. The problem is that I configured mod-jk2 the way, that it
has its own timeout for connecting (see attached workers2.properties). But this
value is not recognized. If I decrease the default connect timeout for FreeBSD
(by /etc/sysctl.conf),
mod_jk2 will use this value and everything is fine. But I don't want to decrease
that value, it could cause other problems.
So I think it is a bug, that mod_jk2 is not using the timeout values from its
workers2.properties in FreeBSD.
Btw exactly the same setup for Apache2 and mod_jk2 works fine on Linux.

------------------------------

[logger]
level=DEBUG

[shm]
file=/tmp/shmFile

# Defines a load balancer named lb. 
[lb:lb]

[workerEnv:]
info=Global server options
timing=1

# Example socket channel, override port and host.
[channel.socket:192.168.1.124:8009]
tomcatId=camenzind
timeout=1

# Example socket channel, override port and host.
[channel.socket:192.168.1.123:8009]
tomcatId=haller
timeout=1

# define the worker 1
[ajp13:192.168.1.124:8009]
channel=channel.socket:192.168.1.124:8009

# define the worker 2
[ajp13:192.168.1.123:8009]
channel=channel.socket:192.168.1.123:8009

# Mapping my URI to Tomcats
[uri:/myURI*]
group=lb

[status:]
info=Status worker, displays runtime information

[uri:/jkstatus/*]
info=The Tomcat /jkstatus handler
group=status:

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org