4944 2007-01-09 09:57 Multijob resources never yield to memory pressure and can't be destroyed 2012-09-05 11:43:34 1 1 1 Unclassified GRAM wsrf managed multi job service 4.0.3 All All RESOLVED WONTFIX P3 major 4.2.1 1 meder@mcs.anl.gov smartin@mcs.anl.gov lane@mcs.anl.gov madduri@mcs.anl.gov smartin@mcs.anl.gov meder@mcs.anl.gov 2007-01-09 09:57:47 It seems that when multijob resources set up their subjobs they subscribe to subjob notifications in such a way that they will never exit memory. In particular, the multijob resource itself implements implements the notify callback interface and is registered with the notification consumer manager for each subjob, which ends up keeping it in memory (this step needs to be proxied). The other issue is that upon destroy we only remove one of the subjob notification consumers, which essentially leaves the multijob resource in memory indefinitely. bacon@mcs.anl.gov 2007-09-19 11:38:08 Reassigning to current GRAM developer to close/fix as appropriate. smartin@mcs.anl.gov 2012-09-05 11:43:34 Doing some bugzilla cleanup... Resolving old GRAM3 and GRAM4 issues that are no longer relevant since we've moved on to GRAM5. Also, we're now tracking issue in jira. Any new issues should be added here: http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363