Description of problem: Clean installtion of engine + reports and dwh engine and dwh service are up. reports portal is unaccessible Version-Release number of selected component (if applicable): rhevm-dwh-setup-3.4.1-1.el6ev.noarch rhevm-reports-3.4.1-1.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1. rhevm-setup , make sure that dwh and reports rpms are installed 2. 3. Actual results: engine and dwh are up and running reports portal is not accessible Expected results: all up Additional info:
Created attachment 914235 [details] sever.log
Created attachment 914236 [details] engine.log
log snippet: ============ 2014-07-02 18:22:20,799 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'http\://saxon.sf.net/jaxp /xpath/om: net.sf.saxon.xpath.XPathFactoryImpl' for service type 'javax.xml.xpath.XPathFactory' 2014-07-02 18:22:20,944 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."ovirt-engine-re ports.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."ovirt-engine-reports.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "ovirt-engine-reports.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server.jar:7.4.0.Final-redhat-15] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc.jar:1.1.5.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011236: No spring integration jar found at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:206) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server.jar:7.4.0.Final-redhat-15] ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011236: No spring integration jar found at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.getResteasySpringVirtualFile(JaxrsSpringProcessor.java:136) at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:202) ... 6 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011236: No spring integration jar found at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.getResteasySpringVirtualFile(JaxrsSpringProcessor.java:111) ... 7 more
This doesn't make any sense. This is a very basic scenario that has not had any problems in the last months. What repos are you using to install? What jboss version? Yaniv
You are using a non supported jboss version: jbossas-standalone-7.4.0 (EAP-6.3.0) It's no wonder it doesn't work, please make sure you follow the installation instructions for 3.4. Yaniv
Juan, do you have any insights to way this is happening on the new jboss? Yaniv
It looks like during the deployment of the application Resteasy is detecting some Spring beans, and is trying to activate the Resteasy integration support, and that is failing. I think that the reports application shouldn't use the version of Resteasy provided by the application server, as they include their own version (Jersey, I believe), but I thought that they are already excluding the resteasy dependencies. The Spring integration can be disabled adding this to the web.xml of the application: <context-param> <param-name>org.jboss.as.jaxrs.disableSpringIntegration</param-name> <param-value>true<param-value> </context-param>
Note that the Resteasy/Spring integration was added recently, in EAP 6.3.0 CR1, in order to fix 1019161.
Tarq, Can you please check whether the workaround suggested in comment #10 works ?
Please add: <context-param> <param-name>org.jboss.as.jaxrs.disableSpringIntegration</param-name> <param-value>true</param-value> </context-param> The previous snippet had a mistake. Yaniv
i added <context-param> <param-name>org.jboss.as.jaxrs.disableSpringIntegration</param-name> <param-value>true</param-value> </context-param> to: /var/lib/ovirt-engine-reports/ovirt-engine-reports.war/WEB-INF/web.xml and it worked
can't test right now because engine-setup doesn't work with reports: https://bugzilla.redhat.com/show_bug.cgi?id=1114914
Need to test on a vt release. moving to MODIFIED for now. Yaniv
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-0176.html