DO NOT REPLY [Bug 4613] New: - Thread which extracts Session object obtained from HttpSessionBindingEvent & queries the session object hangs

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4613>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4613

Thread which extracts Session object obtained from HttpSessionBindingEvent & queries 
the session object hangs

           Summary: Thread which extracts Session object obtained from
                    HttpSessionBindingEvent & queries the session object
                    hangs
           Product: Tomcat 4
           Version: 4.0.1 Final
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Jasper
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Code example:
  public void valueUnbound(HttpSessionBindingEvent parm1) {
    HttpSession session = parm1.getSession();
    log.debug("SessionBindingListener::valueUnbound:Name:"+parm1.getName()
+" :Session"+session.getId());
    System.out.println("1");
    // THE FOLLOWING CALL HANGS AFTER THE FOLLOWING CALL *******
    User user = (User) session.getAttribute(PTLConstants.USER_KEY);
    // THE THREAD NEVER EXECUTES THE NEXT STATEMENT
    System.out.println("2");
    if (user == null) {
           System.out.println("3");
       // log him off anyway
       log.warn("Could not find User object in session"+session.getId());
       log.debug("user object was null");
       return;
    }
    System.out.println("4");
  }

Works OK! in Tomcat 3.2.3

I believe this is the same problem of the thread hanging in HttpSessionListener 
too on sessionDestroyed() method.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>