Issue Details (XML | Word | Printable)

Key: RIO-207
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dennis Reedy
Reporter: Dennis Reedy
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Rio

ServiceExec match on forked pid

Created: 11/Sep/09 01:59 AM   Updated: 11/Sep/09 02:01 AM
Component/s: Deployment
Affects Version/s: 4.0 M3
Fix Version/s: 4.0 M3

Time Tracking:
Not Specified


 Description  « Hide
When deploying a service exec'd service (like Tomcat) the external process pid returned may be the "real" pid, not the child of the exec'd process.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Dennis Reedy added a comment - 11/Sep/09 02:01 AM
By checking the list of pids that JMX attach APIs againt the pid of the forked process we can check if we have the 'actual' pid.

Note that this is only an issue if we want to attach to the exec'd process using JM. If this match fails, the service will still execute and be monitored by the Cybernode