Forum Post: Re: Classic Appserver Gc Overhead Limit Exceeded

  • Thread starter Thread starter gus
  • Start date Start date
Status
Not open for further replies.
G

gus

Guest
i wouldn't bother monitoring. too much work. increase heap size and if oom messages don't stop, increase it more. > On Dec 15, 2015, at 11:27 AM, n.lewers wrote: > > Update from Progress Community [https://community.progress.com/] > > n.lewers [https://community.progress.com/members/n.lewers] > > fyi, the java version s/b 1.7 (knowledgebase.progress.com/.../what-version-of-jdk-is-shipped-with-oe-11-5) [http://knowledgebase.progress.com/articles/Article/what-version-of-jdk-is-shipped-with-oe-11-5)], you can also type C:\Progress\OpenEdge\jre\bin\java -version at the command prompt. > > You can try increasing the Xms to 512 or 1024 to see if that helps. As far as monitoring and tuning related params to garbage collection from Paul's reply, you can look at the following link, www.cubrid.org/.../ [http://www.cubrid.org/blog/dev-platform/how-to-tune-java-garbage-collection/] . > > I am more familiar with HPUX/Linux and I believe we normally used 512, however somebody with more windows server experience can share what they use for that param (as well as the other java:gc params). > > View online [https://community.progress.com/community_groups/openedge_rdbms/f/18/p/22003/77219#77219] > > You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here [https://community.progress.com/community_groups/openedge_rdbms/f/18/t/22003/mute]. > > Flag [https://community.progress.com/community_groups/openedge_rdbms/f/18/p/22003/77219?AbuseContentId=74df39da-31fe-4cf6-9c7d-4d4c506922ed&AbuseContentTypeId=f586769b-0822-468a-b7f3-a94d480ed9b0&AbuseFlag=true] this post as spam/abuse.

Continue reading...
 
Status
Not open for further replies.
Back
Top