Oracle HTTP Server WL Proxy WLTempDir Parameter Location For _wl_proxy Is Not Taking Effect
(Doc ID 2457704.1)
Last updated on MARCH 04, 2019
Applies to:Oracle HTTP Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Depending upon the Oracle HTTP Server installation footprint, a large I/O chatter may be seen concentrated at /tmp.
Seen when setting the alternate location for /tmp/_wl_proxy with WLTempDir.
The _wl_proxy is not being written to the location specified by WLTempDir.
The WLTempDir is used for setting the location of POST data files (_wl_proxy).
By default Oracle HTTP Server concentrates it's POST data file location at /tmp in a folder named _wl_proxy that is written there. In a larger installation footprint where there are many OHS components and lots of POST data being transmitted, there can be sizable I/O chatter on this mount point.
When changes are made to specify a new WLTempDir location for where the _wl_proxy will be placed, it is observed that upon restarting OHS, that it is not directed from /tmp to the location specified at WLTempDir.
It is expected that the former location default (/tmp/_wl_proxy), would be changed to store _wl_proxy at the new alternate location specified by WLTempDir, but it is not, even after restarting Oracle HTTP Server and confirming it's presence in mod_wl_ohs.conf
The issue can be reproduced at will with the following steps:
- Update mod_wl_ohs.conf to include "WLTempDir /my/new/path".
- Restart OHS component.
- Observe path specified by WLTempDir. No _wl_proxy folder may be seen written at the location specified by WLTempDir.
Simply specifying an alternate location for "_wl_proxy" with WLTempDir used for storing POST data files.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document