You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2018/10/08 21:29:00 UTC

[jira] [Commented] (TEZ-3961) Tez UI web.xml tries to reach out to java.sun.com for validation after moving to jetty-9

    [ https://issues.apache.org/jira/browse/TEZ-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642516#comment-16642516 ] 

Jonathan Eagles commented on TEZ-3961:
--------------------------------------

[~kshukla], this looks similar to YARN-8401. Can you provide a patch?

> Tez UI web.xml tries to reach out to java.sun.com for validation after moving to jetty-9
> ----------------------------------------------------------------------------------------
>
>                 Key: TEZ-3961
>                 URL: https://issues.apache.org/jira/browse/TEZ-3961
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.9.1
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>            Priority: Major
>
> Tez UI can throw a 503 error when hosted on a server that cannot reach public IPs like java.sun.com which are listed as servers for DTDs in web.xml.  This behavior change comes from moving to jetty 9 (Tez and Hadoop 3.0) which removed provided schemas that were being shipped with earlier versions. It is suboptimal even in cases where public IPs are accessible to fetch the DTD for a very very simple web.xml file. We can choose to either remove the DTD validation or add dependency explicitly to org.eclipse.jetty.toolchain » jetty-osgi-servlet-api to allow for this jetty change to not affect the behavior of tez-ui.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)