IF the connections are not being released, they may not be dropped when they "die" ...
check the tcp_keep_alive (and related) unix kernel parameterbut this is unlikely if the app is supposed to drop them
Note, apps that make multiple connections to the ASE server are famous for:
a not managing their connections properly (as so psot appears to identify)so watch out for this.
b deadlocking (one connection) against themselves (another connection)
If I have heard this once, I have heard this a thousand times. Not once was it true. It is your job to check (you do have monitoring and auditing, don't you ?) both before and after and identify exactly what has changed (the evidence is something has changed). A customer called me in last week, because a production system broke (slow response) after fully testing a Sybase release, no changes to the app. Ran an auditing script and guess what: two indexes missing plus two duplicate indexes. Amazing what a typo will produce, especially if you do not check the results. Point is problem was in the app, not Sybase release.
On our side we have not made any changes with the DB or code, and application was not hanging up as it is now.
What in God's name are you (apparently a software vendor) doing still on 11.0.3. Without checking my ancient diaries, from memory, that is more than nine years old, and end-of-lifed ages ago. Get with the program.
Last edited by DerekA; 08-14-06 at 04:19.
Senior Sybase DBA/Information Architect derekATsoftwaregemsDOTcomDOTau
Anything worth doing is worth doing Right The First Time
Spend your money on standards-compliant development or spend 10 times more fixing it