[ https://issues.apache.org/jira/browse/TRAFODION-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Atanu Mishra updated TRAFODION-1265: ------------------------------------ Fix Version/s: 2.0-incubating > LP Bug: 1463179 - VSBB update causes TM heap leak > ------------------------------------------------- > > Key: TRAFODION-1265 > URL: https://issues.apache.org/jira/browse/TRAFODION-1265 > Project: Apache Trafodion > Issue Type: Bug > Components: dtm > Reporter: Buddy Wilbanks > Assignee: Joanie Cooper > Priority: Blocker > Labels: heap, leak, vsbb > Fix For: 2.0-incubating > > > Since the May 1 executor checkin that turned on VSBB update, the TM will leak > memory to the point of an OOM condition after only 26 hours of the longevity > test. Pretty sure it will be much quicker if we limit longevity to only > perform the delivery transaction, which is the only VSBB invoker. > We've collected jmaps for some of the TMs on zircon4, and core files for > analysis. Located on /home/squser4/fqw/TMdumps. You can see the corefile > size increasing as well as the old space usage. Here's the first and last > corefiles taken for pid 9915 > -rw------- 1 squser4 seaquest 113142116 Jun 8 18:51 jmapdump-9915.0 > -rw------- 1 squser4 seaquest 341615426 Jun 8 19:58 jmapdump-9915.13 > and here is the initial jmap-9915.0 old space: > PS Old Generation > capacity = 1407713280 (1342.5MB) > used = 100979864 (96.3019027709961MB) > free = 1306733416 (1246.198097229004MB) > 7.17332609094943% used > and then jmap-9915.13 > PS Old Generation > capacity = 571998208 (545.5MB) > used = 250169256 (238.57999420166016MB) > free = 321828952 (306.92000579833984MB) > it grows about 12Meg every 5 minutes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)