Hello,
Following 2.1 upgrade, I got the following oom exception in tomcat5, which
never happened before:
SEVERE: Exception invoking periodic operation:
java.lang.OutOfMemoryError: GC overhead limit exceeded
Mar 13, 2014 6:09:59 AM redstone.xmlrpc.XmlRpcDispatcher writeError
WARNING: java.lang.OutOfMemoryError: GC overhead limit exceeded
Mar 13, 2014 6:10:25 AM redstone.xmlrpc.XmlRpcDispatcher writeError
WARNING: java.lang.OutOfMemoryError: Java heap space
Mar 13, 2014 6:10:29 AM redstone.xmlrpc.XmlRpcDispatcher writeError
WARNING: java.lang.OutOfMemoryError: GC overhead limit exceeded
Mar 13, 2014 6:10:46 AM redstone.xmlrpc.XmlRpcDispatcher writeError
WARNING: java.lang.OutOfMemoryError: GC overhead limit exceeded
Mar 13, 2014 6:10:50 AM redstone.xmlrpc.XmlRpcDispatcher writeError
WARNING: java.lang.OutOfMemoryError: GC overhead limit exceeded
Mar 13, 2014 6:11:40 AM
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector run
WARNING:
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@53d1dbff--
APPARENT DEADLOCK!!! Creating emergency
threads for unassigned pending tasks!
Mar 13, 2014 6:11:42 AM
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector run
WARNING:
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@53d1dbff--
APPARENT DEADLOCK!!! Complete Status:
Managed Threads: 3
Active Threads: 0
Active Tasks:
Pending Tasks:
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@3e12a96d
Pool thread stack traces:
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1,5,]
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0,5,]
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#
Looking at the process, I think it might be tuned!
/usr/lib/jvm/java/bin/java -ea -Xms256m -Xmx256m
Is there a parameter to set to increse Xmx parameter?
thanks,
POierre
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
