Hello Vadim. The Problem from the other thread is possibly related - but i do not use saxon nor changed the default configuration of cocoon-2.0.3 concerning XSLT processor usage (at least i'm not aware of this - i did some updates from earlier cocoon version, but always tried to get all changed configurations from the new cocoon.xconf etc.).
Again, my XML streams transformed are not that big (usually < 100kb), and the resulting JPEG is really small (~2-3kb). But perhaps the bug appears by either big XML input files or a long runtime (points to small errors summing up and finally resulting in the error - but why then a ClassCastException??). Unfortunately i have not found a way to reproduce the problem by force; in that case i would try to debug it. Perhaps i will try to "blow up" my XML input streams and see if i can produce the problem that way. But i'm not sure if it has really to do something with the other thread. Stefan > -----Original Message----- > From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, August 14, 2002 3:49 PM > To: [EMAIL PROTECTED] > Subject: Re: Strange error using JPEG/SVGSerializier under > heavy load - > ClassCastException > > > Stefan Seifert wrote: > > >Configuration: Cocoon 2.0.3, Tomcat 3.2.3. > >We use the SVGSerializer with JPEG-Output to generate > graphical menus (we could not get the customer to use only > plain text menus). > > > >All works fine after a starting up tomcat. But after a few > days (variing) without even touching the server the SVG > Generantion fails with the Error below - a > ClassCastException. Every following request of a JPEG > generation failes with the same error. > >All other requests processing only HTML still work! > > > >This error is very strange, because all works until the SVG > Serialization seems to hang up totally (but only the SVG > Serialization). > >The memory utilisation is normal. There are no > OutOfMemory-Erros or anything that points to a memory leak. > Unfortunately it was not possible to reproduce this problem > by force using a web stress tool, it only happens on the live > servers and only after a few days. > > > >After a tomcat restart all works well again. > > > >Any ideas? I searched the mailing lists of Cocoon and Batik > but found hints. > >We tried replacing the batik 1.5beta2 shipped with Cocoon > 2.0.3 with the latest 1.5 beta3, same problem. > > > > > I wonder is it related to this thread or not: > http://marc.theaimsgroup.com/?t=102795224000002&r=1&w=2 > > Vadim > > >Stefan ... --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
