How to remote debug JSPs on Tomcat 5.0 from JDev 10.1.2

I can remote debug Java applications and servlets. But I can not make it stop within any JSP pages while doing remote debug. I have no problem if I debug locally within the built-in OC4J server.
I set my project properties with remote debugging -> Attaching to JPDA. I start my tomcat using catalina jpda start after setting environment variables JPDA_ADDRESS=8000 and JPDA_TRANSPORT=dt_socket.
Please help,
TIA

Ashraf, thanks for sharing your experience. I would like to comment on your precedure.
Jdeveloper 10.1.2
Tomcat 4.1.31 ( version 5.x.x won't work as it needs jdk 1.5 at least, and jdev is configured to run with 1.4 )I was able to use Jdeveloper 9.0.5 to debug a servlet running in Tomcat 5.5.9 with jdk 1.5.0. I would belive there is no fundamental obstacle for Jdeveloper 10.1.2 to debug Tomcat 5.x.x, thanks to the nature of JPDA.
a- backup $TOMCAT$\bin\catalina.bat.
b- edit $TOMCAT$\bin\catalina.bat to include the following:
set JAVA_OPTS=%JAVA_OPTS% -Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000Another way is to set your environment variable JAVA_OPTS. There is then no need to modify catalina.bat.

Similar Messages

Remote Debugging Jdev11 and Tomcat 5.5 ?

Hi,
How could i make remote debugging Jdevelopper11 and Tomcat5 ?
Where could i configure remote Tomcat option ?
Regards
Philippe

Here are some steps with JDev 10g
http://technology.amis.nl/blog/1984/java-platform-debugger-architecture-jpda-with-tomcat-oc4j-eclipse-intellij-idea-and-jdeveloper
JDev 11g should be basically the same.

How to remote debugging EJB in JDeveloper?

Here is the procedure I follow
1. configure weblogic startWebLogic.cmd file according to the instruction and start it
2. create a EJB project contains HelloWorld.java, HelloWorldBean.java, HelloWorldHome.java and Client.java, Bean has one method hello(), just return a String
3. in JDeveloper, configure project properties, set RUN/DEBUG to Remote Debugging as the instruction provided by Oracle
4. Then how should I do next?
select Client.java --> Debug --> attach it to the target weblogic
select HelloWorldxxx.java --> Debug --> attach it to the target weblogic
I tried the above and it attached to weblogic, after that, the program suspend there, nothing happen, no debug message, no outcome...
I have a question, the project have no EJB Descripter, How Client.java test program find EJB interface through JNDI?
Thanks
-- CHENLW --
Client.java
==// Copyright (c) 2000 qingniao
==package com.chemuser.ejb.HelloWorld;
==import javax.ejb.*;
==import javax.naming.*;
==import java.rmi.*;
==import java.util.Properties;
==
==/**
== * A Class class.
== * <P>
== * @author chenlw
== */
==public class Client {
==
== public static void main(String[] args) {
== try {
== Properties props = System.getProperties();
==
== Context ctx = new InitialContext(props);
== HelloWorldEJBHome home = (HelloWorldEJBHome)ctx.lookup("HelloHome");
== HelloWorldEJB hello = home.create();
==
== System.out.println(hello.hello());
==
== hello.remove();
== } catch (Exception ex)
== {
== ex.printStackTrace();
== }
==
== }
==}
==
==
null

Programming EJB with JDeveloper is not as easily as JBuilder4.0.
I am regret that I must give up JDevelopper which I like most.
Hope JDev Team will enhance these functions in the future.
Thanks
CHENLW

Remote debugging JSPs using Forte and Weblogic

I am compiling JSPs using a build script (ANT) and deploying it to weblogic server instance running on unix. when i mount the JSPs and my classes to Forte and connect to weblogic instance, I can debug the java files. But the JSPs i can't debug. I can put the break points in JSPs but the debugger is not stopping at that breakpoint when i run my application in the browser.

I guess I can answer the question myself...
Turns out that there was a problem in 1.3.0. BugParade #4342974.

How to do a JSP talks with my "EJB from tables" ?

Hi !!
I'm new to Jdev.
I have built a database, using MySql, and I also have built EJB from my tables.
My EJB are Entity Beans and I have used the Wizard to create it from tables of my data base.
Every EJB is working well and I have a simple JAVA client application which can use my
beans to edit data in my database.
Now I need create JSP pages that will use my beans, to edit my database too.
So, I have created a new project and in this project I have built a JSP page, in the same workspace
that has my beans' project.
But I don't know what must I do to put my JSP page connected with my beans.
1) What must I do?
2) Is it possible to put a JSP page talking with a Entity Bean, or it will be necessary to create session beans?
3) Is my beans' project a BC4J project? If not, how to change my beans' project to this goal?
Any hint will be very helpful?
Thanks.
Rodrigo Pimenta Carvalho.
Brazil.
==============================================================================

There is a new feature to support this in the 9.0.3 preview release.

How to on Debugging Mode for T-Code F110 from Script in Sub routine Pool Pr

Hi Every one....
I have done SAP-Script for Payment Vocher for T-code F110 ..I have a Sub Routine Program where I have few Form statements which is called by SAP - Script using Perform Statements, But my problem is when I set a break point in Sub Routine pool program, the out put is issuing with out Debugger ...
Could any one plz suggest me wht to do???
Help ful answers will be rewarded....
Regards,
sg

Hi,
First see if the 'Perform' statement is getting triggered in Script. To put a breakpoint in any script ( even if you do not know the form name, that is the best part ) is se38---->RSTXDBUG --->F8 & execute your pgm/Transaction. The control will wait in the form-debugger.
I hope this helps,
Regards
Raju Chitale

How to do debugging in WebLogic from JDeveloper

Hi All,
We in our project are just starting to use JDeveloper instead of Visual Cafe with Weblogic as App. Server. However i am facing this problem while debugging an EJB deployed from JDeveloper 9i to Weblogic 6.1.
On Clicking Debug|Debug <Project-name> brings up a dialog. After leaving the address field blank(Weblogic running on localhost, and as per your documentation, localhost is default) and port as 5000 (transport_dt_socket set as 5000), the following message comes:
Debugger attempting to connect to remote process at LocalHost 5000.And it doesn't do anything more.
Awaiting for your reply on this.
regards,
Hiamnshu

Hi,
The most important thing is that you need to ensure that WebLogic is start the Java command with debugging options. This is in the JDev documentation in the topic "Starting a Java Process in Debug Mode".
If you have JSP's and servlets you have other steps as well. I have included the generic steps for any application server. We have plans to post a 'How to remote debug JSP's deployed on Weblogic' in the near future. Keep posted.
1. You need to replace WebLogic's JSP engine with OJSP and you need to
setup debugging parameters for OJSP. This is not specifically in the JDev documentation, but you may be able to apply the information found in the topic "Remote Debugging in OC4J".
Here are some tips:
A. You'll probably need to specify the following jars in some WebLogic config file. The jar files are all located in <jdev_install>/lib/
xmlparserv2.jar
ojc.jar
jdev-rt.jar
ojsp.jar
ojsputil.jar
B. Add these jar files to the VM's classpath
C. The OJSP class name is oracle.jsp.runtimev2.JspServlet. You will need to specify this class where you configure your JSP engine information.
D. You need to pass the following debug parameters. Again this is set up in the app server configuration file(s):
debu[i]Long postings are being truncated to ~1 kB at this time.

Remote debug struts Tomcat 4.1

I'm trying to setup jdeveloper 10g to remote debug a struts application which is located in the web apps of the tomcat directory. I called myself setting up everything by using the help documentation. I'm doing something wrong, I need some help.

Hi.
For remote debugging, the Virtual Machine setting on the Runner options panel is not used. That Virtual Machine setting is used for local running/debugging, when JDev will be launching the debuggee process.
For remote debugging, you need to select the correct Remote Debugging Protocol. In the most recent JDev (the preview that came out in November/December 2004), that setting is in the Tools Preferences dialog box, on the Debugger - Remote panel. In previous versions of JDev, that setting is in the Project Properties dialog, on the Debugger - Remote panel (it's right under the Remote Debugging checkbox).
If you will be starting up Tomcat with ojvm (with -XXdebug,detached,port8080 option), then you want to select the "Attach to OJVM" radio button.
If you will be starting up Tomcat with Hotspot (with -Xdebug -Xrunjdwp:<blah blah blah> options), then you want to select the "Attach to JPDA" (or perhaps, but less likely, the "Listen for JPDA") radio button.
-Liz

Remote debugging a jsp

hi
i followed the steps in the following link for remotely debugging jsp;but when i put breakpoint in jsp's it didnt stop at that point;
http://helponline.oracle.com/jdeveloper/help/state/content/navSetId.jdeveloper/navId.4/vtAnchor.trouble/vtTopicFile.jdeveloper%7Ctuning%7Crem_p_main_oc4j%7Ehtml/

Hi.
I hope I can help.
Ok, first of all... Did you open up a browser and "hit" your JSP? This is done by JDeveloper automatically when you do local debugging with the embedded server and often users forget that they have to do it themselves for remote debugging?
If that's not the problem, it may be a difference between what JDeveloper thinks is the breakpoint's location and what the actual location is.
When you set a breakpoint in the code editor, JDeveloper figures out what the package, file, and line number are for the breakpoint. With breakpoints in .java files, the package is easily determined because of the package statement at the top of the .java file. However, with a breakpoint in a .jsp file, JDeveloper has to "predict" what the package will be after the JSP engine (in the server) has converted the jsp to Java.
To do this "prediction", JDeveloper will use the algorithm that the embedded server would use when it processes the jsp. The algorithm to figure out the package takes into consideration the relative path from the project's public_html directory to the jsp file.
So, check that the directory structure within your project's public_html directory exactly matches the directory structure that you have deployed to the stand-alone server that you are remote debugging.
Another thing you can do is to look for the jsp's class in the debugger's classes window. To do this, pause the debugger after your breakpoint has been missed. Look at the debugger's classes window by choosing View | Debugger | Classes. Try to find the jsp class - there will be a lot of classes there, but the jsp class will often begin with an underscore "_". Now, look at the package for that class. Does it match the package that is shown with your breakpoint in the Breakpoints window (View | Debugger | Breakpoints)?
I hope that helps.
-Liz

Remote Debug in oas 4.0.8.2 using JDeveloper3.1

Now I can do remote debug using JDeveloper3.1 in Tomcat or WebLogic!
But I can not do remote debug in Oralce Application Server 4.0.8.2.
Who knows how to remote debug in OAS, mainly for how to configure OAS to support remote debug, please tell me as quickly as possible!
I appreciate ... very much!!!!!!
We are using JDeveloper3.1 and OAS for our business application. So we must know how to remote debug in OAS with JDeveloper3.1.

In the JAva Environment settings for your OAS Application you should add the remote debugging name-value pairs using
X_OPTION
X_OPTION
runjdwp:transport=dt_socket,server=y,suspend=n,address=4000
X_OPTION debug
X_OPTION noagent
JAVA_COMPILER NONE
INITIAL_HEAP 32m
MAX_HEAP 32m
After adding the configuration start the OAS and try to connect to remote OAS VM for JDeveloper
raghu

Remote debug in pck

how to remote debug in pck? can anyone help?
which file i need to change to set to debug mode? i did not find the file
Message was edited by: Spring Tang

Hi Spring
The easiest way to enable debugging is through NWDS:
1. Configure NWDS to connect to your WebAS
2. Open the "J2EE Engine" view
3. Right-click the server node you wish to debug and choose "Enable debugging"
The server node will then restart with debugging enabled. The next step is to actually find an entry-point to start debugging. NWDS allows you to define debug configurations for Servlets/JSPs and Web Dynpro applications, so you need to:
4. Set a breakpoint in a Servlet, JSP or Web Dynpro application
5. Define a debug configuration for that application
6. Start the debugging session
Once the debugging session (and thus the debugging connection to the server) is active, you are not limited to debugging Servlets, JSPs and Web Dynpros but can set breakpoints in arbitrary locations.
Best regards,
Thorsten

Patchset3 (11.1.1.4/wls 10.3.4) Remote debugging JDPA in weblogic cluster

Hi,
I am using Patchset3 (JDeveloper 11.1.1.4/ weblogic server 10.3.4). I was wondering how i can remote debug with
a) weblogic managed server that is part of a weblogic cluster
b) the cluster itself that contains multiple managed servers.
Note that i do understand how to remote debug against a weblogic server (e.g. http://jdeveloperfaq.blogspot.com/2009/12/faq-4-how-to-remote-debug-adf.html), but have not been able to find out how i can achieve this against a cluster that has multiple managed servers. Any directions will be appreciated.
Thanks,

Hi,
haven't tried it but here are some suggestions that might be of help:
1) Each managed server for each cluster node should be setup for remote debugging. This means that each managed server must be started with the -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=n* options in the WebLogic start-up script. Also Tunneling must be enabled for each managed server for each cluster node.
2) Make sure that you specify a different connection port for each managed server. This is indicated by the address* specifier above.
3) It seems logical to me that you will need to start separate instances of JDeveloper - one for each managed server that you need to attach to.
Let us know how it turns out,
Nick

Remote debug - switch on/of via ini ??

Hi, I've read and understood how to remotely debug a VI -- it works quite well.
My question is - can I set the "Enable debugging" and "Wait for debugger on launch" flags in the build specification for the stand-alone real-time application for all my applications, and THEN turn that on or off via something like the .ini file?
This would be great as then we could just set those debugging flags on all our builds, and then be able to enable debug it when neeeded.
Jay
Solved!
Go to Solution.

It's for the feeling of accomplishment, getting a solution is a WIN! Kudos is a nice "Thanks *pat on the back* "
Though it should really be visible in the profile, as it's more important than Kudos.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

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

Remote debugging (jboss deployed) ejb using JDeveloper

Hi there
Does anyone know how to remote debug an ejb deployed in JBoss using JDeveloper (or perhaps know of a link?)? All I can find is this from Oracle:
http://www.oracle.com/technology/products/jdev/howtos/appservers/debug_in_jboss.html
But the cmd to replace in the $bin\run.bat file to enable remote debugging doesn't exist in my version of JBoss (jboss-4.0.1RC1).
Can anyone shed some light here?
Thanks very much in advance...Jon

In run batch file add
set JAVA_OPTS= -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n %JAVA_OPTS%

How to remote debug JSPs on Tomcat 5.0 from JDev 10.1.2

Similar Messages

Maybe you are looking for