4 Replies Latest reply on Mar 23, 2013 1:54 PM by Tomaz Cerar

    Missing w3c module error in EAP 6.1.0.Alpha

    Dieter Tengelmann Newbie

      Hi,

       

      The javax.api module

      modules/system/layers/base/javax/api/main/module.xml

      contains these paths

                      <path name="org/w3c/dom"/>

                      <path name="org/w3c/dom/bootstrap"/>

                      <path name="org/w3c/dom/css"/>

                      <path name="org/w3c/dom/events"/>

                      <path name="org/w3c/dom/html"/>

                      <path name="org/w3c/dom/ranges"/>

                      <path name="org/w3c/dom/stylesheets"/>

                      <path name="org/w3c/dom/traversal"/>

                      <path name="org/w3c/dom/ls"/>

                      <path name="org/w3c/dom/views"/>

                      <path name="org/w3c/dom/xpath"/>

      but there is no w3c module in the modules directory...

       

      Is this eap alpha stuff really tested? Do I miss something?

      I get exceptions like this "Caused by: org.jboss.modules.ModuleNotFoundException: org.w3c.css.sac:main", when I want to start my application...

       

      Best regards,

      Dieter

        • 1. Re: Missing w3c module error in EAP 6.1.0.Alpha
          jaikiran pai Master

          Dieter Tengelmann wrote:

           

          Hi,

           

          The javax.api module

          modules/system/layers/base/javax/api/main/module.xml

          contains these paths

                          <path name="org/w3c/dom"/>

                          <path name="org/w3c/dom/bootstrap"/>

                          <path name="org/w3c/dom/css"/>

                          <path name="org/w3c/dom/events"/>

                          <path name="org/w3c/dom/html"/>

                          <path name="org/w3c/dom/ranges"/>

                          <path name="org/w3c/dom/stylesheets"/>

                          <path name="org/w3c/dom/traversal"/>

                          <path name="org/w3c/dom/ls"/>

                          <path name="org/w3c/dom/views"/>

                          <path name="org/w3c/dom/xpath"/>

          but there is no w3c module in the modules directory...

           

          path name != module name. i.e. they don't mean the same.

           

          Here's what it actually looks like:

           

          <module xmlns="urn:jboss:module:1.0" name="javax.api">
              <dependencies>
                  <module name="system" export="false">
                      <exports>
                          <include-set>
          ...
                              <path name="org/w3c/dom"/>
                              <path name="org/w3c/dom/bootstrap"/>
                              <path name="org/w3c/dom/css"/>
                              <path name="org/w3c/dom/events"/>
                              <path name="org/w3c/dom/html"/>
                              <path name="org/w3c/dom/ranges"/>
                              <path name="org/w3c/dom/stylesheets"/>
                              <path name="org/w3c/dom/traversal"/>
                              <path name="org/w3c/dom/ls"/>
                              <path name="org/w3c/dom/xpath"/>
                              <path name="org/xml/sax"/>
                              <path name="org/xml/sax/ext"/>
                              <path name="org/xml/sax/helpers"/>
                          </include-set>
                      </exports>
                  </module>
              </dependencies>
          </module>
          

           

          So the javax.api module is depending on the "system" module (which is a special module) and is expecting the system module to export those "paths" from within that module. Take a look at the JBoss Modules documentation for further details https://docs.jboss.org/author/display/MODULES/Home

           

           

          Dieter Tengelmann wrote:

           

          Is this eap alpha stuff really tested?

          Yes it is.

           

           

           

          Dieter Tengelmann wrote:

           

          I get exceptions like this "Caused by: org.jboss.modules.ModuleNotFoundException: org.w3c.css.sac:main", when I want to start my application...

           

          Best regards,

          Dieter

          Please post the entire exception stacktrace. Are you adding a dependency on some module named "org.w3c.css.sac" in your deployment?

          • 2. Re: Missing w3c module error in EAP 6.1.0.Alpha
            Tomaz Cerar Master

            I think this deployment error is coused by something else.

             

            we used to have org.w3c.css.sac module in our distro but it is long gone.

             

            it was removed as part of https://github.com/jbossas/jboss-as/pull/1949.

             

            maybe you just need to update your deployment not to use this dependancy anymore.

             

             

             

            --

            tomaz

            • 3. Re: Missing w3c module error in EAP 6.1.0.Alpha
              Dieter Tengelmann Newbie

              I don't have a direct reference to this module, neither in MANIFEST, nor in jboss-deployment-structure, this is the full stack trace:

               

              12:54:29,945 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-9) MSC00001: Failed to start service jboss.module.service."deployment.tengelmann.ear.dieter-web.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.tengelmann.ear.etm

              s-web.war".main: JBAS018759: Failed to load module: deployment.tengelmann.ear.dieter-web.war:main

                      at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:92) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.

              2.0.Alpha1-redhat-4]

                      at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.

              GA]

                      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]

                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]

                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]

                      at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]

              Caused by: org.jboss.modules.ModuleNotFoundException: org.w3c.css.sac:main

                      at org.jboss.modules.Module.addPaths(Module.java:853) [jboss-modules.jar:1.2.0.CR1]

                      at org.jboss.modules.Module.link(Module.java:1194) [jboss-modules.jar:1.2.0.CR1]

                      at org.jboss.modules.Module.relinkIfNecessary(Module.java:1222) [jboss-modules.jar:1.2.0.CR1]

                      at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:226) [jboss-modules.jar:1.2.0.CR1]

                      at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:71) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]

                      ... 5 more

               

              ############################

               

              I've tested it also in 7.1.3 (self-built), the org/w3c/css/sac module isn't there either, stack trace there:

               

              ############################

               

              23:58:04,089 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.module.service."deployment.tengelmann.ear.dieter-web.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.tengelmann.ear.dieter-web.war".main: JBAS018759: Laden des Moduls fehlgeschlagen: deployment.tengelmann.ear.dieter-web.war:main

                  at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:92) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]

                  at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                  at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]

                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]

                  at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]

              Caused by: org.jboss.modules.ModuleNotFoundException: Module org.w3c.css.sac:main is not found in local module loader @6261b548 (roots: /home/tengelmann/opt/jboss7/jboss-as-7.1.3/modules)

                  at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)

                  at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)

                  at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)

                  at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)

                  at org.jboss.modules.Module.addPaths(Module.java:851)

                  at org.jboss.modules.Module.link(Module.java:1206)

                  at org.jboss.modules.Module.relinkIfNecessary(Module.java:1235)

                  at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)

                  at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:71) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]

                  ... 5 more

              ####################

               

              In 7.1.1 my application works fine...? I've got a sac.jar and a cssparser.jar in my ear's lib folder, but no jboss module is addressed explicitly...

              • 4. Re: Missing w3c module error in EAP 6.1.0.Alpha
                Tomaz Cerar Master

                How did you do upgrade to new version?

                 

                Did you copy any modules from old version?

                Do you maybe provide any custom module that you copy into modules directory?

                Do you modify any exisiting module?

                 

                can you paste manifest.mf & jboss-deployment-structure.xml from both ear and war?

                 

                 

                 

                 

                --

                tomaz