Question4Replies284Views NickM591 Member since 2017 23 posts Contra Costa County Posted: 11 months agoLast activity: 11 months 1 week ago Solved Error: java.lang.OutOfMemoryError: GC overhead limit exceededHi,Our application server stopped to run after installing the Pega Platform 8.1. Below is the error."####<Aug 13, 2019 3:51:56,986 PM PDT> <Error> <Socket> <W10> <AdminServer> "<ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <67d98e47-e7bb-4637-b53a-83ddb7b4094d-00000013> <1565736716986> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000405> <Uncaught Throwable in processSockets java.lang.OutOfMemoryError: GC overhead limit exceeded. java.lang.OutOfMemoryError: GC overhead limit exceeded"Thank you.***Edited by Moderator Marissa to update platform capability tags**** Pega Platform Data Integration Java and Activities ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Posted: 11 months agoRachit_Agarwal PEGA replied to NickM591Hi NickM591, GC overhead limit exceeded" indicates that the garbage collector is running all the time and Java program is making very slow progress. You can do the following. Increase the heap size if the current heap is not enough. Use memory profiling tools like MAT ( Memory analyzer tool), Visual VM etc and fix memory leaks. Apart from setting heap memory with -Xms1g -Xmx2g , try -XX:+UseG1GC -XX:G1HeapRegionSize=n -XX:MaxGCPauseMillis=m -XX:ParallelGCThreads=n -XX:ConcGCThreads=n Posted: 11 months agoNickM591 Contra Costa County replied to Rachit_AgarwalHi Rachit, I have updated the arguments based on your suggestions and it did not help. I suspect Pega is failing somewhere and impacting the application server. Thanks. Posted: 11 months agoAbhinav7 PEGA replied to NickM591Hi Nick, Can you please share heap dump during the issue occurred.Please capture it in hprof format. How much is your heap size ,young gen,old gen & eden size. Thanks, Abhinav Accepted Solution Posted: 11 months agoNickM591 Contra Costa County replied to Abhinav7The issue was resolved after we fixed the JVM arguments with the correct heap size values. Thanks all.