cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you know you can set a signature that will be added to all your posts? Set it here! X

Translate the entire conversation x

Windchil Heap Memory shortage problem (with Garbage Collector)

HK_10285495
8-Gravel

Windchil Heap Memory shortage problem (with Garbage Collector)

Version: Windchill 12.0

 

Use Case: Recently I've been experiencing a Heap Memory shortage situation on my Windchill Method Server.


Description:

Recently I've been experiencing a Heap Memory shortage situation on my Windchill Method Server.
To address this situation, we increased memory and added heap memory. However, the garbage collection rate and heap memory usage continue to increase, resulting in errors in use.
It's difficult to understand why this issue persists despite no significant changes to the Windchill system or significant changes in the number of users. Could this be due to a sudden garbage collector issue?

ACCEPTED SOLUTION

Accepted Solutions

Explain a bit more about what you are seeing. When you restart, does it work for a while then suddenly (randomly) spike up and consume memory? Or is it slowly building upon each startup until it reaches its limit? There are tools available in server status or the JMX admin that can show you memory usages as a graph to help isolate the issue. I am trying to see if this is related to a user action or a queue job that is misbehaving. What do you have set for your query limit to the database? It could be that a user is asking to boil the ocean and there are no limits in place. The server status page on the site utilities would be a good place to start as you should see things flashing red. Lastly, how good is the system tuned? Did you run the WCA initially? https://www.ptc.com/en/support/article/CS153338?source=search

 

View solution in original post

2 REPLIES 2

Explain a bit more about what you are seeing. When you restart, does it work for a while then suddenly (randomly) spike up and consume memory? Or is it slowly building upon each startup until it reaches its limit? There are tools available in server status or the JMX admin that can show you memory usages as a graph to help isolate the issue. I am trying to see if this is related to a user action or a queue job that is misbehaving. What do you have set for your query limit to the database? It could be that a user is asking to boil the ocean and there are no limits in place. The server status page on the site utilities would be a good place to start as you should see things flashing red. Lastly, how good is the system tuned? Did you run the WCA initially? https://www.ptc.com/en/support/article/CS153338?source=search

 

Hello avillanueva.

 

Thank u for your interest about my problem and article shared.

 

I found the problem that our custom source have unnecessary searching logic.

 

Unnecessary searching logic make memory leak.

 

So, i fixed and solved. 

 

Thank you.

 

Announcements
Top Tags