On Jan 22, 2009, at 12:43 PM, Vicky C. Miller wrote:
We are finding that our WebObjects instances are becoming
overwhelmed. We are seeing a high number of “Current Active
Sessions” when we look at the Statistics even though we know that
there are actually far fewer active users in our application. We
are also seeing the following with a number of these instances:
You'll probably also experience a problem getting the instances to
Refuse New Sessions. I've seen this before, and I think it happens
when you have images or other resources that makes requests of your
app without sending the session info along, causing an 2 or more
sessions to be created when hitting a single page.
Avg. Memory Usage Per Session (bytes)
Total Memory 102,300
Free Memory -129,468
These numbers have always been wrong for me, so I've learned to
ignore them. :-)
Does anyone have some tuning suggestions as well as killing these
sessions regularly that do not appear to be active or timing out?
We are running on SOLARIS. We have set the following parameter but
going to 60 seconds does not seem to kill these extra sessions that
we are currently seeing:
/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000. We are
running WO 5.2.4, which is the highest WO version level that runs
on SOLARIS.
WO 5.2.x has some pretty serious bugs in deployment (you'll see a lot
of ports in the "CLOSE_WAIT" state if you do an lsof on the wotaskd
process). I highly recommend upgrading to 5.3 (not 5.4).
sacha
--
Sacha Michel Mallais 800 kg gorilla
Global Village Consulting Inc. http://www.global-village.net/
PGP Key ID: 7D757B65 AIM: smallais
1. Never tell everything at once.
-- Ken Venturi, Ken Venturi's Two Great Rules of Life
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
