On Aug 19, 2008, at 3:32 AM, Jens Dueholm Christensen wrote:
Hi
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?
I've added a bug report for this at http://bugs.caucho.com/view.php?id=2855
We can add the pid to the watchdog status command or even create a
watchdog pid command to get the pid for a -server. I don't think it's
possible currently, unless you use JMX to ask each Resin instance what
its -server and pid are.
-- Scott
Regards,
Jens Dueholm Christensen
Business Process and Improvement, Rambøll Survey IT
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
