These errors are now happening quite frequently.
Is there something that could be done so as to restrict these errors
or the only way out is to act after the error by cleaning up & restart?
On 12-Oct-2009, at 9:17 AM, Adam Heath wrote:
> Kaushik Chakraborty wrote:
>> I deleted the .cowstate.xml file and then everything seemed fine. But
>> again this morning I found the same exception. Is the .cowstate.xml
>> remains somewhere in the cache which Webslinger uses? I restarted the
>> server, to flush the cache, and everything again is fine.
>>
>> Please help as there is no place I can find help on Webslinger other
>> than here.
>>
>> Adam / Ean - Please share some light on the issue. Its kind of
>> urgent.
>
> When memory pressure occurs, and the xml processor has to reload a
> class multiple times when .cowstate.xml is being manipulated, the file
> will end up being 0 bytes in size. Then, you'll start getting this
> error later on.
>
> This generally happens to the .cowstate.xml files in the
> /Var/WorkArea/ directory. Best to do a find of all 0-byte files,
> remove them, then restart.
>
> What are you using webslinger for? There are no docs on it, and the
> version in ofbiz isn't really doing anything useful.
Locked
