Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10615

Duplicate layer 'base' in integration/elytron testsuite

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Minor
    • None
    • 13.0.0.Final
    • Test Suite
    • None

    Description

      Testsuite wildfly/testsuite/integration/elytron has workarounded module path problem:

      MSC000001: Failed to start service jboss.patching.manager: org.jboss.msc.service.StartException in service jboss.patching.manager: java.lang.IllegalStateException: Duplicate layer 'base'
	at org.jboss.as.patching.installation.InstallationManagerService.start(InstallationManagerService.java:106)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
	at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Duplicate layer 'base'
	at org.jboss.as.patching.installation.LayersFactory$ProcessedLayers.addLayer(LayersFactory.java:305)
	at org.jboss.as.patching.installation.LayersFactory.processRoot(LayersFactory.java:182)
	at org.jboss.as.patching.installation.LayersFactory.process(LayersFactory.java:127)
	at org.jboss.as.patching.installation.LayersFactory.load(LayersFactory.java:86)
	at org.jboss.as.patching.installation.InstallationManagerImpl.<init>(InstallationManagerImpl.java:47)
	at org.jboss.as.patching.installation.InstallationManager.load(InstallationManager.java:185)
	at org.jboss.as.patching.installation.InstallationManagerService.load(InstallationManagerService.java:128)
	at org.jboss.as.patching.installation.InstallationManagerService.start(InstallationManagerService.java:63)
	... 8 more

      This is currently workarounded using following in pom.xml:

          <!-- let's override the module.path parent configuration with dummy value, to avoid the "IllegalStateException: Duplicate layer 'base'" -->
    <module.path>foo</module.path>

      But this prevent using `org.jboss.as.test.module.util.TestModule`, as it try to put created module into "foo", which fails - adding tests using custom modules requires removing this workaround.

      The reason is target/wildfly/modules is twice in module.path system property (when in InstallationManagerService):

      /home/jkalina/work/wildfly/testsuite/integration/elytron/target/wildfly/modules:
/home/jkalina/work/wildfly/testsuite/integration/elytron/target/wildfly/modules:
/home/jkalina/work/wildfly/testsuite/integration/elytron/target/modules

      Note: when reading module.path from the test (regardless RunAsClient is used or not), the value is correct:

      /home/jkalina/work/wildfly/testsuite/integration/elytron/target/wildfly/modules:
/home/jkalina/work/wildfly/testsuite/integration/elytron/target/modules

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFARQ-51 modulePath without WILDFLY_HOME/modules should be possible

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-3992 InstallationManagerService should not allow duplicate module paths

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-10631 Duplicate layer 'base' in clustering testsuite

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              jkalina@redhat.com Jan Kalina (Inactive)
              jkalina@redhat.com Jan Kalina (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: