[jira] [Created] (AMBARI-22765) Possible JSP problem solution?

["Tulyakov Aleksander (JIRA)" <ji...@apache.org>]

Tulyakov Aleksander created AMBARI-22765:
--------------------------------------------

             Summary: Possible JSP problem solution?
                 Key: AMBARI-22765
                 URL: https://issues.apache.org/jira/browse/AMBARI-22765
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server, ambari-views
    Affects Versions: 2.5.2, 2.6.1
         Environment: 1) ubuntu 14.04, Ambari-2.5.2.0, HDP 2.6.2, jdk1.8.0_77
2) ubuntu 14.04, Ambari-2.6.1.0, HDP 2.6.4, jdk1.8.0_112
            Reporter: Tulyakov Aleksander


When i opened "hello-spring-view" i have got exception similar to this:
https://issues.apache.org/jira/browse/AMBARI-18918

After many time googling, i found commit with change version of jsp library: https://github.com/apache/ambari/commit/c03b6d4b01fbc336c296c9a1a92ca1308cba6ffc

I tried to fix it with change ambari-server/pom.xml
from
{code:xml}
    <dependency>
      <groupId>org.mortbay.jetty</groupId>
      <artifactId>jsp-api-2.1-glassfish</artifactId>
    </dependency>
    <dependency>
      <groupId>org.mortbay.jetty</groupId>
      <artifactId>jsp-2.1-glassfish</artifactId>
    </dependency>
{code}
to
{code:xml}
    <dependency>
      <groupId>org.eclipse.jetty</groupId>
      <artifactId>jetty-jsp</artifactId>
      <version>${jetty.version}</version>
    </dependency>
{code}

After build branch-2.6 with changes all tests passed successfully.
Then i redeployed Ambari with fixes in second environment and example works fine.

P.S. in first environment i just replace jars:
jsp-2.1-glassfish-2.1.v20100127.jar
jsp-api-2.1-glassfish-2.1.v20100127.jar

with:
com.sun.el-2.2.0.v201108011116.jar
javax.el-2.2.0.v201108011116.jar
javax.servlet.jsp-2.2.0.v201112011158.jar
javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
jetty-jsp-8.1.19.v20160209.jar
org.apache.jasper.glassfish-2.2.2.v201112011158.jar
org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
org.eclipse.jdt.core-3.7.1.jar

and it fixed this problem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)