Skip to content

Oozie UI on release label 5.14.2 throwing tomcat error

0

When trying to access the oozie UI on the stated release label, the following error shows up, even with oozie installed and running, how to solve please?

HTTP Status 500 - java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem;
type Exception report

message java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem;

description The server encountered an internal error that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem;
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:400)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
	org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:636)
	org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:588)
	org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
	org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)
root cause

java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem;
	org.apache.jasper.compiler.JDTJavaCompiler$2.acceptResult(JDTJavaCompiler.java:442)
	org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:480)
	org.apache.jasper.compiler.JDTJavaCompiler.compile(JDTJavaCompiler.java:503)
	org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:368)
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:437)
	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:608)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:360)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	org.apache.oozie.servlet.AuthFilter$2.doFilter(AuthFilter.java:171)
	org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:636)
	org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:588)
	org.apache.oozie.servlet.AuthFilter.doFilter(AuthFilter.java:176)
	org.apache.oozie.servlet.HostnameFilter.doFilter(HostnameFilter.java:86)

asked 2 years ago114 views

1 Answer
0

The error you're encountering with the Oozie UI on Amazon EMR release label 5.14.2 appears to be related to a Java compilation issue, specifically with the Eclipse JDT compiler used by Jasper for JSP compilation.

To resolve this issue, you can try the following steps:

  1. Ensure that the correct version of Java is being used by Oozie. You can check and configure the Java version for Oozie Server by setting the JAVA_HOME environment variable in the oozie-env classification.

  2. Verify that all the necessary Java dependencies are present and correctly configured in the Oozie installation directory.

  3. Check if there are any conflicting JAR files in the Oozie lib directory that might be causing version incompatibilities with the Eclipse JDT compiler.

  4. Consider upgrading to a more recent version of Amazon EMR if possible, as newer versions may have resolved this issue. For example, EMR 7.1.0 includes upgrades to components like Netty and Jetty, which might help resolve compatibility issues.

  5. If the problem persists, you may need to manually update the Eclipse JDT compiler JAR file in the Oozie lib directory to a version that is compatible with your current setup.

  6. Restart the Oozie server after making any changes to ensure they take effect.

If these steps don't resolve the issue, you may need to contact AWS support for further assistance, as this could be a specific issue related to the EMR 5.14.2 release label.
Sources
Configure Java version for Oozie - Amazon EMR
Amazon EMR 7.1.0 - Oozie changes - Amazon EMR

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.