Best Practice:  Removing stateful session beans when finished using

Technote (FAQ)
Problem
Solution
When an Enterprise Java Bean™ (EJB™) client no longer needs a stateful session bean, the client explicitly removes it from the container. By doing so, applications can decrease the need for passivation, minimize container overhead, and provide an increased level of performance.

If stateful session beans are not explicitly removed, resources are consumed by the container that manages many stateful session beans.

Related information
Best Practice: Removing Stateful Session Beans When Fi












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, EJB Container
Operating system(s): Multi-Platform
Software version: 3.0.2, 3.0.2.1, 3.0.2.2, 3.0.2.3, 3.0.2.4, 3.5, 4.0
Software edition: Edition Independent
Reference #: 1053986
IBM Group: Software Group
Modified date: 2004-08-30