# Zero sized function / Data format incorrect / packetSizeReset

**URL:** https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342
**Category:** Wowza Streaming Engine
**Created:** [March 26, 2009, 1:41pm UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342 "2009-03-26T13:41:21Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/system/32/447_2.png) [@system](https://community.wowza.com/u/system)
#### Post date: [March 26, 2009, 1:41pm UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342/1 "2009-03-26T13:41:21Z")

</div>

Hi,

A few hours ago Wowza encountered an issue that caused it to stop responding, and then later resume with the following errors:

ERROR server comment 2009-03-26 12:35:45 - - - - - 409980.624 - - - - - - - Data format in

correct, killing client connection.

ERROR server comment 2009-03-26 12:35:45 - - - - - 409980.624 - - - - - - - Zero sized fun

ction (client): type:20 size:0 index:1536

ERROR server comment 2009-03-26 12:35:45 - - - - - 409980.624 - - - - - - - packetSizeRese

t: 8:128

We recently added some additional RAM to the server that this occurred on - could this be a result of faulty RAM? We don’t really want to take the server down to do a memtest unless we really have to though.

Thanks in advance for any help!

---

<div class="post-metadata">

### Author: ![Charlie\_Good](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/charlie_good/32/383_2.png) [@Charlie\_Good](https://community.wowza.com/u/Charlie_Good)
#### Post date: [March 26, 2009, 9:18am UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342/2 "2009-03-26T09:18:09Z")

</div>

It could be. I am not sure. This usually means a single connection is out of sync for some reason or other. It certainly could happen due to bad memory.

Charlie

---

<div class="post-metadata">

### Author: ![Charlie\_Good](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/charlie_good/32/383_2.png) [@Charlie\_Good](https://community.wowza.com/u/Charlie_Good)
#### Post date: [January 3, 2011, 10:38am UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342/3 "2011-01-03T10:38:42Z")

</div>

Be sure you are running latest version of Wowza. There was a small change to fix a problem that could lead to this error message. If you are still seeing this error after upgrade to latest version then be sure server is tuned properly. It could be caused by long garbage collection pauses. If you are still seeing the problem, then it is most likely an errant RTMP connection.

Charlie

---

<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: [February 8, 2011, 5:51pm UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342/4 "2011-02-08T17:51:10Z")

</div>

I think updating did help. You can update to 2.2.3 here:

[https://www.wowza.com/docs/wowza-streaming-engine-software-updates](https://www.wowza.com/docs/wowza-streaming-engine-software-updates)

Then you can update to 2.2.3.04 here:

[https://www.wowza.com/docs/wowza-streaming-engine-software-updates](https://www.wowza.com/docs/wowza-streaming-engine-software-updates)

Richard

---

<div class="post-metadata">

### Author: ![Robert\_Filipovich](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@Robert\_Filipovich](https://community.wowza.com/u/Robert_Filipovich)
#### Post date: [September 19, 2012, 1:15pm UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342/5 "2012-09-19T13:15:44Z")

</div>

We are seeing this in Wowza 3, any further ideas? We feel we have made all the garbage collection tuning etc… They are virtual machines and we are adding memory soon as well. Any other ideas would be great.

---

<div class="post-metadata">

### Author: ![Melih\_Onvural](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Melih\_Onvural](https://community.wowza.com/u/Melih_Onvural)
#### Post date: [January 3, 2011, 10:30am UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342/6 "2011-01-03T10:30:53Z")

</div>

Was there a resolution that anyone found to this problem? We’re seeing it in our error logs, and we’re trying to understand if it’s a hardware problem or if we should focus elsewhere in our stack.

Thanks

---

<div class="post-metadata">

### Author: ![Melih\_Onvural](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Melih\_Onvural](https://community.wowza.com/u/Melih_Onvural)
#### Post date: [January 3, 2011, 10:56am UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342/7 "2011-01-03T10:56:21Z")

</div>

Thanks Charlie! We’re upgrading now, and I’ll report back with the results.

---

<div class="post-metadata">

### Author: ![Sriram\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@Sriram\_Ramachandran](https://community.wowza.com/u/Sriram_Ramachandran)
#### Post date: [February 8, 2011, 10:33pm UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342/8 "2011-02-08T22:33:29Z")

</div>

Hi monvural/Charlie, we are facing the same error with Wowza 2.1.2.

Our windows Flash clients do not have any issue, but ‘clients killed’ with Mac.

Can you tell us if your problem is resolved now?

---

<div class="post-metadata">

### Author: ![Sriram\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@Sriram\_Ramachandran](https://community.wowza.com/u/Sriram_Ramachandran)
#### Post date: [February 10, 2011, 2:28pm UTC](https://community.wowza.com/t/zero-sized-function-data-format-incorrect-packetsizereset/342/9 "2011-02-10T14:28:21Z")

</div>

Thanks much rrlanham, we have not been able to replicate this issue with the latest stable build 2.2.3, so the PktSizeReset issue appears resolved.

Cheers,

Sri1x
