HTTP Trigger and Maximum Number Of Sessions

Version 1
    This document was generated from CDN thread

    Created by: Paulo Silva on 16-02-2012 12:05:22 PM
    I wrote an application to test http triggered application response times in order to troubleshoot an issue that arised with a production application we wrote for a customer.
    The ivr script is very simple containing only a delay step and a Send Http Response step; both the application and trigger are set for 20 sessions.
    We can clearly see that the number of running sessions never goes above 2 or 3, while all other requests wait until one of those sessions terminates; this is exactly the scenario we ran into in the production application and that we set out to prove in the first place with our little test application. In our tests we have seen requests waiting longer than a minute for a response, while the number of sessions was 2 nowhere near the maximum we configured.
    Any ideas/suggestions/comments?
    Thanks in advance,
    Paulo Silva

    Subject: RE: HTTP Trigger and Maximum Number Of Sessions
    Replied by: Nathan Reynolds on 10-04-2012 02:02:54 PM
    Hello Paulo,
    Did you ever find out what was going on with this? I am having this exact issue. I can only have at most 2 or 3 http requests to an http application trigger at a time. I have the max sessions set to 20 as well. Subsequent requests time out after the initial 2 or 3 are setup. Thanks! Nathan