Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Cannot access to Oozie Web UI with Error message below

Solved Go to solution

Cannot access to Oozie Web UI with Error message below

Explorer

Hi,

 

I just installed the CDH 6.1 on my VMs, and I've tried to access to oozie web ui.

 

But I failed with the message below.

 

{
    "errorMessage": "org.apache.jasper.JasperException: PWC6033: Error in Javac compilation for JSP\n\n

    PWC6199: Generated servlet error:\npackage javax.servlet does not exist\n\n
    PWC6199: Generated servlet error:\npackage javax.servlet.http does not exist\n\n
    PWC6199: Generated servlet error:\npackage javax.servlet.jsp does not exist\n\n
    PWC6199: Generated servlet error:\npackage org.apache.oozie.sla.service does not exist\n\n
    PWC6199: Generated servlet error:\npackage org.apache.oozie.service does not exist\n\n
    PWC6199: Generated servlet error:\npackage org.apache.oozie.service does not exist\n\n
    PWC6199: Generated servlet error:\npackage org.apache.oozie.service does not exist\n\n
    PWC6199: Generated servlet error:\npackage org.apache.oozie.service does not exist\n\n
    PWC6199: Generated servlet error:\npackage org.apache.jasper.runtime does not exist\n\n
    PWC6199: Generated servlet error:\npackage org.apache.jasper.runtime does not exist\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class JspFactory\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\npackage org.glassfish.jsp.api does not exist\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class HttpServletRequest\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class HttpServletResponse\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class ServletException\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   variable JspFactory\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class PageContext\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class HttpSession\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class ServletContext\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class ServletConfig\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class JspWriter\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class JspWriter\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class PageContext\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\npackage org.glassfish.jsp.api does not exist\n\n
    PWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n
      symbol:   variable SLAService\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n
      symbol:   variable InstrumentationService\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n
      symbol:   variable MetricsInstrumentationService\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n
      symbol:   class AuthorizationService\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n
      symbol:   variable Services\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class SkipPageException\n  location: class org.apache.jsp.index_jsp\n\n
    PWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class ServletException\n  location: class org.apache.jsp.index_jsp\n\n
    ",
    "httpStatusCode": 500
}

I've tried to set java home with exact location and reinstall the jdk files, but both didn't work. 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Re: Cannot access to Oozie Web UI with Error message below

Explorer

I solved this problem by installing openjdk-1.8.0 using yum and settnig java classpath.

 

Re: Cannot access to Oozie Web UI with Error message below

Community Manager

This worked for me with Oozie HA with haproxy running OpenJDK 1.8.   I did have to make sure the three jars were unlinked on both oozie servers in the /opt/cloudera/parcels/CDH/lib/oozie/embedded-oozie-server/dependency/ directory.   Could it be possible that you may have these jars elsewhere in the classpath for oozie, maybe in the /var/lib/oozie directory?

 

unlink ./jetty-runner-9.3.20.v20170531.jar
unlink ./javax.servlet.jsp-api-2.3.1.jar
unlink ./javax.servlet.jsp-2.3.2.jar

 

Oozie_Web_Console_and_Instances_-_Oozie_-_Cloudera_Manager_and_1__cloudera_host-10-17-100-72____ssh__and_Oozie_Web_Console.png



Robert Justice, Technical Resolution Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Learn more about the Cloudera Community:

Terms of Service

11 REPLIES 11

Re: Cannot access to Oozie Web UI with Error message below

Community Manager

Hi,

 

We have seen this with a few upgrades to CDH 6.X from CDH 5.X recently.   Could you please confirm if this was an upgrade (you had mentioned "just installed", so we would like to confirm)?   The solution for upgrades has been to:

 

1. Execute the below command on the Oozie server host command line
unlink /opt/cloudera/parcels/CDH-6.1.0-1.cdh6.1.0.p0.770702/lib/oozie/embedded-oozie-server/dependency/javax.servlet.jsp-2.3.2.jar

*note that we aim to only remove the link to the actual jar file

2.  Restart Oozie server
3.  Please check if the web ui comes up correctly.

 

This should be fixed in a future upgrade.

 

Thanks,

Robert Justice



Robert Justice, Technical Resolution Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Learn more about the Cloudera Community:

Terms of Service

Re: Cannot access to Oozie Web UI with Error message below

Explorer

 

Thank you for your reply.

 

No, I've just installed CDH 6.1 using cloudera-manager-installer.bin.

 

After the CDH 6.1 cluster has been set, I follow the instruction below to enable the oozie web UI but failed.

 

https://www.cloudera.com/documentation/enterprise/latest/topics/admin_oozie_console.html

Re: Cannot access to Oozie Web UI with Error message below

Explorer

I solved this problem by installing openjdk-1.8.0 using yum and settnig java classpath.

 

Re: Cannot access to Oozie Web UI with Error message below

New Contributor
Our CDH6.1 cluster is a fresh installation, not an upgrade, and also has the problem. I had tried your solution, canceled the unlink, but still failed . How to deal with this problem for a fresh installation of CDH cluster?

Re: Cannot access to Oozie Web UI with Error message below

Community Manager

I confirmed this problem definitely does occur, even with fresh install.   Removing the link to javax.servlet.jsp-2.3.2.jar in the/opt/cloudera/parcels/CDH/lib/oozie/embedded-oozie-server/dependency directory, and restarting, does solve it in my test environment.  The below is for the latest - CDH 6.1.1.   We will be resolving this in the CDH 6.2 release.   Could you please confirm the link is gone, on the oozie server, and confirm the oozie server was restarted? 

 

[root@host-10-17-100-72 dependency]# ls -ltr
total 0
lrwxrwxrwx 1 root root 47 Feb 7 23:58 jetty-xml-9.3.20.v20170531.jar -> ../../../../jars/jetty-xml-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-util-9.3.20.v20170531.jar -> ../../../../jars/jetty-util-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Feb 7 23:58 jetty-server-9.3.20.v20170531.jar -> ../../../../jars/jetty-server-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 44 Feb 7 23:58 javax.servlet-api-3.1.0.jar -> ../../../../jars/javax.servlet-api-3.1.0.jar
lrwxrwxrwx 1 root root 35 Feb 7 23:58 commons-el-1.0.jar -> ../../../../jars/commons-el-1.0.jar
lrwxrwxrwx 1 root root 46 Feb 7 23:58 jetty-io-9.3.20.v20170531.jar -> ../../../../jars/jetty-io-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-http-9.3.20.v20170531.jar -> ../../../../jars/jetty-http-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 55 Feb 7 23:58 jetty-annotations-9.3.20.v20170531.jar -> ../../../../jars/jetty-annotations-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 31 Feb 7 23:58 mail-1.4.7.jar -> ../../../../jars/mail-1.4.7.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 apache-jsp-9.3.20.v20170531.jar -> ../../../../jars/apache-jsp-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 53 Feb 7 23:58 jetty-util-ajax-9.3.20.v20170531.jar -> ../../../../jars/jetty-util-ajax-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 52 Feb 7 23:58 jetty-security-9.3.20.v20170531.jar -> ../../../../jars/jetty-security-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 javax.servlet.jsp-api-2.3.1.jar -> ../../../../jars/javax.servlet.jsp-api-2.3.1.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 taglibs-standard-spec-1.2.5.jar -> ../../../../jars/taglibs-standard-spec-1.2.5.jar
lrwxrwxrwx 1 root root 51 Feb 7 23:58 jetty-rewrite-9.3.20.v20170531.jar -> ../../../../jars/jetty-rewrite-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 taglibs-standard-impl-1.2.5.jar -> ../../../../jars/taglibs-standard-impl-1.2.5.jar
lrwxrwxrwx 1 root root 50 Feb 7 23:58 jetty-runner-9.3.20.v20170531.jar -> ../../../../jars/jetty-runner-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-plus-9.3.20.v20170531.jar -> ../../../../jars/jetty-plus-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-jndi-9.3.20.v20170531.jar -> ../../../../jars/jetty-jndi-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 47 Feb 7 23:58 apache-log4j-extras-1.2.17.jar -> ../../../../jars/apache-log4j-extras-1.2.17.jar
lrwxrwxrwx 1 root root 38 Feb 7 23:58 apache-jsp-8.0.33.jar -> ../../../../jars/apache-jsp-8.0.33.jar
lrwxrwxrwx 1 root root 57 Feb 7 23:58 org.eclipse.jdt.core-3.8.2.v20130121.jar -> ../../../../jars/org.eclipse.jdt.core-3.8.2.v20130121.jar
lrwxrwxrwx 1 root root 50 Feb 7 23:58 jetty-webapp-9.3.20.v20170531.jar -> ../../../../jars/jetty-webapp-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 44 Feb 7 23:58 javax.servlet.jsp-2.3.2.jar -> ../../../../jars/javax.servlet.jsp-2.3.2.jar
lrwxrwxrwx 1 root root 51 Feb 7 23:58 jetty-servlet-9.3.20.v20170531.jar -> ../../../../jars/jetty-servlet-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 49 Feb 7 23:58 apache-jstl-9.3.20.v20170531.jar -> ../../../../jars/apache-jstl-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 37 Feb 7 23:58 apache-el-8.0.33.jar -> ../../../../jars/apache-el-8.0.33.jar
lrwxrwxrwx 1 root root 50 Feb 7 23:58 jetty-client-9.3.20.v20170531.jar -> ../../../../jars/jetty-client-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-jaas-9.3.20.v20170531.jar -> ../../../../jars/jetty-jaas-9.3.20.v20170531.jar
[root@host-10-17-100-72 dependency]# unlink ./javax.servlet.jsp-2.3.2.jar

 

<RESTARTED OOZIE>

 

[root@host-10-17-100-72 dependency]# ls -l
total 0
lrwxrwxrwx 1 root root 37 Feb 7 23:58 apache-el-8.0.33.jar -> ../../../../jars/apache-el-8.0.33.jar
lrwxrwxrwx 1 root root 38 Feb 7 23:58 apache-jsp-8.0.33.jar -> ../../../../jars/apache-jsp-8.0.33.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 apache-jsp-9.3.20.v20170531.jar -> ../../../../jars/apache-jsp-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 49 Feb 7 23:58 apache-jstl-9.3.20.v20170531.jar -> ../../../../jars/apache-jstl-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 47 Feb 7 23:58 apache-log4j-extras-1.2.17.jar -> ../../../../jars/apache-log4j-extras-1.2.17.jar
lrwxrwxrwx 1 root root 35 Feb 7 23:58 commons-el-1.0.jar -> ../../../../jars/commons-el-1.0.jar
lrwxrwxrwx 1 root root 44 Feb 7 23:58 javax.servlet-api-3.1.0.jar -> ../../../../jars/javax.servlet-api-3.1.0.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 javax.servlet.jsp-api-2.3.1.jar -> ../../../../jars/javax.servlet.jsp-api-2.3.1.jar
lrwxrwxrwx 1 root root 55 Feb 7 23:58 jetty-annotations-9.3.20.v20170531.jar -> ../../../../jars/jetty-annotations-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Feb 7 23:58 jetty-client-9.3.20.v20170531.jar -> ../../../../jars/jetty-client-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-http-9.3.20.v20170531.jar -> ../../../../jars/jetty-http-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 46 Feb 7 23:58 jetty-io-9.3.20.v20170531.jar -> ../../../../jars/jetty-io-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-jaas-9.3.20.v20170531.jar -> ../../../../jars/jetty-jaas-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-jndi-9.3.20.v20170531.jar -> ../../../../jars/jetty-jndi-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-plus-9.3.20.v20170531.jar -> ../../../../jars/jetty-plus-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 51 Feb 7 23:58 jetty-rewrite-9.3.20.v20170531.jar -> ../../../../jars/jetty-rewrite-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Feb 7 23:58 jetty-runner-9.3.20.v20170531.jar -> ../../../../jars/jetty-runner-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 52 Feb 7 23:58 jetty-security-9.3.20.v20170531.jar -> ../../../../jars/jetty-security-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Feb 7 23:58 jetty-server-9.3.20.v20170531.jar -> ../../../../jars/jetty-server-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 51 Feb 7 23:58 jetty-servlet-9.3.20.v20170531.jar -> ../../../../jars/jetty-servlet-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 jetty-util-9.3.20.v20170531.jar -> ../../../../jars/jetty-util-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 53 Feb 7 23:58 jetty-util-ajax-9.3.20.v20170531.jar -> ../../../../jars/jetty-util-ajax-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Feb 7 23:58 jetty-webapp-9.3.20.v20170531.jar -> ../../../../jars/jetty-webapp-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 47 Feb 7 23:58 jetty-xml-9.3.20.v20170531.jar -> ../../../../jars/jetty-xml-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 31 Feb 7 23:58 mail-1.4.7.jar -> ../../../../jars/mail-1.4.7.jar
lrwxrwxrwx 1 root root 57 Feb 7 23:58 org.eclipse.jdt.core-3.8.2.v20130121.jar -> ../../../../jars/org.eclipse.jdt.core-3.8.2.v20130121.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 taglibs-standard-impl-1.2.5.jar -> ../../../../jars/taglibs-standard-impl-1.2.5.jar
lrwxrwxrwx 1 root root 48 Feb 7 23:58 taglibs-standard-spec-1.2.5.jar -> ../../../../jars/taglibs-standard-spec-1.2.5.jar
[root@host-10-17-100-72 dependency]# pwd
/opt/cloudera/parcels/CDH-6.1.1-1.cdh6.1.1.p0.875250/lib/oozie/embedded-oozie-server/dependency



Robert Justice, Technical Resolution Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Learn more about the Cloudera Community:

Terms of Service

Re: Cannot access to Oozie Web UI with Error message below

New Contributor

yes,I removed the link, but it still did't work. As you can see, 

 

 

[root@yd-cdh01 dependency]# ll
total 0
lrwxrwxrwx 1 root root 37 Dec 7 10:24 apache-el-8.0.33.jar -> ../../../../jars/apache-el-8.0.33.jar
lrwxrwxrwx 1 root root 38 Dec 7 10:24 apache-jsp-8.0.33.jar -> ../../../../jars/apache-jsp-8.0.33.jar
lrwxrwxrwx 1 root root 48 Dec 7 10:24 apache-jsp-9.3.20.v20170531.jar -> ../../../../jars/apache-jsp-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 49 Dec 7 10:24 apache-jstl-9.3.20.v20170531.jar -> ../../../../jars/apache-jstl-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 47 Dec 7 10:24 apache-log4j-extras-1.2.17.jar -> ../../../../jars/apache-log4j-extras-1.2.17.jar
lrwxrwxrwx 1 root root 35 Dec 7 10:24 commons-el-1.0.jar -> ../../../../jars/commons-el-1.0.jar
lrwxrwxrwx 1 root root 44 Dec 7 10:24 javax.servlet-api-3.1.0.jar -> ../../../../jars/javax.servlet-api-3.1.0.jar
lrwxrwxrwx 1 root root 48 Dec 7 10:24 javax.servlet.jsp-api-2.3.1.jar -> ../../../../jars/javax.servlet.jsp-api-2.3.1.jar
lrwxrwxrwx 1 root root 55 Dec 7 10:24 jetty-annotations-9.3.20.v20170531.jar -> ../../../../jars/jetty-annotations-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Dec 7 10:24 jetty-client-9.3.20.v20170531.jar -> ../../../../jars/jetty-client-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec 7 10:24 jetty-http-9.3.20.v20170531.jar -> ../../../../jars/jetty-http-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 46 Dec 7 10:24 jetty-io-9.3.20.v20170531.jar -> ../../../../jars/jetty-io-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec 7 10:24 jetty-jaas-9.3.20.v20170531.jar -> ../../../../jars/jetty-jaas-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec 7 10:24 jetty-jndi-9.3.20.v20170531.jar -> ../../../../jars/jetty-jndi-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec 7 10:24 jetty-plus-9.3.20.v20170531.jar -> ../../../../jars/jetty-plus-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 51 Dec 7 10:24 jetty-rewrite-9.3.20.v20170531.jar -> ../../../../jars/jetty-rewrite-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Dec 7 10:24 jetty-runner-9.3.20.v20170531.jar -> ../../../../jars/jetty-runner-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 52 Dec 7 10:24 jetty-security-9.3.20.v20170531.jar -> ../../../../jars/jetty-security-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Dec 7 10:24 jetty-server-9.3.20.v20170531.jar -> ../../../../jars/jetty-server-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 51 Dec 7 10:24 jetty-servlet-9.3.20.v20170531.jar -> ../../../../jars/jetty-servlet-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec 7 10:24 jetty-util-9.3.20.v20170531.jar -> ../../../../jars/jetty-util-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 53 Dec 7 10:24 jetty-util-ajax-9.3.20.v20170531.jar -> ../../../../jars/jetty-util-ajax-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Dec 7 10:24 jetty-webapp-9.3.20.v20170531.jar -> ../../../../jars/jetty-webapp-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 47 Dec 7 10:24 jetty-xml-9.3.20.v20170531.jar -> ../../../../jars/jetty-xml-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 31 Dec 7 10:24 mail-1.4.7.jar -> ../../../../jars/mail-1.4.7.jar
lrwxrwxrwx 1 root root 57 Dec 7 10:24 org.eclipse.jdt.core-3.8.2.v20130121.jar -> ../../../../jars/org.eclipse.jdt.core-3.8.2.v20130121.jar
lrwxrwxrwx 1 root root 48 Dec 7 10:24 taglibs-standard-impl-1.2.5.jar -> ../../../../jars/taglibs-standard-impl-1.2.5.jar
lrwxrwxrwx 1 root root 48 Dec 7 10:24 taglibs-standard-spec-1.2.5.jar -> ../../../../jars/taglibs-standard-spec-1.2.5.jar

 

 

and then I restarted the oozie server ,

 

Snipaste_2019-02-27_17-56-44.jpg

 

then I still can't open the oozie web ui, with the error:

 

{"errorMessage":"org.apache.jasper.JasperException: PWC6033: Error in Javac compilation for JSP\n\nPWC6199: Generated servlet error:\npackage javax.servlet does not exist\n\nPWC6199: Generated servlet error:\npackage javax.servlet.http does not exist\n\nPWC6199: Generated servlet error:\npackage javax.servlet.jsp does not exist\n\nPWC6199: Generated servlet error:\npackage org.apache.oozie.sla.service does not exist\n\nPWC6199: Generated servlet error:\npackage org.apache.oozie.service does not exist\n\nPWC6199: Generated servlet error:\npackage org.apache.oozie.service does not exist\n\nPWC6199: Generated servlet error:\npackage org.apache.oozie.service does not exist\n\nPWC6199: Generated servlet error:\npackage org.apache.oozie.service does not exist\n\nPWC6199: Generated servlet error:\npackage org.apache.jasper.runtime does not exist\n\nPWC6199: Generated servlet error:\npackage org.apache.jasper.runtime does not exist\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class JspFactory\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\npackage org.glassfish.jsp.api does not exist\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class HttpServletRequest\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class HttpServletResponse\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class ServletException\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   variable JspFactory\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class PageContext\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class HttpSession\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class ServletContext\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class ServletConfig\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class JspWriter\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class JspWriter\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class PageContext\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\npackage org.glassfish.jsp.api does not exist\n\nPWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   variable SLAService\n  location: class org.apache.jsp.index_jsp\n\nPWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   variable InstrumentationService\n  location: class org.apache.jsp.index_jsp\n\nPWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   variable MetricsInstrumentationService\n  location: class org.apache.jsp.index_jsp\n\nPWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class AuthorizationService\n  location: class org.apache.jsp.index_jsp\n\nPWC6197: An error occurred at line: 62 in the jsp file: \/index.jsp\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   variable Services\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class SkipPageException\n  location: class org.apache.jsp.index_jsp\n\nPWC6199: Generated servlet error:\ncannot find symbol\n  symbol:   class ServletException\n  location: class org.apache.jsp.index_jsp\n\n","httpStatusCode":500}

 

Re: Cannot access to Oozie Web UI with Error message below

Community Manager

My apologies as there were two additional jars in the final bugfix that I missed in my original suggestion.   Could you please also do the following in the /opt/cloudera/parcels/CDH/lib/oozie/embedded-oozie-server/dependency directory:

 

unlink ./jetty-runner-9.3.20.v20170531.jar

unlink ./javax.servlet.jsp-api-2.3.1.jar

 

Restart the oozie server, and please let me know if your oozie web console then functioning.

 



Robert Justice, Technical Resolution Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Learn more about the Cloudera Community:

Terms of Service

Highlighted

Re: Cannot access to Oozie Web UI with Error message below

New Contributor

I tried your solution, unlink the three jars of all hosts of my cluster, and then restarted the oozie server, but still didn't work, the dependency of oozie directory now is :

[root@qa-cdh01 dependency]# ll
total 0
lrwxrwxrwx 1 root root 37 Dec  7 10:24 apache-el-8.0.33.jar -> ../../../../jars/apache-el-8.0.33.jar
lrwxrwxrwx 1 root root 38 Dec  7 10:24 apache-jsp-8.0.33.jar -> ../../../../jars/apache-jsp-8.0.33.jar
lrwxrwxrwx 1 root root 48 Dec  7 10:24 apache-jsp-9.3.20.v20170531.jar -> ../../../../jars/apache-jsp-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 49 Dec  7 10:24 apache-jstl-9.3.20.v20170531.jar -> ../../../../jars/apache-jstl-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 47 Dec  7 10:24 apache-log4j-extras-1.2.17.jar -> ../../../../jars/apache-log4j-extras-1.2.17.jar
lrwxrwxrwx 1 root root 35 Dec  7 10:24 commons-el-1.0.jar -> ../../../../jars/commons-el-1.0.jar
lrwxrwxrwx 1 root root 44 Dec  7 10:24 javax.servlet-api-3.1.0.jar -> ../../../../jars/javax.servlet-api-3.1.0.jar
lrwxrwxrwx 1 root root 55 Dec  7 10:24 jetty-annotations-9.3.20.v20170531.jar -> ../../../../jars/jetty-annotations-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Dec  7 10:24 jetty-client-9.3.20.v20170531.jar -> ../../../../jars/jetty-client-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec  7 10:24 jetty-http-9.3.20.v20170531.jar -> ../../../../jars/jetty-http-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 46 Dec  7 10:24 jetty-io-9.3.20.v20170531.jar -> ../../../../jars/jetty-io-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec  7 10:24 jetty-jaas-9.3.20.v20170531.jar -> ../../../../jars/jetty-jaas-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec  7 10:24 jetty-jndi-9.3.20.v20170531.jar -> ../../../../jars/jetty-jndi-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec  7 10:24 jetty-plus-9.3.20.v20170531.jar -> ../../../../jars/jetty-plus-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 51 Dec  7 10:24 jetty-rewrite-9.3.20.v20170531.jar -> ../../../../jars/jetty-rewrite-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 52 Dec  7 10:24 jetty-security-9.3.20.v20170531.jar -> ../../../../jars/jetty-security-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Dec  7 10:24 jetty-server-9.3.20.v20170531.jar -> ../../../../jars/jetty-server-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 51 Dec  7 10:24 jetty-servlet-9.3.20.v20170531.jar -> ../../../../jars/jetty-servlet-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 48 Dec  7 10:24 jetty-util-9.3.20.v20170531.jar -> ../../../../jars/jetty-util-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 53 Dec  7 10:24 jetty-util-ajax-9.3.20.v20170531.jar -> ../../../../jars/jetty-util-ajax-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 50 Dec  7 10:24 jetty-webapp-9.3.20.v20170531.jar -> ../../../../jars/jetty-webapp-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 47 Dec  7 10:24 jetty-xml-9.3.20.v20170531.jar -> ../../../../jars/jetty-xml-9.3.20.v20170531.jar
lrwxrwxrwx 1 root root 31 Dec  7 10:24 mail-1.4.7.jar -> ../../../../jars/mail-1.4.7.jar
lrwxrwxrwx 1 root root 57 Dec  7 10:24 org.eclipse.jdt.core-3.8.2.v20130121.jar -> ../../../../jars/org.eclipse.jdt.core-3.8.2.v20130121.jar
lrwxrwxrwx 1 root root 48 Dec  7 10:24 taglibs-standard-impl-1.2.5.jar -> ../../../../jars/taglibs-standard-impl-1.2.5.jar
lrwxrwxrwx 1 root root 48 Dec  7 10:24 taglibs-standard-spec-1.2.5.jar -> ../../../../jars/taglibs-standard-spec-1.2.5.jar

My cluster is CDH6.1.0,  JDK8 of Oracle Version. 

 

And another problem I found is that the HA of oozie with haproxy cannot be setted in CDH6.1.0. I will post this problem in another post.

Re: Cannot access to Oozie Web UI with Error message below

Community Manager

Interesting.   I'll make sure I test on HA with OpenJDK.   Just to be sure as you mentioned HA, you did this unlink on all oozie servers behine your haproxy instance, correct?



Robert Justice, Technical Resolution Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Learn more about the Cloudera Community:

Terms of Service