Firefox will share sessions between the tabs so i'm surprised this works
at all.
-Original Message-
From: Quinton Delpeche [mailto:[EMAIL PROTECTED]
Sent: 25 November 2004 11:44
To: [EMAIL PROTECTED]
Subject: Tomcat Sessions...
Hi,
I have a friend who has a question for the list.
> On
Howdy,
>Currently it seems that sessions are serialised and kept through
restarts
>of Tomcat. Is there any way to prevent this so that all sessions are
wiped
>when Tomcat is restarted.
>
>And even better would be to wipe them on a context basis, when a
context is
>reloaded.
Yes to both:
http://j
Morning
>
> Nope, Tomcat 4.1.x will hang onto the sessions. And the even worse news is
> that Tomcat 3.3.2-dev will now hang onto the sessions across a
> context-reload :).
This is not the behaviour I see.Sessions are invalidated after an "ant
reload" on tomcat 4.1.12-LE on a semislackware insta
"Baker, Derek" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hello,
> Tomcat 4.1.12, running with JBoss 3.0.4 on RedHat 8.0, seems to be holding
> onto sessions between deployments of a webapp. With the old version
> (3.something) the sessions would get killed
Hi,
I'll wager that you've cached your session object between requests and
the HttpSessionFacade object
has been 'recycled'.
I got horribly burned by this in some code I wrote - I was caching the
session object in the ServletContext (naughty)
and, if the session object was non-null, I tried to fe
Here is the trace:
java.lang.NullPointerException
at org.apache.tomcat.facade.HttpSessionFacade.getValue(Compiled
Code)
at org.apache.tomcat.facade.HttpSessionFacade.getValue(Compiled
Code)
at SessionTrack.run(Compiled
Code)
at java.lang.Thread.run(Compiled
Code)
I
Yes, i was using HttpServletRequest.getSession()
function call
inside getSession( req )
function, It's working fine with Servlet runner but not with tomcat
as i said ...
William Kaufman wrote:
Is
there any difference in : Jsdk2.0 HttpSession Object & the above
one
org.apache.tomcat.faca
Is there any difference in : Jsdk2.0 HttpSession Object & the
above one
org.apache.tomcat.facade.HttpSessionFacade IS an
HttpSession.
So whenever we try to access the current session object, it
seems that we get NULL object in Tomcat.
I don't know what getSession(HttpServ
D]>
list-post: <mailto:[EMAIL PROTECTED]>
Delivered-To: mailing list [EMAIL PROTECTED]
From: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Thu, 22 Feb 2001 17:37:35 +0100
Subject: RE: Tomcat - Sessions and WAP Browsers
Priority: Normal
X-mailer: Phoenix Mail 0.92.08 Standard Edition
MIM
Hi!,
Actually, WAP protocol does not support cookies (at least the version I
worked on).
You have to deal with URL Rewriting, in order to include the session ID
into the requested URL. Once there, tomcat automatically reads the session
ID from the URL instead of using the cookie. This is the sa
10 matches
Mail list logo