tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33465] New: - StandardSession.removeAttriube throws NullPointerException
Date Wed, 09 Feb 2005 13:26:48 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33465>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33465

           Summary: StandardSession.removeAttriube throws
                    NullPointerException
           Product: Tomcat 4
           Version: 4.1.30
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: andreas.schmidt@team-konzept.de


from time to time i find the following error messages in the log-files of my
production system:

java.lang.NullPointerException
	at
org.apache.catalina.session.StandardSession.removeAttribute(Ljava.lang.String;Z)V(StandardSession.java:1157)
	at
org.apache.catalina.session.StandardSession.removeAttribute(Ljava.lang.String;)V(StandardSession.java:1103)
	at
org.apache.catalina.session.StandardSessionFacade.removeAttribute(Ljava.lang.String;)V(StandardSessionFacade.java:201)
	at
org.apache.catalina.session.StandardSessionFacade.removeAttribute(Ljava.lang.String;)V(StandardSessionFacade.java:201)


unfortunatly i could never cause the error by myself, i just see it happen by
looking in the log-files. digging into the source-code of removeAttribute points
to these lines:

        // Notify interested application event listeners
        Context context = (Context) manager.getContainer();
        Object listeners[] = context.getApplicationListeners();

the null-pointer-exception is thrown in the line that calls
manager.getContainer(), so it seems manager is null, when it comes to the
exception. i don't know how manager can get null -- maybe i have some
miscounfiguration? so without understanding the details or the implementation, i
looked at the other methods that access manager. most of then check the
manager-variable for a null-value before they access it. so maybe this should be
done here too?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message