# Testing from Flazr

**URL:** <https://community.wowza.com/t/testing-from-flazr/35255>\
**Category:** Wowza Streaming Engine\
**Created:** [August 13, 2010, 1:50pm UTC](https://community.wowza.com/t/testing-from-flazr/35255 "2010-08-13T13:50:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Artus](https://avatars.discourse-cdn.com/v4/letter/d/a3d4f5/32.png) [@David\_Artus](https://community.wowza.com/u/David_Artus)\
**Post date:** [August 13, 2010, 1:50pm UTC](https://community.wowza.com/t/testing-from-flazr/35255/1 "2010-08-13T13:50:25Z")

</div>

I’d appreciate any help with this problem playing MP4 content …

I have been using Flazr for load testing. Against Wowza 1.7 it’s working fine: I can spawn multiple threads retrieving chosen content.

With Wowza 2.1.1 build24490 I cannot stream. Flazr gets a response from Wowza that it interprets as

NetStream.Play.Stop

This does not happen with Wowza 1.7.

If it helps Flazr logs that it’s specifying these flash arguments:

15:25:42,110 [New I/O client worker #1-1] INFO [ClientHandler] - sending command (expecting result): [0 COMMAND\_AMF0 c3 #0 t0 (0) s0] name: connect, transactionId: 1, object: {app=vod, flashVer=WIN 9,0,124,2, tcUrl=rtmp://192.168.101.3:1935/vod, fpad=false, audioCodecs=1639.0, videoCodecs=252.0, objectEncoding=0.0, capabilities=15.0, videoFunction=1.0},

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [August 13, 2010, 2:33pm UTC](https://community.wowza.com/t/testing-from-flazr/35255/2 "2010-08-13T14:33:18Z")

</div>

We recommend the Wowza Dynamic Load Balancing system:

[https://www.wowza.com/docs/how-to-get-dynamic-load-balancing-addon](https://www.wowza.com/docs/how-to-get-dynamic-load-balancing-addon)

Richard

---

<div class="post-metadata">

**Author:** ![David\_Artus](https://avatars.discourse-cdn.com/v4/letter/d/a3d4f5/32.png) [@David\_Artus](https://community.wowza.com/u/David_Artus)\
**Post date:** [August 13, 2010, 3:40pm UTC](https://community.wowza.com/t/testing-from-flazr/35255/3 "2010-08-13T15:40:48Z")

</div>

The problem lay in a “registry” I was using, which had different logic for Wowza 1.7 and Wowza 2.1. As it happens the 2.1 version was incorrect. When I looked in the Wowzaa logs it all became clear.

Flazr is working fine for both versions.

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [August 13, 2010, 3:51pm UTC](https://community.wowza.com/t/testing-from-flazr/35255/4 "2010-08-13T15:51:16Z")

</div>

Great, glad it’s working. Thanks for the update.

Richard