Hi John, Many methods exist. Your app could have its own logs (like ofbiz). Java -XDebug, specialized tools like JMeter for load testing. The resources on this are numerous. Then again, debugging any environment after a crash is a challenge. You can apply the same question to LAMP, RoR, Linux, Windows or whatever. It's all about being familiar with the environment and the tools and methods really.
Taher Alkhateeb On Saturday, 9 April 2016, John Spikowski <[email protected]> wrote: > Disclaimer: Not trying to sound negative. > > How do you debug this monster after a crash? > > > > On Sat, 2016-04-09 at 12:49 +0300, Taher Alkhateeb wrote: > > John, > > > > You're confusing VM with JVM. And if you think Java is unstable perhaps > > read into it some more. Java is the most powerful eco > > -system for business on the planet! > > > > Taher Alkhateeb > > On Apr 9, 2016 12:46 PM, "John Spikowski" <[email protected] > <javascript:;>> wrote: > > > > > My biggest concern using Java is its fragile VM environment. What do > you > > > tell a client when the Java balloon 'pops' and everyone goes 500? > > > > > > On Sat, 2016-04-09 at 11:16 +0200, Jacques Le Roux wrote: > > > > Hi, > > > > > > > > The OFBIZ-VM crashed, so the demos were down, restarting... > > > > > > > > Jacques > > > > > > > > > > > > > > > >
