> Hi, why is it not advisable to use hot update in a real-time system? > What are the concerns? I found the following paragraph online. > The problem is how update in changing an existing service , so the way Axis2 deal with that is undeploy the service and deploy the service (something similar to that). So if there are already processing request then system may lead to an unknow state. Because of classes and property reinitialization.
-Deepal > > Thank you! > > Jennifer > > "*Hot update* is the ability to make changes to an existing Web > service without shutting down the system. This is an important feature > and required in a testing environment.* 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.* Additionally, there's the > possibility of loosening the existing service data of that service. To > prevent this, Axis2 comes with the hot update parameter set to FALSE > by default. If you want to have this feature, you can do this by > changing the configuration parameter like this: <parameter > name="hotupdate">true</parameter>" > -- Thank you! http://blogs.deepal.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
