Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 865403

Summary: Cannot add a User to tomcat's UserDatabase
Product: [JBoss] JBoss Operations Network Reporter: Jan Martiska <jmartisk>
Component: Plugin -- TomcatAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: high    
Version: JON 3.1.1CC: jclere, mhasko, mhusnain, spinder, syeghiay
Target Milestone: ---   
Target Release: JON 3.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: ?? Consequence: Adding a user using the JBoss Operations Network (JON) interface used in JBoss Enterprise Web Server results in the following error in the agent log: Fix: None Result: None Workaround: None
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-08 09:04:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Martiska 2012-10-11 11:12:06 UTC 
Tomcat version: EWS 2.0.0.CR1

When I try to add a User through JON's interface, I get this error in agent's log:

2012-10-11 06:58:40,373 DEBUG [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Throwable was found in creation report for request [10032].
java.lang.IllegalStateException: Name [roles] specified for parameter of operation [createUser] on MBean [Users:type=UserDatabase,database=UserDatabase] is invalid. The MBean operation does not take a parameter by that name.
	at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:576)
	at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:524)
	at org.jboss.on.plugins.tomcat.TomcatUserDatabaseComponent.createResource(TomcatUserDatabaseComponent.java:68)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:634)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)
Comment 1 mark yarborough 2012-11-12 20:22:34 UTC 
This bug needs a corresponding bug in Jira or Bz (as appropriate) owned by the plugin team. Mark Yarborough work with John Doyle to define EWS owner.
Comment 2 Michal Haško 2013-01-08 09:04:12 UTC 

*** This bug has been marked as a duplicate of bug 865459 ***