Hi, Oh, this reminds me to have a vote on the stability of 5.0.25! You never answered the key question of whether your session attributes are Serializable or not: that's a binary question, should be easy to determine ;)
Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Ben Souther [mailto:[EMAIL PROTECTED] >Sent: Friday, May 21, 2004 7:24 AM >To: Tomcat Users List >Subject: Re: session data in Tomcat 5 > >Mike, >If you have a small, reproducable test case, send it up. I'd like to take >a >look at it. > > >On Friday 21 May 2004 01:10 am, you wrote: >> Jacob Kjome wrote: >> > I didn't see the earlier posts, but are you using Tomcat-5.0.24? >> > There's a bug related to session cookies which requires a hotfix. >> > However, I'd just install 5.0.25 which has the fix, plus a few >> > others. Also note that Tomcat-5.0.24+ is very strict about objects in >> > the session being serializable (where 5.0.19 was less so). Upon >> > application shutdown, non-serializable attributes will be removed so >> > that upon restart, the non-serializable attributes won't exist in the >> > session. Not sure if that is your problem here, but it's a good thing >> > to note. >> > >> > http://archive.apache.org/dist/jakarta/tomcat-5/v5.0.25-alpha/ >> > >> > Jake >> >> Well, yes and no. That is, on the remote server it is 5.0.19 but >> locally on my laptop (Win2K) and on a Linux box (FC1) I downloaded and >> installed 5.0.24. I wrote a pair of simple test jsp's and the version >> on the Win2K machine certainly has problems as the session is different >> on every submit. The remote server and the Linux box seem better. >> After reading your note I uninstalled the 5.0.24 version then downloaded >> and installed the 5.0.25-alpha version (the alpha part scared me which >> is why I went with the 5.0.24 before). Interestingly enough it also >> seems to exhibit the same behaviour (new session on every submit). I >> guess this means that all the straining and heaving to get things to >> work on a local Tomcat 5 server before deploying them remotely was a >> wasted day. >> >> For those interested, my test consisted of two simple jsp's like the >> following one. This is second.jsp the other being first.jsp. In the >> other jsp test is test2 and test2 is test. >> >> <%@ page language="java" contentType="text/html; charset=UTF-8" >> pageEncoding="UTF-8" %> >> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> >> <HTML> >> <HEAD> >> <TITLE>second.jsp</TITLE> >> </HEAD> >> <BODY> >> <P><font color="blue">Second</font></P> >> <p>Session ID=<%=session.getId()%></p> >> <br>test = <%=session.getAttribute("test")%> >> <br>test2 = <%=session.getAttribute("test2")%> >> <br> >> <form method="post" action="first.jsp" > >> <input type="submit"/> >> </form> >> <% >> session.setAttribute("test","test"); >> %> >> <br>test confirm = <%=session.getAttribute("test")%> >> </BODY> >> </HTML> >> >> For the most part I'm only concerned with session stuff while a user is >> busy editing -- it doesn't have to survive stop/start at all. My >> "feeling" right now (FWIF) after repeated deploy/undeploy on the three >> installs of Tomcat is that Tomcat 5 is certainly is not as solidly >> stable as Tomcat 4.1. >> >> Mike >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
