Hi, On Tue, 30 Apr 2002 15:27, Serge Knystautas wrote: > Someone on the james user list reported this problem, and I wasn't sure > if it's been patched... they're running against the james 2.0a2 release, > which means they're using mid-Nov 2001 snapshots from Avalon if that > helps. Otherwise just thought I should share this user's notes.
It is difficult to see where exactly the problem is - looks like something somewhere is chewing up system memory and I am having a difficult time reproducing it or locating it. Is there a script or something that can reproduce the problem? -- Cheers, Peter Donald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
