Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: 72.14.204.196 is neither permitted nor
 denied by domain of rosenberg.leon@googlemail.com)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=googlemail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=rRbzkDUPim8d86mSXauebsaDLZAJ9GArfxzXwouwl6NWeEEY1RwoN7FqrJNSAea2ohVhyPb8/xoeWCmOZmZkqDPjHZowaYKDlL4HNgXgVl1ksor9wonC/QlBbuLxjaSjBkT2nzARn+DHV2A1cmq10HhgdboBynoLs+N7cY9jK1U=
Message-ID: <327858f40510060711u1e4cb238m77e7d66c9cabc808@mail.gmail.com>
Date: Thu, 6 Oct 2005 16:11:24 +0200
From: Leon Rosenberg <rosenberg.leon@googlemail.com>
Reply-To: Leon Rosenberg <rosenberg.leon@googlemail.com>
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: custom session manager
In-Reply-To: <0E071FA35418D811970500508BBB98190A5B0A@ganymed.allocation.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <0E071FA35418D811970500508BBB98190A5B0A@ganymed.allocation.net>

Sorry, aber how exactly does it solves the problem of having one
session per user? :-)


On 10/6/05, Tobias Meyer <tm@allocation.net> wrote:
> > -----Urspr=FCngliche Nachricht-----
> > Von: Leon Rosenberg [mailto:rosenberg.leon@googlemail.com]
> > Gesendet: Donnerstag, 6. Oktober 2005 11:20
> > An: Tomcat Users List
> > Betreff: Re: custom session manager
> >
> >
> > On 10/6/05, Tobias Meyer <tm@allocation.net> wrote:
> > >
> > > Or, cou could add a static hashmap to your Servlet (or a
> > bean if using JSPs)
> > > where you simply add the sessions with every request. You
> > would have to put
> > > an attribute implementing
> > javax.servlet.http.HttpSessionActivationListener
> > > in each session though, that removes the session from your
> > hashmap when the
> > > session is expired or you will end up with having many
> > invalid entries in
> > > your hashmap. (And I don't even know what happens if you
> > keep the references
> > > to those Session objects when they are recycled by tomcat)
> > > We do this to keep track of our sessions within the application.
> >
> > If you keep your sessions in a hashmap forever they will never be
> > freed by the garbage collector and you will end with an outofmemory
> > error one day.
>
> That's why I said you need one Attribute that implements the
> HttpSessionActivationListener, which, on second thought , was wrong - you
> need to implement HttpSessionBindingListener.
>
> The Method
>
> public void valueUnbound(HttpSessionBindingEvent event)
>
> will get called automatically when the session expires, and you can add c=
ode
> that removes the session from the hashmap.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org