All geek questions in one place

Exception of simultaneous timeout when starting the Jboss Wildfly 9.02 server

I am new to jboss server. When I try to deploy the .war file to the server, the following exception gets printed to the console:

6:38:04,388 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") ]' 16:38:05,642 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Stopped Driver service with driver-name = Aerobay.war_com.mysql.jdbc.Driver_5_1 16:38:09,548 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0190: Step handler org. jboss.as.server.DeployerChainAddHandler$FinalRuntimeStepHandler@ 5f88823f 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:396) at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1384) at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1332) at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1292) at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1180) at org.jboss.as.controller.AbstractOperationContext.handleContainerStabilityFailure(AbstractOperationContext.java:964) at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:590) at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1183) at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:453) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:327) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:313) at org.jboss.as.server.ServerService.boot(ServerService.java:384) at org.jboss.as.server.ServerService.boot(ServerService.java:359) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:271) at java.lang.Thread.run(Thread.java:745)

Thanks in advance for your help!

+7
source share
9 answers

I had the same problem when I tried to deploy the WAR file on my Red Hat Jboss EAP 7.0.

But the server was integrated into my IDE (Eclipse Neon), and the problem arose only in Debug-Modus.

I managed to solve the problem by removing all breakpoints, after which I started the server again.

+19
source

Try to increase the latency by adding the java option "blocking.timeout". You can do this in bin / standalone.conf.bat (depending on how you configure wildfly) by adding the line:
set "JAVA_OPTS =% JAVA_OPTS% -Djboss.as.management.blocking.timeout = 600
Change the number if it is not enough.

+11
source

increasing the timeout does not solve the root cause of the problem. You need to check the reason for the block time and solve the problem. Perhaps in some cases the solution should increase the wait time.

In most cases, increasing resources is a poor way to solve problems. I had this case, Wildfly had a lot of time to download. I increased the timeout to 600 and solved the problem, but still had problems loading the wildlife, which was so annoying.

 2018-03-26 07:50:36,523 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 '[("path" => "xxxxxxxxxxxxxxxx")]'

Finally, I checked the reason for the lock and found that this block was caused by the decision of the network node (NAS storage is defined as a path in wildfly).

I went over to network setup and found that my local DNS was set incorrectly. I added local DNS instead of public DNS, and the problem with the block disappeared. Hope this helps

Relations Sleem

+3
source

When I tried to debug and started the server with debug mode, the following error appeared:

 16:19:50,096 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS013412: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'deploy' at address '[("deployment" => "ViprWeb.war")]' 16:19:50,096 ERROR [org.jboss.as.server] (management-handler-thread - 1) JBAS015870 16:20:00,117 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS013413: Timeout after [5000] seconds waiting for service container stability while finalizing an operation.

I deleted all my breakpoints and restarted my jboss server and it solved the problem.

+2
source

just increase the wait time in standalone.conf.bat to set how to set "JAVA_OPTS =% JAVA_OPTS% -Djboss.as.management.blocking.timeout = 600 This worked for me.

+1
source

I had the same problem. Then I killed the Kaspersky process and it helped!

0
source

I solved a similar problem and succeeded only in uninstalling applications. This provided a clean environment for restarting Wildfly and launching the management and http service. Then deploy the / WARs applications and determine what brought you into this state.

In my case, these were transactions that wanted to restore and delete those from the database in order to solve the problem so that the bot reappears.

0
source

One of the reasons I discovered was if you run in debug mode and somehow, if the scroll lock is turned on / off on the console tab, this happens. Moreover, on the console tab, if your mouse scrolls upside down, the scroll lock will be set, and then you will encounter this problem ....

Check your observations and update them so that it also helps others ...

0
source

Same problem with netbeans

but I didn’t have break points. Running jboss from the command line helped me

  • Stop jboss
  • Close Netbeans
  • open command line
  • Go to jboss> bin> folder
  • type: standalone.bat (this is the beginning of jboss)
  • open netbeans
  • worked fine!

    Hope this helps someone else.
0
source

Source: https://habr.com/ru/post/1237328/

More articles:


All Articles