Bhagya,
This has been cleaned up for the next release. The problem is that
when debugging,
the JVM is paused and and Wrapper things it is hung and kills it. If
you look at the
Wrapper.log file you will most likely see output to that effect.
To work around this for now, you need to extend or disable the
various timeouts.
wrapper.startup.timeout=3600
wrapper.ping.timeout=3600
wrapper.shutdown.timeout=3600
Make sure you remove those settings when you are done debugging as they
disable the ability of the wrapper to detect hung JVMs for an hour. The
above
settings will allow you to keep the JVM paused for one hour. If you
need to do
so for longer, then extend the timeouts further. Read over the docs
for those
properties:
http://wrapper.tanukisoftware.org/doc/english/properties.html
Cheers,
Leif
Prabhakar, Bhagyashree wrote:
>
> I am able to hook up my eclipse debugger to the Wrapper after
> specifying additional parameters to the wrapper
>
> wrapper.java.additional.12="-Xdebug" \
> wrapper.java.additional.13="-Xnoagent" \
> wrapper.java.additional.14="-Djava.compiler=NONE" \
>
> wrapper.java.additional.15="-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y"\
>
>
> However, the execution does not wait at any breakpoint. Also the
> debugger get disconnected as soon as one response is received from the
> webservice with a message "Remote Java Application Terminated" . Can
> anybody please help me fix this strange behavior?
>
> Thanks,
> Bhagya
>
|
