This simple HttpSession inspector provides an estimate of the total size of the HTTP session and the size of each session attribute. These estimates are based on the amount of memory required to serialize each attribute, which gives a fair representation of the amount of effort required to replicate the session across a cluster. As a rule of thumb, the session size should not exceed 50 kB.
Some recommendations to keep the session size manageable:
Session id: MEUcy11l0uJvkk_mxL5fSEWw1x2kXbNuK3jSx7cm Session created: 2026-05-13 21:41:33.963 Total session size: 0 bytes (0 kB)
The estimated size in the table below is based on the amount of memory (in bytes) required to serialize both the name and the value of each attribute. The table is sorted by the size of the attributes, with the largest attributes shown first.
This tool also uses the Java Reflection API on the attributes to see whether they use collection or map classes. Attributes that do use collection or map objects are marked in red. Non-serializable attributes are also indicated: you should only store serializable objects in the session.
| Attribute name | Estimated size (bytes) | Class | Comments |
|---|
Executed in 2 ms on Wed May 13 21:41:33 CEST 2026 - Copyright (c) 2003 BEA Systems, Inc.