What do you mean with sessionid disappears? From the url? Thats basic
tomcat, the first urls are with session id but if session cookie works
it wont append it to the url, or you really have to tell tomcat that
it has to do that everytime.
On 17/06/2009, Jeremy Levy jel...@gmail.com wrote:
We see
I have my apache log configured to include the cookies. I'm not talking
about the URL.
Jeremy
On Fri, Jun 19, 2009 at 2:51 AM, Johan Compagner jcompag...@gmail.comwrote:
What do you mean with sessionid disappears? From the url? Thats basic
tomcat, the first urls are with session id but if
We see a very similar issue: Between one request to another that happen
within a matter of seconds / minutes the sessionid disappears. A lot of our
traffic is mobile so I assume some of it is crappy browser implementation.
We have not been able to reproduce it any meaningful way.
We have been
if your servlet container loses the session there isnt much we can do
-igor
On Wed, Jun 17, 2009 at 2:55 PM, Jeremy Levyjel...@gmail.com wrote:
We see a very similar issue: Between one request to another that happen
within a matter of seconds / minutes the sessionid disappears. A lot of
I'm trying to track down the source of frequent PageExpiredExceptions that
we're getting on our deployment server. One of the errors occured at
01:28:06 this morning. In the Apache logs, I discovered that the user's
session ID spontaneously changed at that time, (see the change between lines
4 5
yes, a changing sessionid will cause a page expired error because the
client all of a sudden gets a new blank session.
changing session ids can be caused by either session expiration or a
manual session invalidation - like during a logout procedure.
you have to figure out what causes the session
I notice there are some secure requests there (https)... so I will now
blindly assume you are having the same problem I had in the past...
I had a problem with session ids changing when trying to swtich between
secure/insecure pages.
If your first request to a tomcat server is secure, and a
good catch Jason.
We have also ran into this when implementing wicket's @RequireHttps
annotation, there is a javadoc section in HttpsRequestCycleProtocol
that talks about this cookie pain.
-igor
On Thu, Jun 11, 2009 at 1:03 PM, Jason Leaja...@kumachan.net.nz wrote:
I notice there are some
Thanks for pointing that out. I've tried some other changes, so I'll wait
and see how they work out. However, if the problem persists I'll look into
the possibility of it being an HTTPS-related issue. That line of reasoning
hadn't ever occurred to me.
Dane
On Thu, Jun 11, 2009 at 1:09 PM, Igor
