Caching Proxy may hang when the log file is full (UNIX)
 Technote (troubleshooting)
 
Problem(Abstract)
For Unix systems, Caching Proxy may stop processing requests and hang when the log file reaches 2 GB in size.
 
Resolving the problem

Caching Proxy is a 32-bit application and opens its log files with a 32-bit function. Because of this constraint, the log files should not exceed a size greater than 2 GB. Caching Proxy may hang, cease to process requests, if the log file exceeds 2 GB in size when Caching Proxy attempts to write to the log file when it is still actively processing requests.

The solution to this problem is to set the MaxLogFileSize directive in ibmproxy.conf to a value less than 2 GB. (The MaxLogFileSize directive of Caching Proxy, by default, is not set which allows a log file to grow to any size.)

The MaxLogFileSize directive specifies the maximum size of an individual log file. When a log file becomes full, the log file will close and a new log file of the same name appended by an incremental integer will be created for use by Caching Proxy.

The following is the syntax of the MaxLogFileSize directive:

MaxLogFileSize <size value> <size unit>

specify <size unit> as: B (bytes), K (kilobytes), M (megabytes), or G (gigabytes

For example:
MaxLogFileSize 128 M
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Edge Server Caching Proxy AIX, Linux, Solaris Edge Server 2.0 PTF1, Edge Server 2.0 PTF2
Application Servers Runtimes for Java Technology Java SDK
 
Historical Number
84660
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Edge Component
Operating system(s): Solaris
Software version: 5.0.1
Software edition:
Reference #: 1112822
IBM Group: Software Group
Modified date: Jun 19, 2003