Once I got the server calmed down, I tried opening up one of those pages and within a minute the server was at the maximum connections and alerting it's little heart out.
Bad news is, this database is a monster so I can't figure out what's actually in those pages. I'll have to see if I can wrestle it from the developer.
So if I get this right, is a problem in case a specific application is called?
But how does the db interfere with the raise of clients? Never the less you might want to log the DB queries during this time if you assume the application's backend DB causes this error.
How about blocking this specific request?