Message Boards

Failed to start service jboss.undertow.deployment.default-server.default

Ramalingaiah Dudimetla, modified 3 Years ago.

Failed to start service jboss.undertow.deployment.default-server.default

New Member Posts: 22 Join Date: 3/4/20 Recent Posts
19:44:17,908 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 84) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./: java.lang.NoSuchFieldError: MODULE_FRAMEWORK_CONCURRENT_STARTUP_ENABLED
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:84)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
        at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.NoSuchFieldError: MODULE_FRAMEWORK_CONCURRENT_STARTUP_ENABLED
        at com.liferay.portal.bootstrap.ModuleFrameworkImpl._setUpInitialBundles(ModuleFrameworkImpl.java:1536)
        at com.liferay.portal.bootstrap.ModuleFrameworkImpl.startFramework(ModuleFrameworkImpl.java:407)
        at com.liferay.portal.module.framework.ModuleFrameworkUtilAdapter.startFramework(ModuleFrameworkUtilAdapter.java:99)
        at com.liferay.portal.spring.context.PortalContextLoaderListener.contextInitialized(PortalContextLoaderListener.java:291)
        at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
        at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:205)
        at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:174)
        at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
        at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
        at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
        at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:239)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:99)
        at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
        ... 6 more19:44:17,916 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./" => "java.lang.NoSuchFieldError: MODULE_FRAMEWORK_CONCURRENT_STARTUP_ENABLED
    Caused by: java.lang.NoSuchFieldError: MODULE_FRAMEWORK_CONCURRENT_STARTUP_ENABLED"}}
19:44:17,921 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
19:44:17,922 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:      service jboss.undertow.deployment.default-server.default-host./: java.lang.NoSuchFieldError: MODULE_FRAMEWORK_CONCURRENT_STARTUP_ENABLED19:44:17,952 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
19:44:17,954 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
19:44:17,954 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
19:44:17,954 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) started (with errors) in 15398ms - Started 2625 of 2852 services (2 services failed or missing dependencies, 349 services are lazy, passive or on-demand)[jboss@ESALES-APP-02 dxp]$ ps -ef|grep java
jboss    48258 48112 28 19:44 pts/0    00:00:55 /usr/java/jdk1.8.0_172/bin/java -D[Standalone] -verbose:gc -Xloggc:/data/app/dxp/jboss/standalone/log/gc.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Djgroups.bind_addr=172.30.30.211 -Djgroups.tcpping.initial_hosts=172.30.30.211[7800],172.30.30.212[7800] -d64 -Dsecmgr -Djava.security.policy=/data/app/dxp/jboss/bin/server.policy -Djboss.home.dir=/data/app/dxp/jboss -Dfile.encoding=UTF8 -Djava.net.preferIPv4Stack=true -Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false -Duser.timezone=Asia/Kolkata -server -Xms16g -Xmx16g -XX:MetaspaceSize=3g -XX:MaxMetaspaceSize=3g -XX:SurvivorRatio=6 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=15 -XX:+UseParNewGC -XXemoticonarallelGCThreads=16 -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+CMSCompactWhenClearAllSoftRefs -XX:CMSInitiatingOccupancyFraction=85 -XX:+CMSScavengeBeforeRemark -XX:+UseCompressedOops -XX:+DisableExplicitGC -XX:-UseBiasedLocking -XX:+BindGCTaskThreadsToCPUs -XX:+UseFastAccessorMethods -Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/data/app/dxp/jboss/standalone/log/server.log -Dlogging.configuration=file:/data/app/dxp/jboss/standalone/configuration/logging.properties -jar /data/app/dxp/jboss/jboss-modules.jar -mp /data/app/dxp/jboss/modules org.jboss.as.standalone -Djboss.home.dir=/data/app/dxp/jboss -Djboss.server.base.dir=/data/app/dxp/jboss/standalone -b=0.0.0.0
jboss    48511 47815  0 19:47 pts/0    00:00:00 grep --color=auto java
[jboss@ESALES-APP-02 dxp]$ ls
bkpdata14720                                                                              jboss          patching-tool-2.0.15.zip   portal-setup-wizard.properties
com.liferay.portal.search.elasticsearch6.configuration.ElasticsearchConfiguration.config  logs           patching-tool-backup       rootDir=
data                                                                                      osgi           portal-ext.properties      unicast.xml
deploy                                                                                    patching-tool  portal-ext.properties.bkp  work
[jboss@ESALES-APP-02 dxp]$ cd jboss/
[jboss@ESALES-APP-02 jboss]$ ls
appclient  bin  docs  domain  JBossEULA.txt  jboss-modules.jar  LICENSE.txt  migration  modules  standalone  version.txt  welcome-content
[jboss@ESALES-APP-02 jboss]$ cd standalone/
[jboss@ESALES-APP-02 standalone]$ ls
configuration  data  deployments  lib  log  tmp
[jboss@ESALES-APP-02 standalone]$ cd deployments/
[jboss@ESALES-APP-02 deployments]$ ls
README.txt  ROOT.war  ROOT.war.failed
[jboss@ESALES-APP-02 deployments]$ more ROOT.war.failed
"{\"WFLYCTL0080: Failed services\" => {\"jboss.undertow.deployment.default-server.default-host./\" => \"java.lang.NoSuchFieldError: MODULE_FRAMEWORK_CONCURRENT_STARTUP_
ENABLED
    Caused by: java.lang.NoSuchFieldError: MODULE_FRAMEWORK_CONCURRENT_STARTUP_ENABLED\"}}"
[jboss@ESALES-APP-02 deployments]$
what is problemthis is production issue please help me
thumbnail
Minhchau Dang, modified 3 Years ago.

RE: Failed to start service jboss.undertow.deployment.default-server.defaul

Liferay Master Posts: 598 Join Date: 10/22/07 Recent Posts
It means you didn't setup Liferay on JBoss properly.

The line numbers in your error message indicate that you're using Liferay 7.1 for the osgi folder, but that you're using Liferay 7.0 or earlier for the Liferay .war. The two need to match.