but it would be useful to know more precisely what is being executed across the webapi.
?? getpeername() failed. errno=107 (Transport endpoint is not connected) -
freeswitch@127.0.0.1 - [29/Jul/2009:00:32:42 +0000] "POST" 200 17
?? getpeername() failed. errno=107 (Transport endpoint is not connected) -
freeswitch@127.0.0.1 - [29/Jul/2009:00:32:42 +0000] "POST" 200 17
?? getpeername() failed. errno=107 (Transport endpoint is not connected) -
freeswitch@127.0.0.1 - [29/Jul/2009:00:32:42 +0000] "POST" 200 17
and I think it's related to some problems I'm having with my program. A few other users
http://www.mail-archive.com/freeswitch-users@lists.freeswitch.org/msg09225.html and
http://jira.freeswitch.org/browse/MDXMLINT-28 noted similar items appearing in their logs, but I could not find a definitive solution. Does anyone have any solutions to this error? When this error appears in my freeswitch_http.log, all webapi commands seem to block, and than rapidly get executed all at once, whenever the block is released. I'm using 14163. The errors appear to happen only once a certain load level is reached, so I'm having trouble reproducing it consistently.
Could this be caused by an xmlrpc request closing the socket connection before FreeSWITCH has a chance to respond? Can anyone recommend any better ways for me to diagnose this issue? Thanks. I'm using the XMLRPC with Ruby on Rails (REE) and Passenger.
--matt