4 Replies Latest reply on Apr 4, 2019 8:50 AM by jewellgm

    Failed to start service

    samajaypal2
    samajaypal2 Apr 2, 2019 8:29 AM

      17:53:45,719 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.subunit."ee.ear"."ee.war".undertow-deployment.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ee.ear"."ee.war".undertow-deployment.UndertowDeploymentInfoService: Failed to start service

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)

              at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)

              at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)

              at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)

              at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)

              at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)

              at java.lang.Thread.run(Thread.java:748)

      Caused by: java.lang.IllegalArgumentException: UT010009: Servlet CreditController of type class emagia.controller.CreditController does not implement javax.servlet.Servlet

              at io.undertow.servlet.api.ServletInfo.<init>(ServletInfo.java:98)

              at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:722)

              at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:275)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)

              ... 6 more

       

       

      17:53:45,797 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ee.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"ee.ear\".\"ee.war\".undertow-deployment.UndertowDeploymentInfoService" => "Failed to start service

          Caused by: java.lang.IllegalArgumentException: UT010009: Servlet CreditController of type class emagia.controller.CreditController does not implement javax.servlet.Servlet"}}

      17:53:45,812 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 43) WFLYSRV0010: Deployed "ee.ear" (runtime-name : "ee.ear")

      17:53:45,812 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

      WFLYCTL0186:   Services which failed to start:      service jboss.deployment.subunit."ee.ear"."ee.war".undertow-deployment.UndertowDeploymentInfoService: Failed to start service

      WFLYCTL0448: 3 additional services are down due to their dependencies being missing or failed

      17:53:45,828 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server

      17:53:45,843 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9090/management

      17:53:45,843 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9090

      17:53:45,843 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started (with errors) in 7772ms - Started 2861 of 3053 services (6 services failed or missing dependencies, 336 services are lazy, passive or on-demand)

      • 3365 Views
      • Tags:
        • 1. Re: Failed to start service
          jewellgm
          jewellgm Apr 2, 2019 8:33 AM (in response to samajaypal2)

          Have you embedded a servlet jar into your war or ear? If so, you may be having classloader conflict issues.  Remove that jar from your deployment, and wildfly will automatically make the servlet classes visible to your war deployment.

            • Actions
          • 2. Re: Failed to start service
            samajaypal2
            samajaypal2 Apr 3, 2019 2:58 AM (in response to jewellgm)

            i did'nt have an servlets. can you plase tell me where i have to check.

              • Actions
            • 3. Re: Failed to start service
              samajaypal2
              samajaypal2 Apr 3, 2019 6:09 AM (in response to jewellgm)

              i did'nt have any servlet jars. in my src lib folder. can you please tell me  where can  i  change or where can modify the javax.servlet.servlet jar in wildfly.

                • Actions
              • 4. Re: Failed to start service
                jewellgm
                jewellgm Apr 4, 2019 8:50 AM (in response to samajaypal2)

                If you have the web subsystem configured in your standalone.xml, then your war should have automatic visibility to the servlet jar embedded inside wildfly.  Be sure to check your ear and war for the servlet jar in the following locations:

                <ear file>/lib

                <ear file>/<war file>/WEB-INF/lib

                 

                If you find it in either of those places, remove it.

                  • Actions