This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am using Tomcat clustering (with static membership) in one of my assignments. When a new instance gets added to the cluster, one static member tag should get added to server.xml of each instance of the cluster. But changing the server.xml means restarting the server - so if I have 10 instances in the cluster and I try to add a new one, we'll have to restart 10 servers because of change in their server.xml - which is not desired.
Is there any way out to reflect the change of server.xml without restarting the server? I am using Tomcat version 6.0.36.
(Dynamic membership cannot be added because of some restrictions)
The server.xml file is digested at Tomcat startup. To get Tomcat to see any changes, Tomcat must be restarted. This is why Context elements in server.xml are discouraged - updating a webapp (Context) when it's in server.xml cannot be done on the fly.
If you cannot support dynamic clustering, you're going to have to cycle each Tomcat. Although at least, since it's a cluster, that means that you only have the annoyance of cycling Tomcats and not of having the entire service down.
Customer surveys are for companies who didn't pay proper attention to begin with.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Changing server.xml without restarting Tomcat