Our company is porting over our system from Adobe Media Server to Wowza and I ran into a nasty bug today.
According to Adobe & Wowza spec, messages can be sent for a shared object using the SharedObject.send(params…) method. This works on AMS, but in Wowza, when sending a message from a flash client with a single parameter (used as the function name), Wowza throws the following error:
ERROR server comment - execute: null
This is the client code that threw the error:
parentApplication.infoRso.send("cancelRequest");
I added in a dummy parameter and it worked fine:
parentApplication.infoRso.send("cancelRequest", "");
I also tried calling the command from within Wowza and it worked fine:
this.parent.infoManager.sharedObject.send("cancelRequest");
It seems that Wowza is expecting at least 1 parameter no matter what.
I’m using Wowza 4.6.0 build 19395, and the client is a Flex application written in ActionScript 3. I tried using both AMF0 and AMF3 encoding on the NetConnection & SharedObject to no avail.
I also checked with another client and verified that the call is not being passed to other clients. It gets stuck at the server.
