Andr� van Toly wrote:
We have already tried 'upping' the number of threads. This will make Tomcat 'hang' more rapidly. Really: maxProcessors="60" is the maximum Tomcat can handle in our configuration.
The point is that in my opinion the Multicast causes a huge peak in Tomcat's thread usage (and because of that: memory usage). It occurs quit frequently and normally Tomcat just keeps running but the Multicast is not delivered (everywhere) and the nodes in the live webapps are not updated.
That is probably because that Multicast spawns a thread for every node change received. So when you are doing lots of node changes it gets bogged down.
My point exactly: When you save a complicated EditWizard (f.e. a news wizard with related images, urls, mediasources etc.) all nodes that were opened in the wizard are considered changed and will be multicasted over all the MMBase instances that share the same cloud. Resulting in a huge number of Multicast threads etc.
---Andr� -- ------------------------------------------------------------------>><<-- Andr� van Toly http://www.toly.nl 06-27233562
