I posted this in an older thread at the end:
1769585
I can't run the debugger using the runner: jvm option of ojvm, hotspot, or client, and can't debug a simple standalone java class w/o an error window within the same project:
When I try to debug a standalone class (HelloWorld.java)
Status line showed connection problem.
got errors:
(can't gab the command line since JDEveloper is locked up - I have an hourglass and the only thing I can do is minimize, maximize, or close it)
c:\jdev10121\jdk\bin\]javaw.exe -ojvm -XXdebug,quiet,port2651 -classpath C:\Projects\jdev10121\MSI\MSI\
Debugger connected to local process.
Debugger connection to debugee process has been lost.
Debugger disconnected from local process.
Process exited.
Debugger unable to connect to local process
If I try to debug using client or hotspot, the application will start, but it does not recognize any of the breakpoints at all, so the debugger never kicks in. It does on a windows xp workstation running the same version of jdeveloper. Also, I can't recompile classes and replace on the fly.
I am able to run the web application regular (w/o debug) using ojvm.
My J2EE settings are 1.4.2_06. This is what resides in c:\jdev10121\jdk\bin. That same path is in my system path. The java_home env var is set to: c:\jdev10121\jdk.
I run the JDEV.exe rather than JDEVw.exe and nothing appears in the console window.
I can't recall anything about the machine that caused this to stop working as it was working less than 1 week ago. The machine is a Windows 2000 Dell workstation. I thought the problem might be caused by adding the Oracle XML Parser to the project, but I removed that library and commented out the code.
The only way the debugger works is to do REMOTE DEBUGGING (I'm connecting to my embedded oc4j via localhost though):
1. Start the application using hotspot in debug mode. Note the port that is sent to oc4j.
2. Create another project for remote debugging, and set the tools->project properties->remote debugging on for that project. right click and select remote debug, and type in the port from the other window. Once connected, I can set breakpoints and examine code, etc.
This is really troubling as putting system.debug messages for debugging is like going back to the early days of cobol on the vax for me -- no wait, the debugger under motif in 1994 worked... well, maybe before cobol then....
Anyway, please let me know if there's a solution to this.
Thanks,
Eric