Hi Joakim, I am glad to hear it is better, but still not the best.
joakim verona dijo: > Antonio, > > I tried to remove the workaround. Initially I was very happy, because it > seemed to work much better. > > Soon the image crashing behaviour resumed though. > > It seems that JPEG decoders themselves leak memory(or something to that > effect). Hmm.... > > My tomcat goes from 97 mb to 115 mb, according to top. When this happens > tomcat throws a "OutOfMemory" exception, > but continues working. Cocoon then gets a "truncatedfile" exception in > the image routines. Are you tried allow Tomcat to use more memory? Maybe you need to play with some switches inside Tomcat. The same apply when you are using FOP. Maybe if you increase the memory for Tomcat it would be able to render more images at once. Can you make the test of it? > After a while the system recovers and can generate a couple of more > thumbnails. > > If the cocoon pooling system for the image reader works properly, as > Vadim suggested, there should never > be more than 2 image buffers active in my case. So out of memory should > never occur if theres no leak. > > I will try to rewrite the scaling code to use the newer > javax.imageio/JAI apis instead. Maybe they work better. > > Thanks also for the 1.4 identification code. > > Regards, > /Joakim > Best Regards, Antonio Gallardo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
