0002855: Resin instance pids

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0002855

[Resin]

minor

always

08-19-08 09:12

09-19-08 15:23

Reporter

ferg

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

3.2.0

Summary

0002855: Resin instance pids

Description

(rep by Jens Christensen)

After using Resin 2.1 for a long long time we upgraded to Resin 3.0 some time last year, and some months ago to 3.1.

We use stacktraces from the running VM for debugging, but the process of retriving the correct PID when running on unix is now quite hard when we have 10+ resin VM?s running on the same server (jps just shows multiple Resin and WatchdogManager processes).

Previous versions (prior to 3.1 at least) used to have a ?pid-file (or similar) option, so the parent resin PID was recorded. This made it easy to get hold of the child PID with a bit of gawk-magic, but with 3.1 this is no longer a possibility.

What can I do to record the PID of a newly launched Resin process ? or even better ? the PID for the Java VM it spawns?

Additional Information

Attached Files

Relationships

There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
08-19-08 09:12	ferg	New Issue
09-19-08 15:23	ferg	Assigned To	=> ferg
09-19-08 15:23	ferg	Status	new => closed
09-19-08 15:23	ferg	Resolution	open => fixed
09-19-08 15:23	ferg	Fixed in Version	=> 3.2.1

Mantis 1.0.0rc3[^]

26 total queries executed.
24 unique queries executed.