At 11:10 AM 2/28/00 -0800, you wrote:
>I got around the DrWatson only when starting Weblogic with ALL of the
>following switches:
>
>-Xdebug -Xnoagent -Djava.compiler=NONE
>-Xrunjdwp:transport=dt_shmem,address=weblogicserver,server=y,suspend=n
>
>(in addition to the ones already specified in startweblogic.cmd)
>
>However, I still can't seem to reach a breakpoint in my servlet after
>attaching...
>
I've had this problem, too, with trying to set breakpoints in Windows/NT
processes to which I've attached. It seems to be random and happens only
with GUI processes (so far in my experience). I can attach to a process,
set a breakpoint, and then interact with the process so that it hits the
breakpoint. The next session, the breakpoint is never hit. I've tried
suspending the process and setting a breakpoint and this sometimes works
and sometimes doesn't. This is definitely a problem and I would appreciate
feedback from other people who are having trouble getting breakpoints to
work in attached processes.
You might consider using debugger server (listen) mode. This mode is the
opposite of application server (attach) mode. In debugger server mode, the
debugger (server) listens for an application (client) needing debug
services. JDEbug's Listen command supports server mode. Please read the
JPDA documenation for more info on setting up your app to run as a debugger
client. The advantage of debug server mode is that the vm that is running
the client app halts as soon as it attaches to the debugger and before
entering the app's main method. Thus you can set breakpoints before the app
even starts, which might be more reliable.
- Paul
------------------------------------------------------------
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
If you have a problem with the JDE, please use JDE->Help->Submit Problem
Report to prepare your query. This will insure that you include all
information that may be required to solve your problem.
