Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 40716]  - JK 1.2.19 on IIS6: Worker reference
 doesn't work
In-Reply-To: <bug-40716-78@http.issues.apache.org/bugzilla/>
Message-Id: <20061010155806.981E37142DC@brutus.apache.org>
Date: Tue, 10 Oct 2006 08:58:06 -0700 (PDT)

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=40716>.
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=40716


------- Additional Comments From jjohnson@livedatagroup.com  2006-10-10 08:58 -------
I agree that the reply_timeout below 1000 is aggressive but the connect_timeout
and prepost_timeout (ping/pong) below a second seems very reasonable. 
Especially when running a cluster that doesn't need sessions.  

If tomcat can't say that its alive in less than a second, something is probably
wrong with it.  IIRC we used to have this problem when our garbage collection
wasn't tuned well.

Regarding the reference problem, I almost reported a bug yesterday saying that
reference didn't work but I had forgot the "worker." prefix (which I see that
you tried).  As soon as I fixed that, my workers did indeed inherit the lbfactor
setting so I know it works at least for that in my case.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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