ResourceContext.getNativeProcess() is supposed to check whether the last known
PID is still running and if not, it is supposed to refresh.
I have seen small lags in this detection, caused by Sigar itself - it just
takes a while for it (or the underlying OS) to figure out that given PID is
really dead.
Now if you are able to consistenly reproduce a scenario where the above is not
true - i.e. the PID doesn't refresh even after say a minute, then I'd consider
it a bug.
Lukas
On Tuesday, September 18, 2012 00:16:48 John Sanda wrote:
I have implemented start and shutdown operations for a top-level
server
type. For the shutdown, I am just doing,
ResourceContext.getNativeProcess().kill("KILL")
For the start operation I am invoking a shell script that does the work.
Here's my question. When I restart the resource, it will get a new pid. I
have been relying on ResourceContext.getNativeProcess().getPid() to get the
pid. In a restart situation though, that won't work until discovery has run
again. Is there a way to force update the stored ProcessInfo immediately
after I execute the resource's start operation?
- John
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel