I have a tip for one question -->
a) add debug-enabled and it will ALWAYS start debugging-ready --> no
need for --debug
b) set suspend to y and you will always be able to leisurely attach to
the server during QL
<java-config debug-options="-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009"
system-classpath="" classpath-suffix="">
<java-config debug-options="debug-enabled="true" -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009"
system-classpath="" classpath-suffix="">
Ken Cavanaugh wrote:
> I need to attach a debugger to the V3 app server. I think I can do that
> by asadmin start-domain --debug and then attach the debugger to 9009.
> But how do I run a single test (say ejb/remoteview) so I can debug the
> server side? I don't want to run all of the QLs, or have the QLs launch
> an instance of GFv3 to which I can't attach a debugger.
>
> Thanks,
>
> Ken.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>