nageshsrao wrote:
we are getting the GC printed on to the same catalina.out and we see that the memberAdded messages appear almost at the time of GB getting printed, does it prove that longer GC pauses are causing this? is there any other data points/proof can be get?
E.g. -XX:+PrintGCApplicationStoppedTime
rearding "network problems", we are requesting the network to capture the multicast traffic between these nodes, is there anything you suggest us to do?
If you are doing the multicast only inside a subnet, the usual basic network monitoring should be sufficient. But often during phases were you have problems that might be network related it is good to keep in touch with the network people in order to discuss, if they know about any general network problems.
If you do multicasting crossing the borders of subnets, the network needs to use multicast group membership protocols, which involves complicated configuration of routers. Most users though don't need to cross subnets.
regaring "increase the membership timeout" we plan to increase this to 5 minutes, do you have any other suggestions. tomcat startup takes almost 70 seconds ( it hosts almost 32 apps) and all of them are clustered.
I would expect, that your GC even with a big heap won't take longer than 20 seconds. Most likely it's much less. On the other hand if you go to 5 minutes, you would always need to wait 5 minutes between shutting down one node and starting it up again. It seems unreasonable to me, that IT staff will obey that. I would suggest 30 seconds and a clear message in the startup script, to remember people using it, that they have to wait 30 seconds after stopping and before starting again.
Regards, Rainer --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
