I haven't seen the -gm switch in version 8 and am reluctant to believe sessions changed so significantly in May that we're overwhelming the max sessions. ASA8 starts up with max concurrent users of 500 and we rarely have more than 50 sessions at any one point in time. We backed out the one patch that could have even remotely been the cause (MSDTC) to no affect. Looks like a rebuild. We're getting hardware ready to set up a test server on the side. We'll cut it temporarily to production and test for 24 hours.
Sybase analyzed the DB traces we executed. Said they saw network disconnects. Our vendor analyzed the ODBC traces and saw the same. Through all of the network changes we fixed our core system which was crashing for several branches a day. At least I accomplished that. Thanks for your insights - and how's the Jolt Cola? That stuff is bad for you, you know.
Main Topics
Browse All Topics





by: mrjoltcolaPosted on 2009-09-19 at 10:51:49ID: 25373816
Could it be that you are reaching maximum connection count for your configuration?
roup/ sybas e.public.s qlanywhere .general/b rowse_thre ad/thread/ 3c2bc6f723 0bb403
inde x.php#http %3A%2F%2Fd cx.sybase. com%2F1100 en%2Fdbadm in_en11%2F gm- databas e-dbengine .html
http://groups.google.com/g
I don't have version 8 around to test with, but with newer versions, the server has a -gm switch that sets the max concurrent connections.
http://dcx.sybase.com/
What are the parameters you use to start ASA?