sessionDestroyed works, but not sessionCreated

[Stephen Huey]

Any idea why my stdout.log in Tomcat would be recording print statements from sessionDestroyed but not sessionCreated?

 
public class OurSessionListener implements HttpSessionListener {
 

  public void sessionCreated(HttpSessionEvent se) {
 
    HttpSession session = se.getSession();
    UserAcctBean user = (UserAcctBean) session.getAttribute("currentuser");
    String loginID = user.getLoginID();
    System.out.println("Added session: " + session.getId() + " for user " + user.getLoginID());
    SystemControl.addActiveUser(session.getId(), user.getLoginID() );
  }
 
  public void sessionDestroyed(HttpSessionEvent se) {
    HttpSession session = se.getSession();
    SystemControl.removeActiveUser(session.getId());
    System.out.println("Removed session: " + session.getId());
  }
 
}

This has been frustrating me for a while. I thought it simply wasn't listening, but apparently it is since I do get statements beginning with "Removed session" in the log file!

[Sonny Gill]

Originally posted by Karelicek Huey:

UserAcctBean user = (UserAcctBean) session.getAttribute("currentuser");
String loginID = user.getLoginID();

Just a wild guess, but maybe currentuser attribute is not set yet,because the session has just been created.
So you are getting a null pointer exception when you call user.getLoginID.
You could try putting a try-catch block for NullPointer around that call, and see if this is the reason.

[Stephen Huey]

Thank you so much!

So simple...I remember that thought crossing my mind when I was first typing that line, but I totally forgot that later on. Details, details...
:roll:


Two thumbs up for you, man! Next one's on me.

[Sonny Gill]

No worries mate. As they say, two pairs of eyes are always better than one when hunting for bugs.
I was wondering though, whether it is a part of the specification that if an exception is thrown in one of these methods, the container must catch it and just continue.

cheers
Sonny