Re: [Wrapper-user] Debugging service started by wrapper, general hints?

[Hubert F. <hub...@ab...>]

Leif,

<What version of the wrapper are you using?  

3.2.4, trunk version

<Starting with 3.2.1, the Wrapper will automatically disable timeouts
if it is able to detect from the 
<java command line that a debugger is being use.
< or the "-Xdebug" parameter is passed to the JVM

Sorry, I missed these release notes for 3.2.1

<Are you encountering problems?  
No, I was just thinking about possible problems, I want to introduce
Wrapper in our company and want to be prepared for all eventually asked
questions. We debug services standalone, running as application with
wrapper and running as service with wrapper, because the behaviour may
differ. We usually start the app with "server=y,suspend=y"  and then
connect with debugger.

<In general when using a debugger when paused, the JVM process will
appear
<to be frozen from the perspective of the Wrapper.  To keep it from 
<killing that "frozen" JVM, it is necessary to extend or disable the
following 
<timeouts.  

Hmm, it seams to me that setting "-Xdebug" is enough, it seams to work
without problems. 
I am amazed.

<Be aware that changing these timeouts for a live system will severely

<degrade and or disable the Wrapper's ability to respond to a
misbehaving JVM.

Will try to avoid changes to these properties.

Thank you
Hubert

Hubert Felber wrote:
> Hello,
>
> Has anybody some general hints about debugging?  I would like to
> connect the debugger to a service started by wrapper. 
> What should one do to prevent the wrapper from restarting the
service
> if being debugged. 
> Should one disable the keepalive feature? Are there any more issues
or
> pitfalls?
>
> Thank you
> hub