Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-556

java.lang.NoSuchFieldError: IS_SECURITY_ENABLED

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 0.8.0
    • Component/s: Build
    • Labels:
      None

      Description

      Please take a look at this log.
      https://builds.apache.org/job/PreCommit-TAJO-Build/80//consoleFull

      This bug still occurs in some cases. Any one can know how we solve this?

      2014-01-27 09:42:37,480 INFO  mortbay.log (NativeMethodAccessorImpl.java:invoke0(?)) - jetty-6.1.14
      2014-01-27 09:42:37,516 INFO  mortbay.log (NativeMethodAccessorImpl.java:invoke0(?)) - Extract jar:file:/home/jenkins/.m2/repository/org/apache/hadoop/hadoop-hdfs/2.2.0/hadoop-hdfs-2.2.0-tests.jar!/webapps/hdfs to /tmp/Jetty_localhost_50670_hdfs____.jana6a/webapp
      2014-01-27 09:42:37,714 ERROR mortbay.log (NativeMethodAccessorImpl.java:invoke0(?)) - failed jsp
      java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
      at org.apache.jasper.compiler.JspRuntimeContext.<init>(JspRuntimeContext.java:197)
      at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:150)
      at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
      at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
      at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
      at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:643)
      at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
      at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1234)
      at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
      at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:460)
      at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
      at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
      at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
      at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
      at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
      at org.mortbay.jetty.Server.doStart(Server.java:222)
      at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
      
      1. TAJO-556_2.patch
        0.4 kB
        Jaehwa Jung
      2. TAJO-556.patch
        3 kB
        Jaehwa Jung

        Issue Links

          Activity

          Hide
          jhkim Jinho Kim added a comment -

          No problem Hyunsik

          Show
          jhkim Jinho Kim added a comment - No problem Hyunsik
          Hide
          hyunsik Hyunsik Choi added a comment -

          Jinho,

          I'm sorry. I submitted the final patch. I missed that point.

          Show
          hyunsik Hyunsik Choi added a comment - Jinho, I'm sorry. I submitted the final patch. I missed that point.
          Hide
          hudson Hudson added a comment -

          SUCCESS: Integrated in Tajo-master-build #35 (See https://builds.apache.org/job/Tajo-master-build/35/)
          TAJO-556: java.lang.NoSuchFieldError: IS_SECURITY_ENABLED. (jaehwa) (jhjung: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git&a=commit&h=d97be6f2c6fce83deb3b43487b8f904be5d0b330)

          • CHANGES.txt
          • tajo-core/tajo-core-backend/pom.xml
          Show
          hudson Hudson added a comment - SUCCESS: Integrated in Tajo-master-build #35 (See https://builds.apache.org/job/Tajo-master-build/35/ ) TAJO-556 : java.lang.NoSuchFieldError: IS_SECURITY_ENABLED. (jaehwa) (jhjung: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git&a=commit&h=d97be6f2c6fce83deb3b43487b8f904be5d0b330 ) CHANGES.txt tajo-core/tajo-core-backend/pom.xml
          Hide
          blrunner Jaehwa Jung added a comment -

          Thanks Jinho Kim.
          I just committed it to master branch.

          Show
          blrunner Jaehwa Jung added a comment - Thanks Jinho Kim . I just committed it to master branch.
          Hide
          jhkim Jinho Kim added a comment -

          +1 for the patch.

          Show
          jhkim Jinho Kim added a comment - +1 for the patch.
          Hide
          tajoqa Tajo QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12625513/TAJO-556_2.patch
          against master revision 106d29c.

          +1 @author. The patch does not contain any @author tags.

          -1 tests included. The patch doesn't appear to include any new or modified tests.
          Please justify why no new tests are needed for this patch.
          Also please list what manual steps were performed to verify this patch.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. The applied patch does not increase the total number of javadoc warnings.

          +1 checkstyle. The patch generated 0 code style errors.

          -1 findbugs. The patch appears to introduce 191 new Findbugs (version 1.3.9) warnings.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 core tests. The patch passed unit tests in tajo-core/tajo-core-backend.

          Test results: https://builds.apache.org/job/PreCommit-TAJO-Build/85//testReport/
          Findbugs warnings: https://builds.apache.org/job/PreCommit-TAJO-Build/85//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core-backend.html
          Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/85//console

          This message is automatically generated.

          Show
          tajoqa Tajo QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12625513/TAJO-556_2.patch against master revision 106d29c. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The applied patch does not increase the total number of javadoc warnings. +1 checkstyle. The patch generated 0 code style errors. -1 findbugs. The patch appears to introduce 191 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in tajo-core/tajo-core-backend. Test results: https://builds.apache.org/job/PreCommit-TAJO-Build/85//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-TAJO-Build/85//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core-backend.html Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/85//console This message is automatically generated.
          Hide
          blrunner Jaehwa Jung added a comment -

          Thanks Jinho Kim.
          I uploaded the second patch.

          Show
          blrunner Jaehwa Jung added a comment - Thanks Jinho Kim . I uploaded the second patch.
          Hide
          jhkim Jinho Kim added a comment -

          Jaehwa Jung
          This issue has been fixed by TAJO-502 already. but reverted by TAJO-475.
          please refer to http://jira.codehaus.org/browse/MNG-5096

          Min Zhou
          Why did change pom.xml ?

          diff --git tajo-core/tajo-core-backend/pom.xml tajo-core/tajo-core-backend/pom.xml
          index abc217e..125a6d6 100644
          --- tajo-core/tajo-core-backend/pom.xml
          +++ tajo-core/tajo-core-backend/pom.xml
          @@ -266,7 +266,7 @@
               <dependency>
                 <groupId>org.apache.hadoop</groupId>
                 <artifactId>hadoop-hdfs</artifactId>
          -      <scope>test</scope>
          +      <type>test-jar</type>
                 <exclusions>
                   <exclusion>
                     <groupId>commons-el</groupId>
          
          Show
          jhkim Jinho Kim added a comment - Jaehwa Jung This issue has been fixed by TAJO-502 already. but reverted by TAJO-475 . please refer to http://jira.codehaus.org/browse/MNG-5096 Min Zhou Why did change pom.xml ? diff --git tajo-core/tajo-core-backend/pom.xml tajo-core/tajo-core-backend/pom.xml index abc217e..125a6d6 100644 --- tajo-core/tajo-core-backend/pom.xml +++ tajo-core/tajo-core-backend/pom.xml @@ -266,7 +266,7 @@ <dependency> <groupId> org.apache.hadoop </groupId> <artifactId> hadoop-hdfs </artifactId> - <scope> test </scope> + <type> test-jar </type> <exclusions> <exclusion> <groupId> commons-el </groupId>
          Hide
          tajoqa Tajo QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12625388/TAJO-556.patch
          against master revision 106d29c.

          +1 @author. The patch does not contain any @author tags.

          -1 tests included. The patch doesn't appear to include any new or modified tests.
          Please justify why no new tests are needed for this patch.
          Also please list what manual steps were performed to verify this patch.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. The applied patch does not increase the total number of javadoc warnings.

          +1 checkstyle. The patch generated 0 code style errors.

          +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 core tests. The patch passed unit tests in .

          Test results: https://builds.apache.org/job/PreCommit-TAJO-Build/84//testReport/
          Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/84//console

          This message is automatically generated.

          Show
          tajoqa Tajo QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12625388/TAJO-556.patch against master revision 106d29c. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The applied patch does not increase the total number of javadoc warnings. +1 checkstyle. The patch generated 0 code style errors. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-TAJO-Build/84//testReport/ Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/84//console This message is automatically generated.
          Hide
          blrunner Jaehwa Jung added a comment -

          After I checked out the latest source code from apache master, I met the same situation. So, I had to spend lots of time to resolve this issue. After checking dependencies, jasper-runtime jar file is the cause of error.It generated on tajo-core-backend, so I verified all dependencies of tajo-core-backend. But the real cause is dependencies of tajo-project.

          'mvn clean install' finished successfully, and I verified tajo on my local cluster.

          Show
          blrunner Jaehwa Jung added a comment - After I checked out the latest source code from apache master, I met the same situation. So, I had to spend lots of time to resolve this issue. After checking dependencies, jasper-runtime jar file is the cause of error.It generated on tajo-core-backend, so I verified all dependencies of tajo-core-backend. But the real cause is dependencies of tajo-project. 'mvn clean install' finished successfully, and I verified tajo on my local cluster.

            People

            • Assignee:
              blrunner Jaehwa Jung
              Reporter:
              hyunsik Hyunsik Choi
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development