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
normaly yes.
but by this application the connection can only handle one session with one
sessionid. but by the local installation the session id is not importand.
Only by the web application we need the session id and here we can oly
handle one sessionid for one connection.
by the local install
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
ok. i know. nothing will be work is not correct.
i mean. i can allways connect 4 until 6 times at the same time. I have not
tested more. i have open 3 session on my local pc with localhost and 3
session on a remote pc with the ip address.
what i need is. that i can only connect with localhost or
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
