Hi there,
Not sure if it helps, but what we did is add a JVM-specific argument in
resin.conf: -Dresin.node=NodeName and then use that
in our shell scripts to help determine the specific PID for each resin
node (through some ps + grep magic). So far we have stayed with 3.0 due
to some differenc
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 run
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 ru
