Re: [Exist-open] Java GC error

[Dannes W. <da...@ex...>]

On 13 Jul 2010, at 20:15 , Mike Ferrando wrote:
> An error occurred: GC overhead limit exceeded

woops, did not see that one before. From http://confluence.atlassian.com/display/DOC/Fix+Out+of+Memory+errors+by+Increasing+Available+Memory 
> OutOfMemoryError: GC overhead limit exceeded
> 
> This error indicates that the JVM took too long to free up memory during its GC process. This error can be thrown from the Serial, Parallel or Concurrent collectors. It often means that the Xmx value is too high - you might consider lowering it. See Garbage Collector Performance Issues for more details. For more severe and persistent performance issues relating to GC, it is recommended to change to a parallel collector, and to ensure that Confluence has access to the memory demanded by its users.
> 
> The parallel collector will throw an OutOfMemoryError if too much time is being spent in garbage collection: if more than 98% of the total time is spent in garbage collection and less than 2% of the heap is recovered, an OutOfMemoryError will be thrown. This feature is designed to prevent applications from running for an extended period of time while making little or no progress because the heap is too small. If necessary, this feature can be disabled by adding the option -XX:-UseGCOverheadLimit to the command line.
> 
> This kind of OutOfMemoryError can be caused if user requests drown the available resources in the JVM. When this occurs, performance will degrade aggressively. This will eventually require a restart or the application may recover.
> 

Did you tweak the -mXx settings of your database?


Kind regards

Dannes

--
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624