Jdeveloper 9i - Debugger Question

Question

Some more info:
1> I start java in debug mode
set PATH=d:\jdev9i\jdk\jre\bin;%PATH%
cd d:\jdev9i\j2ee\home
java -ojvm -XXdebug,detached,port4000 -jar oc4j.jar
2> You'll see the following message:
*** Port is 4000 ***
*** Connect debugger anytime for on demand debugging. ***
Then, OC4J will start up.
3> Back in JDeveloper, bring up the Project Settings dialog box.
Select Debugger on the left side, check the Remote Debugging
checkbox, and select the Attach to OJVM radio button.
4> Put breakpoints in my code
5> When you press Debug button on the toolbar (or from the menu),
you will be presented with the Attach to OJVM dialog box where
you enter the host name of the OC4J machine (leave blank if it's
the same machine) and the debugging port number (4000). Press
Ok, and the debugger will connect to OC4J.
6> Next I start mmy web application from the browser using
http://localhost:8888/property
7> This triggers my breakpoints.
****However here is my problem. At some point in my flow I have to download an applet and I have breakpoints in it that I want to hit. However Jdeveloper just ignores those breakpoints completely.
So how do I switch between the client applet and server side in a debugging session.
Please help urgent!
(Hope Liz Looney-> the debugger pro answers)
FYI: Jdeveloper9i has a cool debugger!!!

Answer 1

Hi,
Your applet is running in the client (the browser). That's a different JVM than the one in the server (OC4J).
You've connected JDev's debugger to the server JVM (OC4J), but you haven't connected it to the client JVM where your applet is running.
Just like with server side java, you have 2 tasks:
1. Start the JVM with debug options.
2. Connect to the JVM with JDev's remote debugger.
....................Start the JVM with debug options....................
If you install a JDK from Sun, then it should have automatically installed the Java Plug-in. (If you are using the JDK which comes with JDeveloper, then I don't know how you get the Java Plug-in.) So, assuming that you can get a JDK from Sun...
From the Windows Control Panel open up the section for the Java Plug-in. Now, depending on which JDK you have installed, the control panel looks a little bit different. I'd recommend using the Plug-in for JDK 1.4, because it gives much more flexibility for specify Java Runtime Parameters. There are several tabs: Basic, Advanced, Browser, Proxies, Cache, Certificates, and About.
Click on the Advanced tab. Here you can specify which JRE to use and the Java Runtime Parameters. In the Java Runtime Parameters, enter the following:
-client -Xdebug -Xrunjdwp:transport=dt_socket,address=6000,server=y,suspend=n
The -client part is to specify the HotSpot Client JVM. Currently OJVM does not work correctly with JDK 1.4, so you'll have to use the HotSpot Client JVM.
The other options are the JPDA debug options.
The address=6000 part specifies port number for the debugger to connect to. If your browser is running on the same machine as OC4J, you want to make sure that you use a different port number. (Remember you were using 4000 for debugging OC4J).
The suspend=n part specifies that you want the JVM to start up and not to WAIT for a debugger connection. If you put suspend=y, the JVM would stop and wait for the debugger to connect. (You may decide later that for your situation, suspend=y would be appropriate.)
Click on the Browser tab. Here you can check which browsers where you want to use the Java Plug-in. Make sure that the browser you will use for your applet is checked.
Click on the Basic tab. Here you can choose whether to show or hide the Java console.
Press the Apply button and then re-start your browser.
....................Connect JDev's remote debugger....................
You should create another project for remote debugging your applet. Because you are using a HotSpot JVM, you must choose the Attach to JDPA radio button in the Project Settings dialog box, on the Debugger panel.
Put breakpoints in your applet.
Select your applet remote debugging project and press the Debug button on the toolbar. You will be presented with the Attach to JPDA dialog box, which looks just like the Attach to OJVM dialog that you use for remote debugging OC4J. Again, enter the host name of the browser machine (leave blank if it's the same machine as JDev) and the debugging port number (6000). Press Ok, and the debugger will connect to the browser's JVM using the JPDA (Java Platform Debugger Architecture) protocol.
Now, when your applet executes the code where your breakpoint is, JDev's debugger should stop at the breakpoint.
Remember that you have 2 debugging sessions going on simultaneously. You can use the Run Manager window (do View | Run Manager from the main menu) to control which debugging process is the active session. The toolbar buttons will always operate on the active debugging process.
Some people find it easier to run the client and debug the server or to debug the client and run the server, but you can do both at the same time. You'll have to see which you find easiest for you
-Liz
PS - I'm glad you like JDev's Debugger!