h1. Context parameters:

If you deploy the Webconsole with apache Tomcat, take attention to don't set to "true"

the "*reloadable*" context parameter in the _server.xml_ file of your web server.
{code:language=xml|title=server configuration file} <Context docBase="petals-webconsole-ui" path="/petals-webconsole-ui" reloadable="false" source="org.eclipse.jst.j2ee.server:petals-webconsole-ui" debug="0">
<Realm className="org.apache.catalina.realm.UserDatabaseRealm" digest="SHA-1" resourceName="UserDatabase"/>
</Context>{code}
As is signified in the Tomcat documentation for "reloadable" parameter :


"Set to true if you want Catalina to monitor classes in /WEB-INF/classes/ and /WEB-INF/lib for changes, and automatically reload the web application if a change is detected. This feature is very useful during application development, {color:#ff0000}but it requires significant runtime overhead and is not recommended for use on deployed production applications{color}. You can use the [Manager|http://tomcat.apache.org/tomcat-4.1-doc/manager-howto.html] web application, however, to trigger reloads of deployed applications on demand."

+http://tomcat.apache.org/tomcat-6.0-doc/config/context.html+

If you deploy the Petals Webconsole with "reloadable" to "true", the container reload the application context whenever you add, delete, modify ... one server or one user.

You'll be really annoying, because it will require you to login again.