Re: [OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-23 Thread Santhoshkumar Sunderrajan
@bogdan-iancu The fix seems to work fine for us. The error is gone now. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-23 Thread Santhoshkumar Sunderrajan
Thanks for the fix, I will try out and update you. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/829#issuecomment-200498948___ Devel

Re: [OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-23 Thread Santhoshkumar Sunderrajan
Try this: https://www.dropbox.com/sh/93j7gdfwk2h5lnq/AACGTMrj6zKaXHjw_YBQBm84a?dl=0 I wasn't able to reproduce the successful case this time. It's failing all the time. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-22 Thread Santhoshkumar Sunderrajan
Here is the log file with additional logging requested: https://www.dropbox.com/sh/93j7gdfwk2h5lnq/AACGTMrj6zKaXHjw_YBQBm84a?dl=0 I was able to reproduce both successful (good_async.txt) and failure (bad_async.txt) cases. Please search for in the logs to identify the async+exec+curl web

Re: [OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-21 Thread Santhoshkumar Sunderrajan
Yes, I can still reproduce it. **Note: **First query is done independently. The second query i.e., port 49864 (/ws/index.php/...) is causing this problem. If you can provide me a patch with extra logging to the module, I can experiment and get back to you. --- You are receiving this because

Re: [OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-19 Thread Santhoshkumar Sunderrajan
**More information:** I tried the following: ` async(exec("sleep 4", "", "$var(restGetResponse)"), RT_RESUME_AFTER_RESPONSE);` I still the error. Makes me wonder whether async+exec is the problem here. --- You are receiving this because you are subscribed to this thread. Reply to this email

Re: [OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-19 Thread Santhoshkumar Sunderrajan
Hi @bogdan-iancu, Yes, there was a connection attempt in both the failure and success cases. So more information: a) Curl makes a webrequest. Webservice will block until a timeout say 4s. Hence we used async for scalability. **Success Case:** ``` osips[6987]:

Re: [OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-18 Thread Santhoshkumar Sunderrajan
2nd one is the faulty one i.e., port 49864 (/ws/index.php/...). I will be deleting the content of the dropbox since you downloaded it. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-18 Thread Santhoshkumar Sunderrajan
Here is the dropbox link to the pcap: https://www.dropbox.com/s/jod9zdifa93d5yv/trace_2016-03-16_20_55-UTC.pcap?dl=0 It has webrequests made to port 80. Thank you. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[OpenSIPS-Devel] [opensips] Problem with using async and exec (#829)

2016-03-15 Thread Santhoshkumar Sunderrajan
We are using async and exec to make a web-request as shown below: $var(fullQueryClientReadyRequest) = "an url with params"; async(exec("curl --connect-timeout 30 --max-time 30 \"$var(fullQueryClientReadyRequest)\"", "", "$var(restGetResponse)"), RT_RESUME_AFTER_RESPONSE); We