Bug #1974


If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayed

Added by François ARMAND over 12 years ago. Updated about 7 years ago.

System integration
Target version:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Name check:
Fix check:


Today, if there is an initialisation error in the inventory endpoint webapp or in Rudder webapp, the application container is nonetheless started but the application does not work. That is the expected behaviour (a servlet container may and generally run several application, it won't be good to have an error on one of them to shutdown the whole thing).

But in our case, we have one application container by application, and we manage the full environment. So it would be much much much more easy to diagnosis a boot error for an admin if the whole application was clearly stopped.

Option I see for now:

  • a System.exit(Int)
    • but that's bad because it brutally stops the servlet container, maybe letting open resources not cleaned
  • a container proprietary method (to be investigated for Jetty)
  • a syscall to a shell script that call the normal app container shutdown (well, I know, it's ugly, but it's the most configurable for an admin who want to add things for that case and portable and simple)

Subtasks 1 (0 open1 closed)

Bug #10654: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayedReleasedFrançois ARMANDActions

Related issues 5 (0 open5 closed)

Related to Rudder - Architecture #2630: Rudder Webapp and Rudder Inventory should be two different applicationRejectedActions
Related to Rudder - Bug #10567: Infinite "rudder is loading" page if rudder-init didn't runReleasedNicolas CHARLESActions
Related to Rudder - Bug #15387: Clean-up Jetty abort on bootReleasedVincent MEMBRÉActions
Has duplicate Rudder - Bug #1466: Rudder should halt on fatal errors during initializationRejected2011-07-15Actions
Has duplicate Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)RejectedActions

Also available in: Atom PDF