4 Replies Latest reply on Jun 28, 2012 7:44 PM by Bernd Eckenfels

    AS 7 domain robustness - process controller doesn't autorestart  app server node after a fail

    Maksym Gryevtsov Newbie



      We are evaluating whether jBoss 7 is ready for production run, and found that jboss process controller detects a fail of a java application server node process (we killed it manually), but do not  attempt to restart it automatically. Assuming that app node process might fail for some reason, for example out of memory, it's critical it will be restarted automatically. The only way we found it do it manually via CLI/console. Is there a way to force the process controller do it automatically? Is it a bug?


      We use latest 7.1.2.Final


      12:48:43,326 INFO  [org.jboss.as.process.Server:demo-jbnode1.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:demo-jbnode1'

      14:50:46,666 INFO  [org.jboss.as.process.Server:demo-jbnode1.status] (reaper for Server:demo-jbnode1) JBAS012010: Process 'Server:demo-jbnode1' finished with an exit status of 1 (after we kill the correspondent java)

      14:53:09,495 INFO  [org.jboss.as.process.Server:demo-jbnode1.status] (ProcessController-threads - 4) JBAS012017: Starting process 'Server:demo-jbnode1' (only happens after manual restart)


      With our current JBoss 4, the wrapper takes that responsibility. We use JBossNative to run it as a win service.