Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 35901]  -
    jk 1.2.14 - Worker stop action does not hold
Message-Id: <20050808152105.0A65BE0@ajax.apache.org>
Date: Mon,  8 Aug 2005 17:21:05 +0200 (CEST)

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


chuck.sumpter@lmco.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |


------- Additional Comments From chuck.sumpter@lmco.com  2005-08-08 17:21 -------
(In reply to comment #8)
> This works although it might give some problems with already
> opened browsers and hitting 'refresh'.
> 
> If you open a new browser instance the values will be shown correctly.
> Even for the existing browsers the correct values will be shown after
> 60 seconds, and that depends on the browser itself an how it deals with
> 'Pragma: no-cache' header.
> 
> I see this as irrelevant for any 'normal' usage of the lb manager.
> 

A Browser refresh retained the settings after the use of the Disabled check box
and the Update Worker button.  

"values will be shown correctly".  Do you mean by this, that the
workers.properties will be read and those values displayed.  If this is true,
then the update worker dynamically is pretty worthless. 

"'Pragma: no-cache' header" The application I support uses this header. We've
never had any problems with it. 

"I see this as irrelevant for any 'normal' usage of the lb manager." One has to
wonder what you call 'normal'?  

Let me frame my response from the perspective of someone moving from JK2 to
jk1.2.14.  We made heavy use of the Disabled flag in the workers2.properties to
shut off new sessions to a worker (jvmroute).  Under JK2, when this setting was
changed and the reset link used on the jkstatus page, the disabled setting was
retained until changed.  

My expectations for jk1.2.14 were that it would act in a similar manner.  If
that was a bad assumption, then what does dynamic configuration mean.  I've read
every scrap of doc I can find on this topic.  If I missed something, please
point me to where this is discussed.

-- 
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org