jsw has a feature to auto restart it managed JVM when problem occurs like: - JVM exits by itself either normal or abnormal.
- JVM hang in my case, JVM hangs due memory exhaustion, no response to jsw heartbeat, not response to normal shutdown request initiate by JSW, a kill -9 was issue as the last resort The question here how could it possible corrupted karaf cache which leads to the need for manual intervention to remove karaf/data directory to get it start again -D On Sat, Mar 23, 2013 at 3:28 PM, Achim Nierbeck <[email protected]> wrote: > Hi Dan, > > could you give us more details on why it dies with the server wrapper? > Regarding killing Karaf, that can be troublesome, but I think after a clean > reboot (without killing ;)) > it should start nicely again. > > regards, Achim > > > 2013/3/23 Dan Tran <[email protected]> >> >> Hi my karaf application, currently in development, occasionally get >> killed by java service wrapper due to many reasons. However, there >> are case it karaf just cant come back ( ie some of bundle got stuck in >> grace period or just die ). is it because of file system corruption >> due to kill -9? and nothing Karaf can do? >> >> Thanks >> >> -D > > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> > Commiter & Project Lead > blog <http://notizblog.nierbeck.de/>
