We ran the load test this morning on latest snapshot.tar.gzip on FreeBSD 8.1 64-bit and on latest nightly windows 64-bit binaries. Works well on windows, pizza on BSD / OSX. Don't think it is related to ESL-56, since we handle the case where events arrive before replies, our problem is that event and reply seems to be 'merged' corrupting the protocol. Mauritz 28. feb. 2011 kl. 19:08 Anthony Minessale <anthony.minessale@gmail.com>:
indeed, this is almost guaranteed to be fixed in latest HEAD.
On Mon, Feb 28, 2011 at 9:36 AM, Peter Olsson <peter.olsson@visionutveckling.se> wrote:
Are you using git HEAD as of the last couple of days? I know there was some changes for this last week related to ESL-56 - at least I saw some commits related to it... Or it this not at all related to ESL lib?
/Peter ________________________________________ Från: freeswitch-users-bounces@lists.freeswitch.org [freeswitch-users-bounces@lists.freeswitch.org] för Mauritz Løvgren [mauritz.lovgren@hotmail.com] Skickat: den 28 februari 2011 15:26 Till: FreeSWITCH Users Help Ämne: [Freeswitch-users] mod_event_socket message pizza received from BSD machines
Hi,
We are experiencing weird behaviour when using socket connection to mod_event_socket while running FS on FreeBSD and Mac OSX.
We send a lot of bgapi and api commands to the FreeSwitch while controlling and monitoring hundreds of sessions.
We have created a simple load-test that displays the problem we face. The load-test simply fires the following command continuosly to freeswitch: “bgapi sofia status”, generally as fast as freeswitch can receive it.
The following occurs, but only on FreeBSD or MacOSX (10.6.6) (both 64-bit) while using latest version of FreeSwitch:
- Replies and events are inter-mixed on the receive stream (the output from freeswitch), causing protocol errors in the receiving client.
This does _not_ happen on CentOS or Windows, so we wonder what could be causing this. Is there a problem with threading or socket libs here? We assume that FreeSwitch protect a mod_event_socket inbound connection output stream by locking (or other means) to make sure not any two messages are written ‘simultaneously’ causing garbage in the receiving end?
Regards, Mauritz Lovgren System Architect IPLink Inc. http://www.iplink.no
!DSPAM:4d6bb3a032761738012832!
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org