Server User Manual
Table Of Contents
- Sun GlassFish Enterprise Server 2.1 Performance Tuning Guide
- Preface
- Overview of Enterprise Server Performance Tuning
- Tuning Your Application
- Java Programming Guidelines
- Java Server Page and Servlet Tuning
- EJB Performance Tuning
- Goals
- Monitoring EJB Components
- General Guidelines
- Using Local and Remote Interfaces
- Improving Performance of EJB Transactions
- Use Container-Managed Transactions
- Don’t Encompass User Input Time
- Identify Non-Transactional Methods
- Use TX_REQUIRED for Long Transaction Chains
- Use Lowest Cost Database Locking
- Use XA-Capable Data Sources Only When Needed
- Configure JDBC Resources as One-Phase Commit Resources
- Use the Least Expensive Transaction Attribute
- Using Special Techniques
- Tuning Tips for Specific Types of EJB Components
- JDBC and Database Access
- Tuning Message-Driven Beans
- Tuning the Enterprise Server
- Deployment Settings
- Logger Settings
- Web Container Settings
- EJB Container Settings
- Java Message Service Settings
- Transaction Service Settings
- HTTP Service Settings
- ORB Settings
- Thread Pool Settings
- Resources
- Tuning the Java Runtime System
- Tuning the Operating System and Platform
- Tuning for High-Availability
- Index

File Cache Information (le-cache)
The le cache caches static content so that the server handles requests for static content quickly.
The le-cache section provides statistics on how your le cache is being used.
For information on tuning the le cache, see
“HTTP File Cache” on page 67.
■
Number of Hits on Cached File Content
■
Number of Cache Entries
■
Number of Hits on Cached File Info
■
Heap Space Used for Cache
■
Number of Misses on Cached File Content
■
Cache Lookup Misses
■
Number of Misses on Cached File Content
■
Max Age of a Cache Entry: The maximum age displays the maximum age of a valid cache
entry.
■
Max Number of Cache Entries
■
Max Number of Open Entries
■
Is File Cached Enabled?: If the cache is disabled, the other statistics are not displayed. The
cache is enabled by default.
■
Maximum Memory Map to be Used for Cache
■
Memory Map Used for cache
■
Cache Lookup Hits
■
Open Cache Entries: The number of current cache entries and the maximum number of
cache entries are both displayed. A single cache entry represents a single URI. This is a
tunable setting.
■
Maximum Heap Space to be Used for Cache
Keep Alive (keep-alive)
The Admin Console provides the following performance-related keep-alive statistics:
■
Connections Terminated Due to ClientConnection Timed Out
■
Max Connection Allowed in Keep-alive
■
Number of Hits
■
Connections in Keep-alive Mode
■
Connections not Handed to Keep-alive Thread Due to too Many Persistent Connections
■
The Time in Seconds Before Idle Connections are Closed
■
Connections Closed Due to Max Keep-alive Being Exceeded
HTTP Service Settings
Chapter 3 • Tuning the Enterprise Server 63










