How IBM HTTP Server reacts when the WebSphere Application Server plugin-cfg.xml is updated
 Technote (FAQ)
 
Question
After the plugin-cfg.xml is updated, when should the IBM® HTTP Server child process begin using the new plugin-cfg.xml?
 
Answer
The plug-in checks and uses the current configuration when it receives and starts working on a request. The same configuration is used until the requests have been served. When the plugin-cfg.xml is updated, the IBM HTTP Server plug-in will reload the new configuration at the RefreshInterval, which is defined in the plugin-cfg.xml. The plug-in configuration works within the process scope. That is to say, for a multi-threaded Web server like IBM HTTP Server 2.0.x, if one thread within a process detects that the plugin-cfg.xml has been modified and reloads it, the new configuration will be used by all the other threads for all the new requests.

However, for all the requests that are being processed by the plug-in, the old configuration is still used until the requests have been served. In other words, a plugin-cfg.xml reload will not affect the existing active requests.

Plug-in regeneration is a separate process that updates the plugin-cfg.xml and it does not affect how the plugin-cfg.xml gets reloaded by the Web server.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Plug-in
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1180460
IBM Group: Software Group
Modified date: Oct 19, 2007