> "Hassan Schroeder" <hassan.schroe...@gmail.com> wrote in message > news:4eedb92a0910012200v3ee194eay9fea204be71e4...@mail.gmail.com... > On Thu, Oct 1, 2009 at 6:38 PM, Eric B. <ebe...@hotmail.com> wrote: > > > I'm running Tomcat 6.0.18 and seeing something very bizarre. If I use > > HttpSession.setMaxInactiveInterval() in one session, and then in a > > different > > session, use HttpSession.getMaxInactiveInterval(), I get the value that > > I > > just set in the first session. > > > Am I seeing strange behaviour, or is this behaviour by design? > > I don't see that behavior in a quick test with > Tomcat 6.0.20, context running Servlet Spec 2.5 on > (Mac) Java(TM) SE Runtime Environment (build 1.6.0_15-b03-226) > Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-92, mixed mode > > Do you have a test case? Are you really sure you're getting those > data points from different sessions?
No, I don't have a test case for that at all. One of my developpers made modifications to our application in order to set the max inactive interval. I looked at his code changes, and they all _seem_ correct, so was very surprised to see that kind of behaviour. I ran some tests myself within our application and confirmed the behaviour he saw so was even more surprised. I didn't want to spend time building a test case and/or debugging Tomcat if this was designed behaviour. Now that you have confirmed otherwise, over the next few days, I'll make sure to do exactly that and see where/why our application is failing. I'll report back once I get more info. Thanks, Eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
