I do not get the same value back, and our app does not use jsessionid currently. If I install the pages on a server that works properly, I get the same value back between page views. On this server, I get different values, which is consistent with losing session. There is no proxy in the way (all intranet) (that I know of; I'm not a network engineer but I play one at work, and so I believe that the parallel discussion about proxy servers does not pertain to my issue) (possible that WinXP installs some sort of proxy server software like internet connection sharing or something like that??)
To add weirdness to the issue, yesterday, the little two page app worked properly if installed in the Tomcat examples directory on the misbehaving server; today it does not. I had modified the server.xml file, and tried to change it back (from memory; I didn't make a big change) but failed to resolve the problem. I will do yet another clean install and trace my steps carefully. Thanks for everyone's help. Andrew > -----Original Message----- > From: Justin Ruthenbeck [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 05, 2003 5:25 PM > To: Tomcat Users List > Subject: Re: Tomcat 4 losing session (may be related to Win XP) > > > Are the sessions the same between the two calls? That is, > when you call > HttpSession#getId() for each of them do you get the same id back? > > justin > > At 02:27 PM 11/5/2003, you wrote: > >Hi all, > > > >I've come across a situation I can't figure out and I'm > wondering if it > >has to do with the fact that this is the first time we've installed > >Tomcat on Windows XP Prof. > > > >Symptom: Tomcat loses session. If you set up a very simple two JSP > >process where page 1 stuffs (setAttribute) something into > the session, > >and page 2 displays it, the value comes back as null > > > >Tests: if I copy the two JSPs to the examples directory > included in the > >Tomcat distribution, the pages perform properly. If I create my own > >context and execute the pages from there, the getAttribute > returns null. > > > >I created the context by duplicating the context in the > server.xml file > >and pretty much just changing the codebase. > > > >Other environment info: running behind Apache2 (latest), on port 8082 > >(http) and 8009 (AJP13) because Oracle Servlet Engine shows > up on port > >8080 (side note: anyone have info on how to get the flying pig to go > >away when you've uninstalled the Oracle HTTP server???); JDK > 1.4.*, and > >this is Tomcat 4 (latest). > > > >The exact same set up works fine on Windows 2003 and Windows > 2000 Prof. > >And this machine works fine as a client to the server running on any > >other machine, so it's not a cookie issue I don't think. > > > >Am I missing something obvious? Could it be permission-related? > >Something in the way the session data is stored on disk? Sure would > >appreciate any advice. > > > >Andrew Longley > >Senior Software Developer > >MindFlow Technologies, Inc. > >http://www.mindflow.com > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > ____________________________________ > Justin Ruthenbeck > Software Engineer, NextEngine Inc. > justinr - AT - nextengine DOT com > Confidential. See: > http://www.nextengine.com/confidentiality.php > ____________________________________ > > > --------------------------------------------------------------------- > 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]
