I don't think this can be explained away as a JVM problem. Even if Xalan or Cocoon is running out of resources, they should be printing a more informative error message.
But since they were working fine with an older version of Xalan, I suspect the resources are fine, and that this is a bug. Marcelo F. Ochoa wrote: > Carsten Ziegeler wrote: > >> I don't know the reason for this problem, but it seems that >> it has something to do with the hsqldb. >> In most cases deleting the cocoondb.backup file in the WEB-INF/db >> directory and then starting your servlet engine again, solves >> the problem. >> >> RHTH >> Carsten >> > In my case when I maked the .ear file for OC4J container I play > moving several files from/to lib directory and randomly the problem > desapear, but IMO it was because the JVM manages differents resources > with several combinations, also when the squid proccess manage less > incoming connections on the server the problem also disapear, then I > think that is problem of the JVM connected with the operating system > resources. > Best regards, Marcelo. > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
