JBoss server rolls back all deployments on if start up times out
Issue
- The timeout reached during startup leads to unwanted behavior. Applications that had been deployed successfully before the timeout are rolled back/undeployed. It's preferable to have all deployed applications to be available even one or some of them fail. How do disable this behavior?
- When JBoss server startup times out before reaching server stability, all deployments are rolled back, including any that were deployed successfully and had been available until the timeout occurred. The server is set to an unstable state and requires restarting. The timeout is configurable through the system property
jboss.as.management.blocking.timeout
. Some customers require a different startup timeout behavior: the server should issue a warning that one or more deployments have failed and allowed any successfully deployed applications to function.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
- 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.