# SharedObject message issues

**URL:** <https://community.wowza.com/t/sharedobject-message-issues/48176>\
**Category:** Wowza Streaming Engine\
**Created:** [February 23, 2017, 7:14pm UTC](https://community.wowza.com/t/sharedobject-message-issues/48176 "2017-02-23T19:14:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert\_Hotz](https://avatars.discourse-cdn.com/v4/letter/r/8dc957/32.png) [@Robert\_Hotz](https://community.wowza.com/u/Robert_Hotz)\
**Post date:** [February 23, 2017, 7:14pm UTC](https://community.wowza.com/t/sharedobject-message-issues/48176/1 "2017-02-23T19:14:25Z")

</div>

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:

```auto
ERROR server comment - execute: null

```

This is the client code that threw the error:

```auto
parentApplication.infoRso.send("cancelRequest");

```

I added in a dummy parameter and it worked fine:

```auto
parentApplication.infoRso.send("cancelRequest", "");

```

I also tried calling the command from within Wowza and it worked fine:

```auto
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.