Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Stupid bugzilla. You hit enter on a wrong text field, and this happens. Description of problem: Tomcat6 (possible even Tomcat7) plugin seem not to be invoking the 'save()' operation on 'Users:type=UserDatabase,database=UserDatabase' MBean. When a user removes a tomcat role through the JON web interface, the role is still written in tomcat-users.xml. That means, that when tomcat is restarted, the role will be active again. Version-Release number of selected component (if applicable): 3.1.2.ER4 How reproducible: 100% Steps to Reproduce: 1. add a tomcat role in JON. 2. assert it is available through jconsole 3. assert it is present in tomcat-users.xml 4. remove the tomcat role in JON. 5. assert it is available through jconsole 6. assert it is present in tomcat-users.xml Actual results: role is still present in tomcat-users.xml, but not available in jconsole Expected results: role should be removed from tomcat-users.xml
The plugin correctly invokes the save method on all user database operations, but the said user database default configuration is to be read only (and so refuses to do the save). This needs to be configured by the user if he wants to be able to edit the user database dynamically, and is an obvious safety feature.
Unless I missed something, it's a duplicate, the bahvaior is a bit weird but that's what Tomcat does by default. *** This bug has been marked as a duplicate of bug 688358 ***