Sun Microsystems Sun Java System Web Server 7.0, Manual

Page: 64 / 132

...
</Object>
<Object name=
"
myname
"
>
Service method=(GET|HEAD) type=*~magnus-internal/* fn=send-file
nocache=
""
</Object>
In the above example, the server does not cache static files from
/export/mydir/
when
requested by the URL prefix
/myurl
. For more information on editing
obj.conf
, see Sun Java
System Web Server 7.0 Update 1 Administrator’s Configuration File Reference .
File Cache Dynamic Control and Monitoring
You can add an object to
obj.conf
to dynamically monitor and control the file cache while the
server is running.
▼
To Control and Monitor the File Cache
Add a
NameTrans
directive to the default object:
NameTrans fn=
"
assign-name
"
from=
"
/nsfc
"
name=
"
nsfc
"
Add an
nsfc
object definition:
<Object name=
"
nsfc
"
>
Service fn=
"
service-nsfc-dump
"
</Object>
This enables the file cache control and monitoring function (
nsfc-dump
) to be accessed through
the URI
/nfsc
. To use a different URI, change the
from
parameter in the
NameTrans
directive.
The following is an example of the information you receive when you access the URI:
Sun Java System File Cache Status (pid 3602)
The file cache is enabled.
Cache resource utilization
Number of cached file entries = 174968 (152 bytes each, 26595136 total bytes)
Heap space used for cache = 1882632616/1882632760 bytes
Mapped memory used for medium file contents = 0/1 bytes
Number of cache lookup hits = 47615653/48089040 ( 99.02 %)
Number of hits/misses on cached file info = 23720344/324195
Number of hits/misses on cached file content = 16247503/174985
Number of outdated cache entries deleted = 0
Number of cache entry replacements = 0
Total number of cache entries deleted = 0
Parameter settings
1
2
Using Monitoring Data to Tune Your Server
Sun Java System Web Server 7.0 Update 1 Performance Tuning, Sizing, and Scaling Guide • 64