Jack Hamilton posted the following:
> We mostly switched to pool services back at First Health lo those many
> years ago, and found that it helped, but also came with a different set
> of problems. The pool servers would also hang occasionally, and we had
> to set up a process to kill them as well. I don't know what, if
> anything, they're using now.
Jack, I remember such issues from way, way, way back in my US Customs days.
Here at SAS Mecca, we run a lot of Socket Services with a one-to-one relationship between the SAS Broker and a SAS App Server, and we run several Pool Services (as previously described); but we do not run any Launch Services. We very, very rarely have any issues with the pool servers hanging. However, every great once in a while we do get a hang in a socket service app server. Those can mostly be remedied by a simple restart. However, here and there over the years, we have had some stubborn ones that we had to work hard to kill.
So, I think that the SAS/IntrNet software has become more reliable, durable, and robust over the years. We are pretty pleased with it.
Jack, best of luck in all your SAS endeavors!
I hope that this suggestion proves helpful now, and in the future!
Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.
Michael A. Raithel
"The man who wrote the book on performance"
Author: Tuning SAS Applications in the MVS Environment
Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
Author: The Complete Guide to SAS Indexes
They are so wrong. Godzilla should not be destroyed, he should
be studied. - Dr. Kyohei Yamane