DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Redis-Based Tomcat Session Management
  • When Kubernetes Breaks Session Consistency: Using Cosmos DB and Redis Together
  • The Clandestine Culprits: Unmasking Modern Web Security Misconfigurations (And Their Automated Nemeses)
  • Cookies Revisited: A Networking Solution for Third-Party Cookies

Trending

  • Mocking Kafka for Local Spring Development
  • How You Clear Your HTML5 Canvas Matters
  • Agentic AI Has an Observability Blind Spot Nobody Is Talking About
  • Kafka and Spark Structured Streaming in Enterprise: The Patterns That Hold Up Under Pressure
  1. DZone
  2. Coding
  3. Languages
  4. Hooking Up HTTPSessionListener with Tomcat

Hooking Up HTTPSessionListener with Tomcat

By 
Shan Arshad user avatar
Shan Arshad
·
May. 09, 14 · Interview
Likes (0)
Comment
Save
Tweet
Share
14.6K Views

Join the DZone community and get the full member experience.

Join For Free

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).

Web.xml

<listener>
    <display-name>sessionListener</display-name>
    <listener-class>com.javapitshop.SessionListener</listener-class>
</listener>

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.

SessionListener.java

package com.vdi.servlet;
 
import javax.servlet.http.HttpSessionEvent;
import javax.servlet.http.HttpSessionListener;
 
/**
 * @author Javapitshop
 *
 */
public class SessionListener implements HttpSessionListener {
 
 
    @Override
    public void sessionCreated( HttpSessionEvent arg0 ) {
     
    }
 
    @Override
    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.

@Override
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.


Apache Tomcat Session (web analytics)

Published at DZone with permission of Shan Arshad. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Redis-Based Tomcat Session Management
  • When Kubernetes Breaks Session Consistency: Using Cosmos DB and Redis Together
  • The Clandestine Culprits: Unmasking Modern Web Security Misconfigurations (And Their Automated Nemeses)
  • Cookies Revisited: A Networking Solution for Third-Party Cookies

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook