Debugging in JDeveloper

I cannot debug in JDeveloper. When I try to debug I get an error that some class is not found. Has someone got an idea regarding this?

<BLOCKQUOTE>quote:<HR>Originally posted by Liz Looney ([email protected]):
Hi.
Can you give more details about the problem?
-Problem is that when I debug the program I get some error that rcsa class is not found.
Can you build the project without any errors?
-Yes I can build the project without errors
Can you run the project?
-Yes I can run the project
What kind of project is it? Is it a Java application or an applet or a servlet or a JSP or what?
-This is servlet
Liz<HR></BLOCKQUOTE>
null

Similar Messages

Remote debugging in JDeveloper

Hi,
Can you please provide the steps to do remote Debugging of source from JDeveloper
Thanks

are you looking for this?
http://aboutsoa.wordpress.com/2009/03/10/remote-debugging-in-jdeveloper/
http://jdeveloperfaq.blogspot.com/2009/12/faq-4-how-to-remote-debug-adf.html
http://xmlandmore.blogspot.com/2010/12/using-remote-debugging-in-jdeveloper.html

Problem debug with JDeveloper 10.1.2 Mac OS X

Hi,
I can't run debug on OSX 10.3.8 java version 1.4.2_05
it brings this long message:
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/bin/java -client -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=50479 -classpath /Users/42714/jdevhome/mywork/MyTestXML/Project1/classes:/Users/42714/jdevhome/system10.1.2.0.0.1811:/Applications/JDeveloper.app/Contents/Resources/jdev/BC4J/lib/adfm.jar:/Applications/JDeveloper.app/Contents/Resources/jdev/BC4J/jlib/adfjclient.jar:/Applications/JDeveloper.app/Contents/Resources/jdev/jlib/bigraphbean.jar:/Applications/JDeveloper.app/Contents/Resources/jdev/jlib/LW_PfjBean.jar mypackage1.dialog
Then it shows the message:
"Attempting to connect debugger to debuggee process
and that's it. Stuck.
When running the project without debugger, runs fine.
Please help.
Thanks,
Nava.
P.S. I couldn't run the debugger since I've installed JDeveloper. I run XCode developer tools 1.2

Go to ~/Library/Caches/com.apple.Safari
Move the Cache.db from the com.apple.Safari folder file to the Trash, restart your Mac, try Safari.
If that doesn't help, try Safari in another user account. Same problems there, log back into your admin account, launch Disk Utility.
That's located in /Applications/Utilities
Select the startup disk on the left then select the First Aid tab.
Click: Verify Disk (not Verify Disk Permissions)
If the disk needs repairing follow the instructions for Using Disk Utility to verify or repair disks

How to use Remote Debugging in JDeveloper 3.1 ?

I am trying to use the Remote Debugging option with EJBs in JDeveloper 3.1 with Oracle8i 8.1.6.
I checking all steps the online walkthrough for Remote Debugging EJB in 8i and it didn't work.
I'm using Oracle8i EJB/CORBA debug option in project properties, but it does not stop in my EJB's break points.
I tried deploying the EJB again ( with break points) and again it didn't work.
The error message I got in the trace file is:
Errors in file D:\Oracle\admin\SCT\udump\sctS000.TRC:
ORA-29516: Aurora assertion failure: Java thread deadlock detected
Could someone please tell me how to use it?
null

Which platform is the database running on ??
Other things you should check -
when debugging the EJB, JDev
3.1 looks through your IIOP connections to find the one to use.
Make sure that the IIOP connection that JDev is using for the debugging matches the IIOP connection that the EJB client application is using.
raghu
null

PL/SQL debugging use JDeveloper

JDeveloper appears to require DEBUG ANY PROCEDURE privilege due to being needed for DBMS_DEBUG_JDWP. Is there any way around this? I am sure our DBA would prefer not to be routinely giving this out and all we need to do is debug stored procedures created by the schema owner while logged in as the schema owner.

micwic --
I logged bug6508875 for this.
One suggestion in the meantime until we can get compile errors directed to the log window for offline objects...
You can open the Database Navigator to point to the same db connection. After generating the offline PL/SQL to the db, refresh the connection in the DB navigator. You will see any invalid objects flagged with an error icon. Then you can right-click on the PL/SQL with the error, and "Make" it. This will display the errors in the log window, similar to SQL Developer.
-- Brian

Debug JSP/JDeveloper 3.1

I am trying to use JDeveloper 3.0 to debug JSP pages. The pages call each other through standard link tags ( <a href=myjsp.jsp...)
I can debug a single jsp page but not the linked to pages. Can this be done in 3.0?
If not.. when is JDeveloper 3.1 expected??
Thanks,
Dave
null

This is possible in JDeveloper 3.0
For example create
A.jsp which has a link to B.jsp as
<% out.println("Hello World"); %>
Call second JSP
Place a break point on out.println
B.jsp has
<% out.println("Hello World"); %>
place a breakpoint on this line
Run A.jsp in the debug mode and when you see the html page rendered in browser click on the link which calls B.jsp and this will stop at the breakpoint place in B.jsp
raghu
null

When Debugging in jDeveloper

Hi all - hope this is the right forum for this but, when I initially installed Oracle I was using the wrong time zone. I also installed Oracle jDeveloper. Then I changed the timezone to SA time - which is GMT+2 but now I am getting the following error ...
Exception breakpoint occurred at line 106 of FileInputStream.java.
java.io.FileNotFoundException: C:\JDeveloper\jdev9051\jdk\jre\lib\zi\GMT+02:00 (The system cannot find the file specified)
Warning: The debugger has stopped in a class where tracing is disabled.
Because of the tracing options set in your project, Step Over is not available in this class.
If you wish to step through this class, please update your tracing options by choosing Tracing... from the context menu in the Classes window.
I can just click on resume and things continue to the Embedded OC4J but its annoying. Is there any way I can fix this without reinstalling Oracle products?
Thanks,
Russell

Sundararam,
I did not believe this and then I tried
and I was able to duplicate your situation.
The problem can happen if your debugger preferences are set in a particular way.
Do the following:
While JDeveloper is debugging.
You are at break point
Right click in the window where the locals
are displayed - but do not click on elements - right click in the empty area -
and select Properties...
This launches the Context Tree Properties dialog which controls your debugging options.
To get to the correct choice,
be sure your settings for
[X] Display Data
and Public, Protected and Private are all checked [x][x][x]...
Press OK to accept changes and
hopefully you can see the members within
your local variables.
I hope this helps,
-John
(Context Tree Properties)

Debugging with JDeveloper 2 with JDK 2

Oracle Jdev team,
I am running jdeveloper 2 (JDK 1.2), build 343. Whenever I
attempt to debug an app i get this error dialog:
Cannot debug project with Target JDK 'java
version "JDK1.2_JDEVELOPER'", can only debug with Target
JDK 'java version "1.2"'.
My Project Properties Target JDK Version is pointing to the java
1.2 java.exe that came with Jbuilder.
Path of java.exe
D:\Tools\JDeveloper20\java1.2\jre\bin\java.exe
Classpath
D:\Tools\JDeveloper20\java1.2\jre\lib\rt.jar
Sourcepath
[D:\Tools\JDeveloper20\java1.2\src.jar]\src\
I've attempted to use various 1.2 jdks to get the debugger to
work, but always with the same version.
The project began as a JDK 1.2 project (did not attempt to
switch from a jdk 1.1.x project).
I;m sure you've seen this before, what am I doing wrong???
THanks in advance, Peter
null

I have the same problem but even wierder.
When I try to debug my project JDeveloper says
Cannot debug project with Target JDK 'java version
"JDK1.1.7_JDeveloper'", can only debug with Target JDK 'java
version "1.1.8'".
I do indeed have such a Target JDK defined, but I have not
compiled anything in the current project with that. In fact I
haven't switched JDKs at all in this project, nor in this
workspace.
What gives?
Markus Burle (guest) wrote:
: JDeveloper Team (guest) wrote:
: : Hi
: : JDeveloper allows to use different JDK's but the debugger
only
: : works with JDK's that come with JDeveloper. If you are
pointing
: : to a JDK outside it will still work but the debugger will be
: : disabled.
: : regards
: : raghu
: The original poster (see below, marked with an X) IS using the
: JDK that comes with JDeveloper. I'm also using it and have the
: same problem.
: Markus
: : Peter (guest) wrote:
: : : Oracle Jdev team,
: : : I am running jdeveloper 2 (JDK 1.2), build 343. Whenever I
: : : attempt to debug an app i get this error dialog:
: X : Cannot debug project with Target JDK 'java
: X : version "JDK1.2_JDEVELOPER'", can only debug with Target
: X : JDK 'java version "1.2"'.
: X : My Project Properties Target JDK Version is pointing to
the
: X java
: X : 1.2 java.exe that came with Jbuilder.
: : : Path of java.exe
: : : D:\Tools\JDeveloper20\java1.2\jre\bin\java.exe
: : : Classpath
: : : D:\Tools\JDeveloper20\java1.2\jre\lib\rt.jar
: : : Sourcepath
: : : [D:\Tools\JDeveloper20\java1.2\src.jar]\src\
: : : I've attempted to use various 1.2 jdks to get the debugger
to
: : : work, but always with the same version.
: : : The project began as a JDK 1.2 project (did not attempt to
: : : switch from a jdk 1.1.x project).
: : : I;m sure you've seen this before, what am I doing wrong???
: : : THanks in advance, Peter
null

How do I disable remote debugging in JDeveloper??

I am having a problem disabling the remote debugging feature inside JDeveloper 9i. I currently have a workspace in which I has set up a remotely debuggable project and another "normal" project which contains the client application that accesses my remote application. When I start the remote application, I am able to attach the remote debugger inside JDeveloper and it works just fine. However, when I attempt to debug my local project, it starts with the following JVM parameters :
java -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=1552
and fails to start since it cannot attach to a remote process. I have double-checked the project settings and the remote debugging checkbox is NOT select for the local project. I have even resorted to restarting JDeveloper, but that failed to resolve the problem.
Does anybody have any suggestions as to how to fix this problem?

Hi David,
Some things concern me about the java command you show in your post:
1. On Windows, JDeveloper should be starting javaw, not java. In your post, you show a java command. Is it really java or is it javaw?
2. JDeveloper should be specifying which JVM to use. In your post, you show a java command where there is no JVM specified (there is no -ojvm or -hotspot). Check your project settings - on the Libraries panel, what J2SE (JDK) are you using? on the Runner panel, what Virtual Machine is selected?
Other than that, the command you show in your post (the command that JDev launches when you try to debug your local project) contains (mostly) the correct command options for local debugging with a JVM which supports JPDA debugging (for example, classic or hotspot).
Let me explain the command options:
java -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=1552-Xdebug Enables debugging.
-Xnoagent Disables old debugging agent (also called sun.tools.debug).
-Djava.compiler=NONE Disables the JIT compiler.
-Xrunjdwp Loads the JPDA JDWP library.
:transport=dt_socket Use sockets for communicating with the debugger.
,server=y Listen for a debugger to attach.
,address=1552 Use port 1552.
JDev will use the above command options when you do local debugging with a JVM other than OJVM. (Note that -Xnoagent and -Djava.compiler=NONE are not required for HotSpot, but are accepted and ignored.)
The command that you show is not trying to connect to anything.
When JDev does remote debugging, it does not start the java process at all.
I think there is some other reason why your program does not start up. What other messages are displayed in the Log Window? Do you see messages like "Debugger attempting to connect to local process." or "Debugger connected to local process." or "Debugger unable to connect to local process."?
-Liz

JDeveloper 11.1.1.1.0 hangs while debugging a simple application

Hello all... I use Jdeveloper 11g in my Fedora linux ( version 9 ) machine. Jdev works fine normally, but when I try to debug a sample application it simply hangs and does not allow me to do anything besides going to console mode and killing off all the processes associated with Jdev in the following manner..
[sugantha@localhost ~]$ ps aux | grep jdev
and then kill -9 <PIDs>
The code where it hangs exactly is this...
*public void actionPerformed(ActionEvent e) {*
String cmd = e.getActionCommand();
*if (ON_TOP_COMMAND.equals(cmd)) {*
if (onTop.isSelected())
layeredPane.moveToFront(dukeLabel);
else
layeredPane.moveToBack(dukeLabel);
*} else if (LAYER_COMMAND.equals(cmd)) {*
int position = onTop.isSelected() ? 0 : 1;
layeredPane.setLayer(dukeLabel,
layerList.getSelectedIndex(),
position);
with the breakpoint placed in line 2 of the code shown.Pressing F7, F8 or F9 has no effect. Has anyone ever encountered this issue or is there a workaround to avoid this kind of behaviour while debugging in JDeveloper. Thanks in advance.

"Installing the ADF runtime is not required if you are using JDeveloper to run applications in Integrated WebLogic Server."
http://docs.oracle.com/cd/E24382_01/admin.1112/e16179/deploy.htm#BGBECCBE
When I explicitely add the groovy-lang-1.6.3.jar in "Project properties" --> "Libraries and Classpath" then it works!
The groovy-lang-1.6.3.jar gets deployed with the application.
But still, why isn't it sufficient to have "ADF Model Runtime" (containing groovy-lang-1.6.3.jar) added ??
Is the ADF Model Runtime library deployed with the application? Select Manage Libraries. Is the ADF Model Runtime library selected as Deployed By Default?
If a new library is created, is the library a Deploy by Default?
If a library is added to a Model or ViewController project and used in the other project is a dependency defined between projects?
On JDeveloper 11.1.1.4.0 the same application works when debugging it.
Does anybody know how to fix it. Is there a missing library which was automatically added in the old JDeveloper but is not any more in the new one?
JDeveloper 11.1.1.4.0 JDeveloper runtime libraries that are deployed into Oracle WebLogic Server to support ADF applications includes groovy-all-1.6.3.jar in the adf.oracle.domain.ear Library and System Classpath.
http://docs.oracle.com/cd/E23549_01/web.1111/e15470/ap_jdevlibs.htm#BCFCIGBJ
In JDeveloper 11.1.2.2.0 groovy-all-1.6.3.jar is included only in the adf.oracle.domain.ear Library, not the system classpath.
http://docs.oracle.com/cd/E26098_01/admin.1112/e16179/ap_jdevlibs.htm
And is 1.6.3 the right version for ADF 11.1.2.2.0 Applications or should I add a newer groovy version?
The groovy version is the same groovy-all-1.6.3.jar.
Edited by: dvohra16 on Sep 11, 2012 9:18 AM

Help: Multi-language Support in Jdeveloper 9i Log Window

I have basically solved the multi-language display problem in code editor, compiling and run. If I send the output out of JDeveloper, it's displayed well.
However, if I run or debug in JDeveloper and want to see the result in JDeveloper log window, the non-english characters are still not recognisable. Anyone knows the correct setting?

Hi...
It sounds like your encoding settings aren't set correctly. Your compiler encoding should be set to the same value as your environment encoding and this should usually be the same as your operating system default encoding (unless your app is encoded as Unicode).
Set the encoding for compiler in the Project Properties under Profiles\Developement\Compiler. Leave it as default unless you have a good reason otherwise.
Set the encoding for the environment in the Tools\Preferences menu item, in the Environment page. Leave it as default (which should = Compiler encoding) unless you have a good reason to change it.
If you continue to have problems, I'll need to know the version of JDeveloper you're using, the OS and region settings, and the values set for for encoding in JDeveloper.
Regards,
Tony

TCP/IP portrange for local Debugging

How can I restrict the TCP/IP ports used to connect from the server to the client when locally debugging with JDeveloper 10g?
I'm talking about this command (executed by JDeveloper):
call dbms_debug_jdwp.connect_tcp(ip-address, port)
Thanks.

The implementation of the Blackfin target is partially located in "plug-in" VIs that you can access. Open "C:\Program Files\National Instruments\LabVIEW 7.1 Embedded\resource\LabVIEW Targets\Embedded\vdk\vdk_LEP_TargetPlugin\LEP_vdk_ScriptCompiler.vi". You can see in the attached screenshot where this plugin VI determines the IP of the host PC and concatenates it in as a compiler flag. You can modify this LabVIEW code to hard-code that IP if you have multiple IP addresses, or even add functionality to programmatically get the correct IP address!
Message Edited by Michael P on 09-14-2006 02:22 PM
Michael P
National Instruments
Attachments:
BFIP.JPG ‏49 KB

Dubug In Jdeveloper 10.1.3

Hi ,
Does anybody knows how to debug in JDeveloper 10.1.3 because, i tried to put breakpoint in the .java files its showing me breakpoint mark, but while debugging the code , it execution not halt at the breakpoint. Is there any setting that i should do?

Can you create a new Workspace & project and create a simple Test.java with a beep and a System.out.println and try to debug this????
Because the steps already explained are the same I am using and even for remote debugging it is working for me.

HOW TO: Debug a remote JSP

<h1>HOW TO: Debug a remote JSP</h1>
Note: The process of debugging a remote JSP on an Apache/Jserv
installation involves a couple extra steps that were not covered in the JDeveloper
3.2 documentation. 
Introduction
You use JDeveloper to debug JavaServer Pages (JSP) deployed and running on
a server that includes a JSP container, such as Apache Jserv. Your JSP container
will need to be configured to enable remote JSP debugging using JDeveloper.
JDeveloper allows you to use one of two protocols for JSP debugging - the
Oracle Java Virtual Machine (OJVM) debugging protocol or the Sun Java Platform
Debugging Architecture (JPDA). Before you start your remote debugging session,
you will have to choose which method to use. If you use the OJVM protocol, your
debugging session will run more quickly and you will have some additional features
to assist you. You can only use OJVM on a Windows NT system. If your server
is running UNIX or another operating system, you must use the
"classic" JVM.
Setting up your project for remote JSP debugging
Once you have created a JSP project, you need to set your project options
so that remote debugging is enabled: 
<ol>
From the Project menu, select Project
Properties. 
</li>
Click the Run/Debug tab.
</li>
From Debug Files As: dropdown list, select Remote
Debugging. 
</li>
Click OK. 
</li>
</ol>
Configuring the Remote Server
The following options must be changed on the host running the Apache/Jserv
server. These instructions assume the server is running Windows NT: 
Changes to jserv.properties
These options control which Java Virtual Machine is used and how it is loaded.

<ol>
For The Java Virtual Machine interpreter parameter <tt>wrapper.bin</tt>:

</li>
<ul>
[*]Comment out any existing entries by putting a <tt>#</tt> at the beginning
of the line.
<blockquote>
<pre>#wrapper.bin=C:\java1.1.8\bin\java.exe</pre>
</blockquote>
</li>
[*]Add a new entry with the full path of the <tt>java.exe</tt> that you want
to use. To use the JDeveloper 1.3 OJVM, put
<blockquote>
<pre>wrapper.bin=C:\Program Files\Oracle\JDeveloper 3.2\java1.2\bin\java.exe</pre>
</blockquote>
</li>
</ul>
For the Arguments passed to Java interpreter parameter <tt>wrapper.bin.parameters</tt>:
The value you put for this parameter depends on which Debugging Protocol
you will choose in the Remote Debugging Dialog in JDeveloper
when you start debugging.
</li>
<ul>
[*] If you want to use the JDeveloper 3.2 OJVM, put </li>
<blockquote>
<pre>wrapper.bin.parameters=-ferrari -XXdebugondemandquietport4000</pre>
</blockquote>
[*]If you want to use Java Platform Debugging Architecture, put
<blockquote>
<pre>wrapper.bin.parameters=-classic -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=4000 -Xdebug -Xnoagent -Djava.compiler=NONE</pre>
</blockquote>
The <tt>4000</tt> parameter defines the port number which the JDeveloper
debugger will use to communicate with the server. You can specify a different
port number, but it must match the port which you will enter in the Remote
Debugging Dialog in JDeveloper when you start debugging. 
</li>
</ul>
[*] For the PATH environment value passed to the JVM parameter <tt>wrapper.path</tt>
enter the location of <tt>jdwp.dll</tt>, which is part of the Java Platform
Debugging Architecture.
This parameter is only necessary if you will choose the Java Platform
Debugging Architecture debugging protocol:
<blockquote>
<pre>wrapper.path=C:\jpda\bin</pre>
</blockquote>
</li>
For the CLASSPATH environment value passed to the JVM parameter
<tt>wrapper.classpath</tt>: 
<ul>
Keep the location of <tt>ApacheJServ.jar</tt>. If it is not already
there, add it. 
<blockquote>
<pre>wrapper.classpath=C:\Program Files\Apache\JServ\ApacheJServ.jar</pre>
</blockquote>
</li>
Comment out the location of <tt>jsdk.jar</tt>. 
<blockquote>
<pre>#wrapper.classpath=C:\jsdk2.0\lib\jsdk.jar</pre>
</blockquote>
</li>
[*]Add the location of <tt>servlet.jar</tt> from JDeveloper 3.2.
<blockquote>
<pre>wrapper.classpath=C:\Program Files\Oracle\JDeveloper 3.2\lib\servlet.jar</pre>
</blockquote>
</li>
[*] Add the locations of <code>jdeveloper.zip</code> and <code>ojsp.jar</code>
from JDeveloper.
<blockquote>
<pre>
wrapper.classpath=C:\Program Files\Oracle\JDeveloper 3.2\lib\jdeveloper.zip
wrapper.classpath=C:\Program Files\Oracle\JDeveloper 3.2\lib\ojsp.jar
</pre>
</blockquote>
</ul>
</ol>
Changes to jserv.conf
<ol>
For the ApJServAction parameter: 
<ul>
[*] Comment out any existing <tt>ApJServAction .jsp</tt> entries by putting
a <tt>#</tt> at the beginning of the line. </li>
<blockquote>
<pre>
#ApJServAction .jsp /servlets/org.gjt.jsp.JSPServlet
</pre>
</blockquote>
[*]Add a new <tt>ApJServAction .jsp</tt> entry like this.
<blockquote>
<pre>
ApJServAction .jsp /servlets/oracle.jsp.JspServlet
</pre>
</blockquote>
</li>
</ul>
</li>
</ol>
Changes to zone.properties
<ol>
In the Servlet Init Parameters section: 
</li>
<ul>
Add the following lines. 
<pre>
servlet.oracle.jsp.JspServlet.initArgs=emit_debuginfo=true
servlet.oracle.jsp.JspServlet.initArgs=jspcompiler=oracle.jdeveloper.jsp.JspOjcCompiler
servlet.oracle.jsp.JspServlet.initArgs=classpath=C:\Program Files\Oracle\JDeveloper 3.2\java1.3\jre\lib\rt.jar
</pre>
</li>
</ul>
</ol>
Copying the JSP to the Apache/Jserv Server
Once you have restarted the server with the modified parameters, you need to
copy your JSP to the server's HTML root directory. For most Apache installations
this is <tt>C:\Program Files\Apache\htdocs</tt>. 
You also need to make sure the JSP is in your HTML directory in the JDeveloper
tree, typically <tt>C:\Program Files\Oracle\JDeveloper 3.2\myHTML</tt>. The
reason for this is JDeveloper uses the folder name as its package name.
Debugging a JSP
Debugging a JSP is very similar to debugging any other Java program.
<ol>
From the Run menu, select Debug
"filename.jsp". 
Start the JSP running (for example, start your web browser and open a
connection to the JSP). 
Debug as normal. 
</ol>
If you are using the JDeveloper OJVM debugging protocol, you will be able
to disconnect from the JSP container. This allows you to stop debugging, but
leave the JSP container running. In addition, you will be able to use two extra
debugging functions that are not available using the JDPA protocol - Run
to End of Method and Set Next Statement.
If you using JPDA, you must use Stop to end your debugging.
Using this method will also stop the JSP container.
<blockquote>

</blockquote>
null

Hi,
It again same as you do in your local server...You can monitor the BPEL process flow in the em console and debug..if its not sufficient....u can also monitor the logs located at
<SOA_Home>\user_projects\domains\domain1\servers\soa_server1\logs to debug.

OAS server-side JSP debugging

Hi All
Is there a way to do the OAS server side JSP debugging using JDeveloper or other tools?
ka
null

Hi
The pdf file only mentioned 4 ways to do that but didn't include the details on how to do it. Appreciate if you could you tell me more precisely on how to do it with OAS?
ka
null

Debugging in JDeveloper

Similar Messages

Maybe you are looking for