John, I had an issue awhile back where the app server was 'backed up'.and because of this backup it didn't seem like the app was working (thread bound)..so people were closing their browser and trying to log back in, didn't work, rinse and repeat. This behavior from several hundred users at the same time quickly used all of my Proxy Pools on my two midtier servers.so people started getting the errors mentioned below..obviously the fix was to make the app server not be backed up and everything processed properly..but because of this incident we have increased our pool size..couldn't find any guidelines..so I set it at 500..don't know how to tell how many are currently in use.so I have no clue if 500 is too many, too few, etc.but haven't seen the error since.
From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of John Sundberg Sent: Tuesday, June 01, 2010 9:11 AM To: arslist@ARSLIST.ORG Subject: Re: Error while executing API ** Speaking of the default of 80 -- has anybody changed this one way or the next - and if so - what did you see? It seems to me as if you can have 80 connections to the ARServer from this "client" at once - is that what a ProxyPool is? How long does a Proxy live? -John On Jun 1, 2010, at 10:00 AM, LJ LongWing wrote: ** SriSamSri, This is a configuration parameter in your Mid-Tier under 'General Settings' titled 'Maximum connections per server'. The default is something like 80..but basically it's a queuing mechanism that prevents a single midtier server from overwhelming the app server..I think the default is 80. Increase it to something larger..or increase the number of midtier servers you have to accommodate a larger load spread across them.. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of SriSamSri Appecherla Sent: Monday, May 31, 2010 6:27 AM To: arslist@ARSLIST.ORG Subject: Error while executing API ** Hi, I am creating Incidents in Remedy using java API (ARS 7.5, MidTier 7.5, Oracle 11g, Sun Solaris 10). I see the following error during the execution - We have reached the max number proxies in the pool; wait for one to become available for thread Tid_118 for server 10.142.165.141:7919 <http://10.142.165.141:7919/> This error does not stop Incidents creation. However, I feel this is slowing the process of Incidents creation in Remedy. What could be the reason for this error? Thanks! Regards, SriSamSri Appecherla Mobile# +91 991 610 6008 _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ -- John Sundberg Kinetic Data, Inc. "Building a Better Service Experience" Recipient of the WWRUG09 Innovator of the Year Award john.sundb...@kineticdata.com 651.556.0930 I <http://www.kineticdata.com/> www.kineticdata.com _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
