[Freeswitch-users] XML_CURL max connection limit

[Michael Jerris]

I would need to see the specifics of your dialplan, but I suspect you have some transfers or execute extension that are causing it to re-enter dialplan.  Are you sure on all the others that they are making the exact same requests?  Details here will be necessary to understand exactly what is going on..

Mike

On Jun 7, 2013, at 4:07 AM, Muhammad Shahzad <shaheryarkh at gmail.com> wrote:

> Guy, after detailed analysis i can confirm it was an Apache issue, and changing Apache configuration changes the concurrent call limit. However, one thing i observed about xml curl is that it makes several request with same parameters per call. Even if we have no calls running on server, as well as as Apache is completely free. I can see FS makes at least
> 
> 1). 3 hits for dialplan.
> 2). 2 hits for directory.
> 3). 4 hits for voicemail.
> 4). 3 hits for ivr.
> 5). 2 hits for sofia.
> and so on..
> 
> While ideally only one hit should be sufficient to get all these configurations. What is the point of making all these redundant hits? We have roughly 15 - 20 hits made per call, which is huge and causes significant load on Apache.
> 
> Both Apache and FS are running on dedicated machines and connected over Gigabit Ethernet with zero packet loss, so i doubt these hits are "re-transmission".
> 
> Thank you.
> 
> 
> 
> 
> On Thu, Jun 6, 2013 at 1:24 AM, Muhammad Shahzad <shaheryarkh at gmail.com> wrote:
> Yes, its a feature, i know. I was just looking at how this feature was tested, as mentioned in its logs,
> 
> 2010-01-04 15:01:51.945020 [INFO] mod_dialplan_xml.c:408 Processing 21653XXXXX->121637XXXXX in context termination
> 2010-01-04 15:01:52.054466 [ERR] mod_xml_curl.c:310 Received HTTP error 0 trying to fetch http://192.168.0.2/gateway.php
> 2010-01-04 15:01:52.054545 [CONSOLE] mod_xml_curl.c:317 XML response is in /tmp/6632ebb1-d19f-4d51-a07e-ec2ce0387f83.tmp.xml
> 
> Thank you.
> 
> 
> 
> 
> On Thu, Jun 6, 2013 at 12:48 AM, Michael Jerris <mike at jerris.com> wrote:
> This is adding a feature to allow timeout to be set in ms instead of seconds.  This is not a problem, its a feature, that was added a while ago.  Until you can determine if the request is being sent for the one thats failing, your not going to solve this issue.
> 
> Mike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20130607/cc4d03b4/attachment.html