No, just a typo in where you had put them. Just miscommunication. I
failed to communicate precisely what I was seeing earlier when I brought
it up,but I thought you understood and were already changing it, and I
saw some SVN commits go by that appeared to touch the stuff I was
talking about, so I left it. Anyway, hopefully, this is the only cause
of this.
In the event that we do still see the JVM just "going away," try to
ensure that the JVM process is running in a working directory where it
can write core dumps and log files and has no resource limit setting
preventing it. We should normally see a hotspot err (hs_err_<pid>.log)
file in the case that the JVM crashes. In my experience, though, these
are extremely rare in pure Java settings.
--a.
Dave Johnson wrote:
Well, don't I feel like an ID10T now. I just committed a fix for that.
Thanks Anil!
- Dave
On Dec 5, 2005, at 11:09 AM, Anil Gangolli wrote:
Dave,
I still see the System.exit() calls I had mentioned finding in the
run() (not main()) method of the TurnoverReferersTask and this is
likely causing mysterious exits.
--a.
Dave Johnson wrote:
I added the RequestFilter back into the chain saturday and the blank
screen problems have completely disappeared, but I did get a crash
on Sunday. The JVM again disappeared without leaving any log
messages. This is significant; I haven't see crashes like this before.
- Dave
On Dec 3, 2005, at 6:30 PM, Dave Johnson wrote:
Just a word of warning. Thursday, I deployed the latest code in the
Roller trunk to my site and since then my site's main page has gone
blank three times (I restored the page by clearing the site-wide
page cache) and the site has crashed twice (the JVM crashes,
leaving no stack trace). If you want to check out the new features
you might want to do it on a test system only. I'm not sure what's
going on yet. I'll be working on isolating the problem once I get
back to work on Monday.
- Dave
