Can't get wildfly bundle to install

Q&A
1

Hello,

I’m attempting to install 7.4.3 with wildfly. I installed java and then extracted the wildfly bundle and attempted to run the installed script. H2 configuration works (and so does mysql when I tried an external DB), It spins up wildfly, then attempts to start JBossWS5.1.5Final, hangs for 5 minutes, times out, and dies. This is a fresh install on a brand new Windows Server 2012 machine. During the 5 minutes, wildfly’s homepage is accessible via localhost:8080, but bonita is not. I’ve added java to the path (both ways, only 1 version of java on the machine), but other than that it’s just the java 8 install defaults.

I can get the tomcat bundle to spin up and access bonita, but we’ll eventually need the SQL Server DB so I’m trying to build my environment on wildfly from the start.

Stack:

Windows Server 2012
Java 8 (v. 131)

Errors:

2017-05-25 08:31:45,447 INFO  [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6) 
2017-05-25 08:35:47,954 WARN  [org.jboss.as.domain.management.security] (default I/O-2) WFLYDM0113: Generated self signed certificate at C:\BonitaBPM\server\standalone\configuration\application.keystore. Please note that self signed certificates are not secure, and should only be used for testing purposes. Do not use this self signed certificate in production.

2017-05-25 08:36:15,206 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
    ("core-service" => "management"),
    ("management-interface" => "http-interface")
]'
2017-05-25 08:36:20,209 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0190: Step handler org.jboss.as.server.DeployerChainAddHandler$FinalRuntimeStepHandler@3b8fe71f for operation {"operation" => "add-deployer-chains","address" => []} at address [] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException
	at org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:498)
	at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1369)
	at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1328)
	at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1301)
	at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1185)
	at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:767)
	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:644)
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
	at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329)
	at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:493)
	at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:387)
	at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:349)
	at org.jboss.as.server.ServerService.boot(ServerService.java:397)
	at org.jboss.as.server.ServerService.boot(ServerService.java:366)
	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
	at java.lang.Thread.run(Unknown Source)
2

GooglWebSearch told me this:

https://mirocupak.com/enabling-long-deployments-on-wildfly/

regards
Seán

PS: As this reply offers an answer your question, and if you like it, please Mark UP and/or as Resolved.

3

Thanks to Sean’s link, I was able to find that the problem was definitely a timeout. The difference from the link above is that the file it says to update is autogenerated and clobbered every time you start the process.

To fix this error, go to the file [BonitaDir]/setup/wildfly-templates/standalone.xml.

Find this bit (around line 413):

<subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0"> <!-- 'deployment-timeout' value can be increased if your startup is too long to fit, because there are too many BPM elements to restart --> <deployment-scanner path="deployments" relative-to="jboss.server.base.dir"...

And increase the deployment timeout to 1500. (Or whatever).

Also find this bit (around line 34):

<system-properties>

And add this property:

<property name="jboss.as.management.blocking.timeout" value="1500"/>.

4

Good. That was quite helpful. I guess I didn’t google the right stuff. I was confused because I assumed the default configuration would work. I’m going to write up the solution, but +1 to you.