View Complete Thread
  • Re: 504 Gateway Timeout with RequestAquireState

    Nov 16, 2019 10:24 AM|email2saga|LINK

    Thanks for the reply Rovastar !!!

    You are right, we hit an external API via direct IPAddress, close to 2% of our transactions has wrong IPAddress and i dont have choice to skip them, so all these calls are holding the worker process threads for 75 Secs which is proxy timeout and its an expected  scenario for our business case.

    I have set the WCF throttle as based on server CPU count (4)

    <serviceThrottling maxConcurrentCalls="64" maxConcurrentSessions="400" maxConcurrentInstances="464"/>

    As you mentioned i will check the dump during hang state and confirm.