|
Problem |
After the plugin-cfg.xml is updated, when should the IBM®
HTTP Server child process begin using the new plugin-cfg.xml? |
|
Solution |
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
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 Web
server. |
|
|
|
|
|
|