Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-404

ClassNotFound error in Undertow subsystem when security manager is enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.0.DR7
    • 7.0.0.DR4, 7.0.0.DR5
    • Undertow
    • None
    • Hide
      # just run following command:
      ./standalone.sh -secmgr
      # and check the console (or log file)
      
      Show
      # just run following command: ./standalone.sh -secmgr # and check the console (or log file)

      When running EAP 7 with security manager enabled I see following ERROR in the log:

      13:56:47,794 ERROR [org.apache.jasper] (ServerService Thread Pool -- 55) JBWEB005034: Error loading core class: java.lang.ClassNotFoundException: org.apache.jasper.runtime.ProtectedFunctionMapper$1 from [Module "io.undertow.jsp:main" from local module loader @3abfe836 (finder: local module finder @2ff5659e (roots: /home/jcacek/test/700DR5/jboss-eap-7.0/modules,/home/jcacek/test/700DR5/jboss-eap-7.0/modules/system/layers/base))]
      	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
      	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
      	at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
      	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
      	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
      	at org.apache.jasper.security.SecurityClassLoad.securityClassLoad(SecurityClassLoad.java:58)
      	at org.apache.jasper.compiler.JspRuntimeContext.<clinit>(JspRuntimeContext.java:85)
      	at java.lang.Class.forName0(Native Method)
      	at java.lang.Class.forName(Class.java:344)
      	at org.wildfly.extension.undertow.UndertowSubsystemAdd.performBoottime(UndertowSubsystemAdd.java:85)
      	at org.jboss.as.controller.AbstractBoottimeAddStepHandler.performRuntime(AbstractBoottimeAddStepHandler.java:112)
      	at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
      	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:822)
      	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:620)
      	at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:373)
      	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:349)
      	at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:359)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:745)
      	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
      

      This behavior was reproduced in DR4 and DR5.
      The DR2 and DR3 versions seem to be OK.

              tomazcerar Tomaž Cerar (Inactive)
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: