Bugzilla – Bug 3948
Service must release all of its resources on deactivation
Last modified: 2012-09-05 11:42:58
You need to
before you can comment on or make changes to this bug.
During deactivation the service must properly release all of its resources. For
example, the service must stop all of its threads, stop background tasks, close
database connections, close opened files, etc. This is extremely important with
the container dynamic deployment features as services that do not do proper
cleanup might eventually crash the other services or the container.
Please see the following for details on deactivation:
Is this still a problem? I don't see any details on what exactly was going
wrong or how to reproduce it.
It is the service responsiblity to ensure that it shutdowns all of it threads,
stops all of processes, etc. You have to figure out what is needed here. To
test things I would suggest running things in a profiler. That is, submit a
job, wait until it is done, perform some hot deploy option (or just simply a
reload operation) that force GC and take a shapshot of the heap. See how many
instances of some gram classes are there. If they doubled then something is
holding references to them. Also, check the number of gram-specific threads.
There should be no gram specific threads after reload (unless you do
loadOnStartup). And once all this looks good, do the same test but while the
job is executing.
(In reply to comment #2)
> It is the service responsiblity to ensure that it shutdowns all of it threads,
> stops all of processes, etc. You have to figure out what is needed here.
So you're saying that there is no evidence of anything wrong. This is just a
testing request. Is that right? If that's the case, I hardly consider this
"critical". Putting a target milestone seems more appropriate.
> test things I would suggest running things in a profiler. That is, submit a
> job, wait until it is done, perform some hot deploy option (or just simply a
> reload operation)
What is a "reload" operation?
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: