Re: Anyone seen this?

[Leo Simons <le...@apache.org>]

Adam Jack wrote:
> Any clue when they started, or what they were? Can you link start time to
> the timestamps in the gump build log to correlate to a project?

yep, and I can do more than that:

[lsimons /proc/16903]$ pwd
/proc/16903
[lsimons /proc/16903]$ ls -al | grep cwd
lrwxrwxrwx    1 lsimons  gump            0 Aug  1 13:00 cwd -> 
/data/gump/ant
[lsimons /proc/16903]$ ps -aux | grep java
lsimons  16903 87.6  0.4 235716 1272 ?       SN   Jul31 1380:50 java 
-Xbootclass
[lsimons /proc/16903]$ cat maps > ~/bad-process-memory-map.txt

that's the ant build itself if I'm not mistaken. I'm at a loss as to 
what's causing this. I also can't tell when this started as I was on 
vacation and the machine hung up in my absence. If anyone recalls seeing 
the gump instance on my machine go down, that'd pinpoint the day. Also, 
if anyone feels like doing more debugging, I'll get you access to the 
machine.

grz,

- Leo

Re: Anyone seen this?

[Stefan Bodewig <bo...@apache.org>]

On Fri, 01 Aug 2003, Leo Simons <le...@apache.org> wrote:

> that's the ant build itself if I'm not mistaken.

cat cmdline would tell you if you wanted to be sure, but it looks a
lot like dist-ant or test-ant.  Does the log indicate where the
process is hanging?

In either case, some change in Ant could have triggered a VM bug
(RedHat 8 is not exactly Java's favorite Linux distribution).

Stefan