Re: hotupdate in production
In the article "The Axis2 Deployment model, Part 1" (http://www-128.ibm.com/developerworks/library/ws-axis2soap/index.html), it suggests the one not use this feature in production: "However, it's not advisable to use hot update in a real-time system, because it could result in the system leading into an unknown state." Is there an alternative, other than restarting Tomcat? If your production instance of Axis2 is providing multiple services, it's not great to bring them down as well. Well I was talking about the hot-update . Meaning you are trying to change existing (running) services. If you want to add new services then there is no problem with that. Can anyone provide more information on what the drawbacks of hotupdate are? Say , you have system where a request processing for the service you are going to update. Then that particular service processing might lead to an unknown state. -Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HotUpdate
Hi Stephan ; It will be gr8 if you could help me to re-create the issue, pls create a JIRA and attach whatever necessary to re-create the issue. Thanks Deepal > hello. > > question regarding hot update - axis2 is running as a server. > > 1. deployed an aar > 2. axis2 picks it up and installs it > 3. deployes again same aar, class files have changed > 4. axis2 picks it up and installs it, after undeploying the previous > instance > > but: the class files are not reloaded. > > axis2.xml: > ... > true > true > ... > > Any hint ? > > Thanks and kind regards, > Stephan Gloor, Webservices teacher, HSZ-T, Zürich, Switzerland -- Thanks, Deepal "The highest tower is built one brick at a time" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
