Description of problem: engine fails to start with error org.apache.jasper.JasperException: JBWEB004062: Unable to compile class for JSP: JBWEB004061: An error occurred at line: 26 in the generated java file The type java.util.Map$Entry cannot be resolved. It is indirectly referenced from required .class files JBWEB004211: Stacktrace: org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85) org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:69) org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:451) org.apache.jasper.compiler.Compiler.compile(Compiler.java:361) org.apache.jasper.compiler.Compiler.compile(Compiler.java:339) org.apache.jasper.compiler.Compiler.compile(Compiler.java:326) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:606) jboss eap 6.3 has a known Bug 1080026 - root cause is a package name ecj Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. start ovirt engine 2. go to welcome page https://localhost/ovirt-engine 3. blow with errors above mentioned
Let's hope that this bug is fixed with a fresh RHEV-M Appliance build. We'll need to rebuild for 3.4.5 anyway and we can address this bug there.
Roy, please give the complete appliance name of the appliance you used.
/usr/share/ovirt-engine-appliance/rhevm-appliance-20150513.0-1.ova
Thanks. We actually had this bug in our 3.5 and 3.6 builds. This has been fixed in the 3.5 and 3.6 tags since yesterday. This bug can then be validated once a new RHEV-M Appliance build is ready.
Verified with: rhevm-appliance-20151119.0-1 rhevm-appliance-20151115.0-1 Both rhevm-appliance for 3.5 and 3.6 complete setup successfully and webadmin is accessible with no errors.
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://access.redhat.com/errata/RHBA-2016:0385