Hi Andrzej, Thanks again. Its interesting. I did create the Child JVM with 200m, 1 GB, 2 GB, 3 GB and finally 4 GB Heap space with min and max set to the same.
The error is reproducible. Then again, 7 out of 8 jobs complete successfully in 10 mins and this one job takes more than 30 mins to fail. This is the strange thing and I'm out of all options now. :-( Let me play around more with GC settings. Thanks, Venkat --- Andrzej Bialecki <[EMAIL PROTECTED]> wrote: > Venkat Seeth wrote: > > Hi Devraj, > > > > The log file for key-value pairs are huge? If you > can > > tell me what are you looking for I can mine and > send > > the relevant information. > > > > 343891695 2007-02-20 18:37 seq.log > > > > This time aroung I get the following error: > > > > java.lang.OutOfMemoryError: GC overhead limit > exceeded > > > > > This message is so curious I went and googled for > it. Additional > information on this is here: > > http://java.sun.com/j2se/1.5.0/docs/guide/vm/gc-ergonomics.html > > Look at the point 3. - the time-limit setting seems > to be related (from > reading the JVM sources ;) ) with this error > message. > > All in all, your GC is overworked .. ;) > > -- > Best regards, > Andrzej Bialecki <>< > ___. ___ ___ ___ _ _ > __________________________________ > [__ || __|__/|__||\/| Information Retrieval, > Semantic Web > ___|||__|| \| || | Embedded Unix, System > Integration > http://www.sigram.com Contact: info at sigram dot > com > > > ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367
