Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of kevan.miller@gmail.com
 designates 66.249.82.227 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type:mime-version:subject
         :date:references:x-mailer;
        b=fLMSbDap/N6sBCiYAiCIgFcWX/XF9sG7dpPbj6zHT/l6+84/IBx4SSMKwFfITUWkPJ
         LrSCknsIfYTtmDn1qo9MuvmAQLAFeu9Ee8sh3yJNzQTBLoIpmuQYWZGN1A4++NTVXk7q
         JdP0mWTelC+PIqJVMsDeV1ffnmi+NI4tFbjZU=
Message-Id: <2B281218-CFBB-47BA-8CAC-6A7152A1DD0C@gmail.com>
From: Kevan Miller <kevan.miller@gmail.com>
To: user@geronimo.apache.org
In-Reply-To: <19402329.post@talk.nabble.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-23-559649453
Mime-Version: 1.0 (Apple Message framework v926)
Subject: Re: Swap Sessions to disk
Date: Mon, 15 Sep 2008 22:35:01 -0400
References: <19402329.post@talk.nabble.com>


--Apple-Mail-23-559649453
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Sep 9, 2008, at 6:09 PM, Radim Kolar wrote:

>
> I have problem with session management. Currently G stores all  
> sessions in
> memory, so after memory is exhausted, G crashes.
>
> Its very easy to DOS Geronimo server that way (just run ab benchmark  
> tool
> from apache) and it takes just a few minutes. Also lot of bots don't  
> bother
> with sending session cookie back - they are eating valuable server  
> memory if
> session handling is enabled for JSP page.
>
> I propose to change tomcat session manager to manager with swap to  
> disk
> feaure. its called org.apache.catalina.session.PersistentManager and  
> it
> should be used by default and configured via portlet. Other  
> applications
> servers, like WAS, can limit number of open sessions and thus  
> increasing
> reliability.
>
> https://issues.apache.org/jira/browse/GERONIMO-3838

https://issues.apache.org/jira/browse/GERONIMO-3376 was intended to  
enable this support. A problem was fixed in 3376. However, I'm pretty  
sure the full function was not properly tested. Working properly, this  
would give you the ability to configure the maxActiveSessions for a  
StandardManager or configure a StandardManager.

Agreed that it would be nice to be able to configure these features  
via the Admin Console. I'm not sure that PersistentManager should be  
the default, however. I'd be happy to start with just being able to  
configure this, period.

Are you offering to help implement this? Your contributions would be  
most welcome!

--kevan


--Apple-Mail-23-559649453
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Sep 9, 2008, =
at 6:09 PM, Radim Kolar wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><br>I =
have problem with session management. Currently G stores all sessions =
in<br>memory, so after memory is exhausted, G crashes. <br><br>Its very =
easy to DOS Geronimo server that way (just run ab benchmark tool<br>from =
apache) and it takes just a few minutes. Also lot of bots don't =
bother<br>with sending session cookie back - they are eating valuable =
server memory if<br>session handling is enabled for JSP page.<br><br>I =
propose to change tomcat session manager to manager with swap to =
disk<br>feaure. its called org.apache.catalina.session.PersistentManager =
and it<br>should be used by default and configured via portlet. Other =
applications<br>servers, like WAS, can limit number of open sessions and =
thus increasing<br>reliability.<br><br><a =
href=3D"https://issues.apache.org/jira/browse/GERONIMO-3838">https://issue=
s.apache.org/jira/browse/GERONIMO-3838</a><br></div></blockquote><div><br>=
</div><div><a =
href=3D"https://issues.apache.org/jira/browse/GERONIMO-3376">https://issue=
s.apache.org/jira/browse/GERONIMO-3376</a> was intended to enable this =
support. A problem was fixed in 3376. However, I'm pretty sure the full =
function was not properly tested. Working properly, this would give you =
the ability to configure the maxActiveSessions for a StandardManager or =
configure a StandardManager.</div><div><br></div><div>Agreed that it =
would be nice to be able to configure these features via the Admin =
Console. I'm not sure that PersistentManager should be the default, =
however. I'd be happy to start with just being able to configure this, =
period.</div><div><br></div><div>Are you offering to help implement =
this? Your contributions would be =
most&nbsp;welcome!</div><div><br></div><div>--kevan</div></div><br></body>=
</html>=

--Apple-Mail-23-559649453--