Servlets : HttpSessionListener Demo

Master Core Java & Servlets!

Subscribe to Ram N Java for beginner-friendly coding walkthroughs, session management tutorials, and hands-on Java guides!

🔔 Subscribe to Ram N Java

Hands-On with HttpSessionListener

In Java web applications, managing session state and observing lifecycle transitions is vital for security, auditing, and user analytics. The HttpSessionListener interface allows your application to intercept and respond to session creation and destruction events in real time.

Whenever a user initiates a request that starts a new session (e.g., calling request.getSession()), or when a session is explicitly invalidated or times out due to inactivity, the servlet container notifies all registered listeners. This hands-on tutorial demonstrates how to implement and test this listener in an Apache Tomcat environment.

Implementing the Lifecycle Callback Methods

To create an active session listener, implement the HttpSessionListener interface and annotate the class with @WebListener (or configure it inside web.xml):

• sessionCreated(HttpSessionEvent se): Executes when a new session instance is created. You can retrieve session attributes, print session IDs, or increment total session metrics.
• sessionDestroyed(HttpSessionEvent se): Executes when session.invalidate() is called or when the session reaches its max inactive interval timeout.

@WebListener
public class SessionLifecycleDemoListener implements HttpSessionListener {

    @Override
    public void sessionCreated(HttpSessionEvent se) {
        HttpSession session = se.getSession();
        System.out.println("Session Created: " + session.getId());
    }

    @Override
    public void sessionDestroyed(HttpSessionEvent se) {
        HttpSession session = se.getSession();
        System.out.println("Session Destroyed: " + session.getId());
    }
}

Key Takeaways & Practical Use Cases

• Automatic Invocation: No need to invoke listener methods manually; the servlet engine triggers them across the entire application automatically.
• Clean Decoupling: Session logging and lifecycle operations remain decoupled from individual business servlets.
• Session Timeout Handling: Allows applications to run custom cleanup logic even when users do not click an explicit "Logout" button.

Recommended Related Tutorials

Continue exploring servlet listeners and session handling with these tutorials from Ram N Java:

• Servlets Tutorial: Introduction to HttpSessionListener | Servlets
• HttpSession Listener Demo: Counting Logged-in Users in Servlets | Servlets
• Servlets Tutorial: HttpSessionAttributeListener Demo | Servlets