Over a million developers have joined DZone.

Hooking Up HTTPSessionListener with Tomcat

DZone's Guide to

Hooking Up HTTPSessionListener with Tomcat

· Integration Zone ·
Free Resource

SnapLogic is the leading self-service enterprise-grade integration platform. Download the 2018 GartnerMagic Quadrant for Enterprise iPaaS or play around on the platform, risk free, for 30 days.

We have got a use case in project where we need to identify the time when Tomcat expires any user’s session. Basically we need to flush some persisted values of that user from DB.

For that i have hooked up sessionListener at application load(web.xml).



In web.xml file we are telling the server that it should intimate that class at the time of session creation and invalidation.
Server will automatically calls methods of this class if session of any user expires or developer himself invalidates any session.


package com.vdi.servlet;
import javax.servlet.http.HttpSessionEvent;
import javax.servlet.http.HttpSessionListener;
 * @author Javapitshop
public class SessionListener implements HttpSessionListener {
    public void sessionCreated( HttpSessionEvent arg0 ) {
    public void sessionDestroyed( HttpSessionEvent sessionEvent ) {

In above code we simply have to implement HttpSessionListener interface and override its methods. Methods are self descriptive so you can provide your implementation in any or both cases depending upon your usecase.

Below is my implementation how i have provided implementation of one of those overridden methods.

public void sessionDestroyed( HttpSessionEvent sessionEvent ) {
        synchronized ( this ) {
            HttpSession session = sessionEvent.getSession();
            if ( session != null ) {
                UserSessions sessions = userDao.getUserSession( session.getId() );
                if ( sessions != null ) {
                    userDao.deleteUserSessionByUserId( sessions.getUserId() );
                    UtilityLogger.logInfo( "UserSession Released from an expired login of User : " + sessions.getUserId() );

The major part of above provided implementation is persisted session id. Well as server is intimating application(SessionListener.java) on session invalidation so that means i couldn’t access anything saved in session as it is invalidated by server or user has called invalidate function himself. So for that we need to persist every user’s session id in DB and remove it from DB whenever its session expires or invalidates.

With SnapLogic’s integration platform you can save millions of dollars, increase integrator productivity by 5X, and reduce integration time to value by 90%. Sign up for our risk-free 30-day trial!


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}