Description of problem: deployments to RHQ Server (RHQ EAP Server) is not possible Version-Release number of selected component (if applicable): rhq master (57e5b74) How reproducible: always Steps to Reproduce: 1. install rhq master server, agent and storage 2. create deployment child for rhq server (eap rhq server) - e.g. helloworld.war 3. Actual results: helloworld.war is uploaded but not deployed Expected results: test.war installed to rhq server and visible in server gui Additional info: deployments work in jon3.2.1 server.log: 12:40:16,968 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/coregui]] (http-/0.0.0.0:7080-6) org.rhq.coregui.CoreGUI PackageVersionFileUploadServlet: file was uploaded: helloworld.war 12:40:24,446 INFO [org.rhq.enterprise.server.resource.ResourceFactoryServerServiceImpl] (http-/0.0.0.0:7080-16) Received create resource response: CreateResourceResponse[RequestId=10091, Status=Failure] agent.log: 2014-06-18 12:40:24,439 INFO [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Creating resource through report: CreateResourceReport: ResourceType=[ResourceType[id=0, name=Deployment, plugin=JBossAS7, category=Service]], ResourceKey=[null] 2014-06-18 12:40:24,441 INFO [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Sending create response to server: CreateResourceResponse[RequestId=10091, Status=Failure]
This is expected. We don't allow deployments to the RHQ server, they are disabled after installation. This is to protect the server from running anything other than RHQ. Mazz, I'm closing this - please just verify that this is true.
What Jay said is absolutely true. In fact, in the RHQ/EAP 6.3 branch (which will go into master at some point) we totally cripple the deployer so nothing else can get deployed in RHQ Server. The RHQ Server is not meant to have any custom deployment units deployed in it. You should not deploy any war, ear or any other deployment unit in RHQ Server. That is unsupported.