You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/07/15 07:58:43 UTC
DO NOT REPLY [Bug 21600] New: - 's lost after manager stop/start or reload

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21600

<Parameter>'s lost after manager stop/start or reload

           Summary: <Parameter>'s lost after manager stop/start or reload
           Product: Tomcat 5
           Version: 5.0.4
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: hoju@visi.com


I believe this was true with Tomcat-4.1.xx, but I'm posting this as a 5.x.x bug
since I doubt the behavior will be changed for 4.x.xx...

If one sets <Parameter> elements in a context configuration file (ccf), they
will be read upon webapp startup, but as soon as one stops/starts or reloads the
webapp via the Tomcat manager app, the prevously configured <Parameter>'s are
not taken into account.

For example, I have the following in my ccf...

<Parameter name="log4j-log-home" value="C:\" override="true"/>
<Parameter name="log4j-sysprop-name" value="MyWebapp.log.home" override="true"/>

Upon first startup, my webapp obtains this configuration information and reports...

Setting system property [ MyWebapp.log.home ] to [ C:\ ]


when I reload the webapp via the Tomcat manager app, I get the following...

No System property name provided. Please set the "log4j-sysprop-name" context
parameter.


I imagine this issue also applies to setting <Environment> and other elements
supported by ccf's as well.

Is this expected behavior?  I can't imagine it is.  I sure didn't expect it and
it makes it difficult to configure webapps and trust that they will continue to
stay configured througout the entirety of their deployment whether they are
reloaded or not.

Jake

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