Am not usre to understand you. First you request to limit the number of
session, then you say you application is anyway already doing this?
When you close browser, the SessionId cookie is detroyed in the browser.
About 30 minutes later (in default tomcat installation) the Session
object stored in
quot;8080"
>>>> maxThreads="1" minSpareThreads="1" maxSpareThreads="1"
>>>> minProcessors="1"
>>>> maxProcessors="1" enableLookups="false" acceptCount="1" debug="0"
>>>> co
Connection has nothing to do with session. A session lives across
several connections to server. Are you trying to prevent 2 different
user from logging in at the same time? This is an application specific
issue and should be handled, probably using an HttpSessionListener. It's
not the tomcat's job
connectionTimeout="2" useURIValidationHack="false"/>
>>
>> Thanks for your help.
>>
>> Frank
>>
>>
>
>
> -
&
Can you describe with more details the "nothing will work" and your
intended behaviour. Explain how you tested configuration. According to
your configuration, the connector should work like this:
1) Serves exactly one request at a time (maxProcessors).
2) When another connection is attempted and y
:
http://www.nabble.com/Tomcat-limited-connection-to-only-1-tf3039025.html#a8446295
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail
