Wonder, Bla...
ERXApp has support for not accepting sessions when a certain memory
threshold has been reached and accepting them once they time out.
Also, you can set the timeout to something lower if the user hasn't
yet logged in, for example.
Cheers, Anjo
Am 22.01.2009 um 21:43 schrieb Vicky C. Miller:
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:
Avg. Memory Usage Per Session (bytes)
Total Memory 102,300
Free Memory -129,468
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.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-
dep...@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/anjo%
40krank.net
This email sent to a...@krank.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
