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 16680] New: - Internal Server Error on HttpSession.setAttribute()
Date Sun, 02 Feb 2003 21:35:15 GMT
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=16680>.
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=16680

Internal Server Error on HttpSession.setAttribute()

           Summary: Internal Server Error on HttpSession.setAttribute()
           Product: Tomcat 4
           Version: 4.1.18
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Servlet & JSP API
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: treeck@yahoo.com


4.1.18 of Tomact, HttpSession.setAttribute throws the Exception, 
java.io.NotSerializableException, and displays an "Internal Server Error" on 
the generated web page, when the saved session attribute is not serializeable.

In version 3 of Tomcat, it was not required that a saved attribute be 
serializable. Further, there are cases where the saved object may be very 
complex and difficult to serialize. While necessary for J2EE clustering, a 
session attribute being serializable should not be hard requirement for all 
cases -- or at least handled more gracefully and documented that this is a 
requirement.

-George

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