Article - CS379058
Single wt.servlet.IPRequestTracker object consumed memory of Method Server in Windchill PDMLink 12.0
Modified: 09-Mar-2023
Applies To
- Windchill PDMLink 12.0.2.0 to 12.0.2.4
Description
- After several days of uptime MethodServer runs out of heap space
- MethodServer runs out of heap, but performance tables doesn't show any MethodContexts with large bytes allocated
- Heap dump of MethodServer shows 10 GB for a single wt.servlet.IPRequestTracker object
- wt.servlet.IPRequestTracker has a queue of over 1 million wt.servlet.Request objects
- Method Server Heap accumulates over a period of week causing all sorts of performance issues
- MethodServer log indicates UserDetailsPersistor thread was interrupted:
WARN [RMI TCP Connection(1864)-xxx.xx.xxx.xxx] wt.method.MethodContextMonitor.contexts - Interrupting method context 4eie0lug;l93cintc;5844;1r6dbp;35 with thread UserDetailsPersistor [269] via JMX WARN [RMI TCP Connection(1864)-xxx.xx.xxx.xxx] wt.method.server - Interrupting thread UserDetailsPersistor
This is a printer-friendly version of Article 379058 and may be out of date. For the latest version click CS379058