run-dmc hangs and times out on WildFly 11+

31 views
Skip to first unread message

Anders Rye

unread,
Oct 9, 2018, 8:40:55 AM10/9/18
to Immutant
Hi,

Calling run-dmc with certain options seems to  consistently hang during startup on WildFly 11+. Eventually causes the exception at the bottom. Did some trial and error testing:

(web/run-dmc app {:path "/some-path"}) ;fails
(web/run-dmc app {}) ;fails
(web/run-dmc app {:path nil}) ;works, for some reason 
(web/run app {:path "/some-path"}) ;works
(web/run app {}) ;works
(web/run app {:path nil}) ;works

Tested on WildFly (in docker) 10.1.0.Final (where all of the above works), 11.0.0.Final, 13.0.0.Final, 14.0.1.Final , using immutant/web 2.1.10 (with dev-war)

Are there any recommendations for which version of WildFly to use with the most recent version of immutant?

Anders
 

10:42:14,553 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 76) MSC000001: Failed to start service jboss.deployment.unit."test-0.0.1-SNAPSHOT-dev.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.unit."test-0.0.1-SNAPSHOT-dev.war".undertow-deployment: java.lang.RuntimeException: java.lang.RuntimeException: Timed out waiting for initialization to complete after 240 seconds. If you need more time, use the wunderboss.deployment.timeout sysprop.
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    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)
    at org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Timed out waiting for initialization to complete after 240 seconds. If you need more time, use the wunderboss.deployment.timeout sysprop.
    at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:252)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
    ... 8 more
Caused by: java.lang.RuntimeException: Timed out waiting for initialization to complete after 240 seconds. If you need more time, use the wunderboss.deployment.timeout sysprop.
    at org.projectodd.wunderboss.as.ServletListener.contextInitialized(ServletListener.java:141)
    at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
    at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
    at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
    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:1502)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
    at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
    ... 10 more

10:42:14,562 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "test-0.0.1-SNAPSHOT-dev.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test-0.0.1-SNAPSHOT-dev.war\".undertow-deployment" => "java.lang.RuntimeException: java.lang.RuntimeException: Timed out waiting for initialization to complete after 240 seconds. If you need more time, use the wunderboss.deployment.timeout sysprop.
    Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Timed out waiting for initialization to complete after 240 seconds. If you need more time, use the wunderboss.deployment.timeout sysprop.
    Caused by: java.lang.RuntimeException: Timed out waiting for initialization to complete after 240 seconds. If you need more time, use the wunderboss.deployment.timeout sysprop."}}

Vincent Heuken

unread,
Oct 10, 2018, 7:14:37 AM10/10/18
to Immutant
>Are there any recommendations for which version of WildFly to use with the most recent version of immutant?

I asked this on Clojurians Slack recently. The answer was "8.2.1.Final, 9.0.2.Final, and 10.1.0.Final"
https://clojurians-log.clojureverse.org/immutant/2018-09-25
Reply all
Reply to author
Forward
0 new messages