Zero bytes read from the steam, indicating the end of stream, or a read error under heavy load!

[patriot3w]

I'm working on a journal archiving slowness issue, i got numerous below lines:

Dtrace journaltask only:

{CZlibCompressor::LoadInputBuffer:#391}Zero bytes read from the steam, indicating the end of stream, or a read error under heavy load!

Any idea where this stream targeted to? 

Thanks. 

[patriot3w]

we are having 60K in one jorunal mailbox, 50K in another journal mailbox backlogs. Refer to below link

https://www-secure.symantec.com/connect/forums/journal-mails-not-being-archived , is it because the back log caused the slowness issue?

Thanks.

[JesusWept3]

What version of Enterprise Vault?
What version of windows?
What version of Exchange?
What do you use for EV Storage (Centera? NetApp?)

I've seen this before when someone was using Centeras and they had something like 5 vault stores on a single server and all used centera collections, and because of this, so many StorageFileWatch processes were being created it was exhausting the memory, and it was showing this by throwing strange ZLib errors

you may also want to look at whether there are any processes with massive amounts of open handles, whether the antivirus is set to exclude your Vault Store and Temp locations (and if you are using centeras with collections, the temp collections area) .... and also make sure your paging file is appropriately set, i've seen a lot where people have 16GB of memory and only 4GB of paging file

[JesusWept3 · Accepted solution]

And just to add to this issue , saw an issue the other day where the journaling was crawling, and there was monitoring process (not EV) that had created about 60k+ file handles, once that process was killed, journaling started flying

[patriot3w]

What version of Enterprise Vault?

EV 10 SP1(10.0.1)

What version of windows?

Windows 2008 R2 SP1
What version of Exchange?

Exchange 2010 + SP2
What do you use for EV Storage (Centera? NetApp?)

CIFS(Network share on Windows 2008 R2 SP1)

All the vault stores on the single network share path. 

Let me check on the file handles.