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

wildfly 27 war file deployment issue

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • None
    • REST
    • None
    • ---
    • ---

      Hi Team,

      we are trying to upgrade the wildfly from 23 to 27, while deploying our application war file ("dsearch.war"), we are getting the below ModuleNotFoundException for the module "org.jboss.resteasy.resteasy-spring", the same war works fine in the wildly23 and it is failing in the 27 version, could you let us know even though all dependent jars are already bundled in the war file why it is falling.

      I don't wish to add dependencies in the jboss-deployment-structure.xml file. I just want to instruct wildlfy to give priority to my application bundled jar files (both interface and implementation files), if wildlfy doesn't find then let it use wildfly's

      2022-11-14 18:22:05,557 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."dsearch.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."dsearch.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "dsearch.war"
          at org.jboss.as.server@19.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
          at org.jboss.msc@1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
          at org.jboss.msc@1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
          at org.jboss.msc@1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
          at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
          at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
          at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
          at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
          at java.base/java.lang.Thread.run(Thread.java:834)
      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.modules.ModuleNotFoundException: org.jboss.resteasy.resteasy-spring
          at org.jboss.as.jaxrs@27.0.0.Final//org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:202)
          at org.jboss.as.server@19.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
          ... 8 more
      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.modules.ModuleNotFoundException: org.jboss.resteasy.resteasy-spring
          at org.jboss.as.jaxrs@27.0.0.Final//org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.getResteasySpringVirtualFile(JaxrsSpringProcessor.java:132)
          at org.jboss.as.jaxrs@27.0.0.Final//org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:198)
          ... 9 more
      Caused by: org.jboss.modules.ModuleNotFoundException: org.jboss.resteasy.resteasy-spring
          at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:301)
          at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:287)
          at org.jboss.as.jaxrs@27.0.0.Final//org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.getResteasySpringVirtualFile(JaxrsSpringProcessor.java:94)
          ... 10 more

              jperkins-rhn James Perkins
              anareddy1507 Ananda Reddy C (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: