> > I am watching the log of Tomcat. I found after 20 minutes,
> the Tomcat
> > still create lots of new sessions. But the LoadRunner has
> stopped to
> > send request for 15 minutes.
Makes perfect sense to me.
The servlet times out on the DB connection, which may take up to a
minute or so, fails, and then processes the next request, which will
experience the same timeout. Since you have somehow asked for sessions
to be created for each, tomcat will still be processing requests and
thus creating sessions.
Your "caching" thing happens at the socket level. This pseudocode
application runs on any single system, without blocking or deadlocking:
#server
s = socket(..)
s.listen()
# Client - this will not block
c = socket(..)
c.connect(s.getaddr())
c.send("hello")
c.close()
# server again - no, we're not using threading
m = s.accept()
data = m.recv()
m.close()
In other words, you can connect, send and close a client socket, without
the server actually ever reading the request. If you set the SO_LINGER
option in the client, or simply wait for the response, you can alter
this behaviour.
This message and attachment(s) are intended solely for use by the addressee and
may contain information that is privileged, confidential or otherwise exempt
from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for
delivering this message to the intended recipient, you are hereby notified that
any dissemination, distribution or copying of this communication is strictly
prohibited.
If you have received this communication in error, please notify the sender
immediately by telephone and with a 'reply' message.
Thank you for your co-operation.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
