D
dbeavon
Guest
Thanks Rob, this is helpful. I saw messages about not having enough servers in the db logs. But after that I was lost insofar as all those parameters are concerned. Things work fine - normally - until all of a sudden users stop being able to make connections. And the -n wasn't the problem since we were well under that limit (the client-side message seemed to indicate that we had exceeded available resources, presumably connections). It might be nice if the logs said something like "... you ran out of servers. Consider doubling -Mn to XX and, seeing as how you are using more than one type of broker, please consider setting -Mpb to XX/2. While you are at it you, the database is using 90% of the available user connections (-n) so you may want to increase that too." This is all the type of stuff that the database should troubleshoot ("cognitively" to use the latest buzzword from Progress). It can easily run some calcs on the real-life numbers and give me a recommendation. I imagine a lot of tech support and consulting hours are consumed just to get a working set of broker/server parameters in place.
Continue reading...
Continue reading...