The Wrapper is currently waiting for 1 second between the
time that the thread dump request is sent and the JVM
process being killed. That was always plenty of time in my
tests, but I guess it needs to be longer. Just to make
everyone happy, I'll add another config property for this
timeout.
Changing this to a feature request.
Cheers,
Leif
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Most likely 1 second is just too slow. I doubt that your
software is affecting it that much as it is all running on
the remote machine.
Unfortunately, it is not possible to wait for the dump to
complete because I am just sending a signal to the JVM which
recognizes the signal and invokes the dump. The contents
of the dump differ greatly depending on the platform and JVM
implementation, so parsing the output is also not possible.
The safest (and easiest) thing to do is to just extend the
length of the delay. I will set the default to 2 seconds
and then allow users to set it longer if they wish. If I
make the value too long, then the wrapper will appear
sluggish on shutdown.
Cheers,
Leif
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Adding too many properties just confuses people, so I am
going to try increasing the delay between requesting a
thread dump, and killing the JVM process from 1 second to 3.
That should not be too sluggish for users as this is not
the normal shutdown mode. Let me know if anyone is still
having problems with the thread dump being truncated.
This will be in 3.0.5.
Cheers,
Leif
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Wrapper log file
Logged In: YES
user_id=228081
The Wrapper is currently waiting for 1 second between the
time that the thread dump request is sent and the JVM
process being killed. That was always plenty of time in my
tests, but I guess it needs to be longer. Just to make
everyone happy, I'll add another config property for this
timeout.
Changing this to a feature request.
Cheers,
Leif
Logged In: YES
user_id=92749
I guess that my use of remote control software slows things
down considerably.
Wouldn't it be possible for Wrapper to actually wait exactly
until the thread dump is completed?
Logged In: YES
user_id=228081
Most likely 1 second is just too slow. I doubt that your
software is affecting it that much as it is all running on
the remote machine.
Unfortunately, it is not possible to wait for the dump to
complete because I am just sending a signal to the JVM which
recognizes the signal and invokes the dump. The contents
of the dump differ greatly depending on the platform and JVM
implementation, so parsing the output is also not possible.
The safest (and easiest) thing to do is to just extend the
length of the delay. I will set the default to 2 seconds
and then allow users to set it longer if they wish. If I
make the value too long, then the wrapper will appear
sluggish on shutdown.
Cheers,
Leif
Logged In: YES
user_id=228081
Adding too many properties just confuses people, so I am
going to try increasing the delay between requesting a
thread dump, and killing the JVM process from 1 second to 3.
That should not be too sluggish for users as this is not
the normal shutdown mode. Let me know if anyone is still
having problems with the thread dump being truncated.
This will be in 3.0.5.
Cheers,
Leif