Re: [Wrapper-user] Debugging with wrapper

[<da...@sm...>]

I agree and disagree. I don't think the wrapper should set its ping to =20
0 if debug is set, but I do think it should not restart when debug is =20
set. Maybe record in in the log file that it timed out, but due to =20
debug existing, the application won't be restarted, unless there is =20
some super-sexy way of finding out from the debugged application that =20
the wrapper thread (and others depending upon the debugger that =20
connects to it) has been debug paused.

My thoughts at least!

Cheers again Leif!

Quoting Chandra Patni <cp...@ig...>:

> I think wrapper should set ping timeout to zero if -Xdebug and
> -Xrunjdwp .... option is set  for JVMDI supporting VMs. And print out
> this as warning. It should also do the same when -agentlib:jdwp...
> option is set for newer JVMTI supporting VMs. Otherwise, it will always
> result in surprised user.
>
>
>
> Leif Mortenson wrote:
>> Chandra,
>> I'm not sure of any way to let the Wrapper know that the JVM is  =20
>> paused due to
>> debug mode.  You would not want to disable the ping timeout simply becaus=
e
>> debug was enabled.    I should add a note about this or maybe make  =20
>> the Wrapper
>> provide some additional info if the command line contains -Xdebug.  Setti=
ng
>> wrapper.ping.timeout to 0 should solve the problem for you however.
>>
>> Cheers,
>> Leif
>>
>> Chandra Patni wrote:
>>
>>> I started my JVM with
>>> -Xdebug -Xnoagent -Djava.compiler=3DNONE  =20
>>> -Xrunjdwp:transport=3Ddt_socket,server=3Dy,suspend=3Dn,address=3D5005
>>>
>>> and attached IDE debugger. Blocked a JSP thread on a breakpoint.  =20
>>> The wrapper restarts/shuts down (depending on  =20
>>> wrapper.disable_restarts=3DTRUE) the VM.
>>>
>>>
>>> ERROR  | wrapper  | 2006/05/09 16:35:02 | JVM appears hung: Timed  =20
>>> out waiting for signal from JVM.
>>> ERROR  | wrapper  | 2006/05/09 16:35:02 | JVM did not exit on  =20
>>> request, terminated
>>> STATUS | wrapper  | 2006/05/09 16:35:03 | JVM Restarts disabled.  =20
>>> Shutting down.
>>> STATUS | wrapper  | 2006/05/09 16:35:03 | <-- Wrapper Stopped
>>>
>>> I can set the wrapper.ping.timeout to zero to avoid this.  =20
>>> Shouldn't wrapper should detect debug mode?
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> Using Tomcat but need to do more? Need to support web services, security=
?
>>> Get stuff done quickly with pre-integrated technology to make your =20
>>>  job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geroni=
mo
>>> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>
>>
>>
>> -------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, security?
>> Get stuff done quickly with pre-integrated technology to make your  =20
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim=
o
>> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job eas=
ier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user