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

Similar Messages

JSP Remote debugging from Jdev to WL 7.0

          I am trying to remote debug my JSP deployed on WL from Jdeveloper 903.
          I have included the parameters to make WL start in a debug mode.
          I have also included ojsp.jar, servlet.jar and ojc.jar in WL classpath.
          So I can start WL in debug mode, I can launch the url to get access to my JSP,
          a break point is included in the code but it doesn't stop at the break point.
          I am using JPDA.
          Do I have to modify something else to be able to remote debug my JSP?
          PS: remote debugging my EJB works fine.
          Thanks for your help


          Is there any possibility to change the JSP engine in Weblogic server and customize
          the new JSP
          with additional parameters, so that IDE's can debug JSP code itself?
          "Mike Herrick" <[email protected]> wrote:
          >
          >As far as I know this is behaving correctly.
          >
          >To debug a JSP via JDPA you have to compile your JSPs and put the Servlet
          >classes
          >the JSP compiler spits out in your IDE Classpath. Then you can debug
          >those Servlets
          >-- but you can't set break points in the JSP itself. Not the best.
          >
          >Some IDE Vendors add this on top of JDPA etc.
          >
          >I'm not 100% on this, but think I'm correct.
          >
          >Mike
          >
          >"Magali Richard" <[email protected]> wrote:
          >>
          >>I am trying to remote debug my JSP deployed on WL from Jdeveloper 903.
          >>I have included
          >>the parameters to make WL start in a debug mode. I have also included
          >>ojsp.jar,
          >>servlet.jar and ojc.jar in WL classpath. So I can start WL in debug
          >mode,
          >>I can
          >>launch the url to get access to my JSP, a break point is included in
          >>the code
          >>but it doesn't stop at the break point. I am using JPDA. Do I have to
          >>modify something
          >>else to be able to remote debug my JSP?
          >>
          >>PS: remote debugging my EJB works fine. Thanks for your help
          >>
          >

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.

Remote Debugging w/9iAS not working !

I tried posting this in the app server area but apparently, it's too difficult for anyone to answer. No replies.
We need to debug a deployed jsp that uses java beans.
The jsp/java beans app is in jdevleoper 9.0.3.1 (windows 2000).
I have deployed the application to Oracle 9ias java edition (9.0.3) on Red Hat Linux.
I know how to modify the project settings in jdeveloper for remote debugging.
when I start debug mode in jdeveloper I am prompted for the host name and port number for the remote debug session. What port do I use ?
Do I need to do something to start 9ias at a certain port ? If so, how do I do this ?
I have seen conflicting information on this that mainly refers to a standalone oc4j, not the oc4j in 9ias.
Frank

Hi,
We have gotten many requests for collateral that details these steps. We are currently working on such a document. Keep posted to the JDeveloper OTN website http://otn.oracle.com/products/jdev for updates on this.
-Stuart

Remote Debugging (Jdev 10.1.3 to AS 10.1.3)

Hi,
I have been trying to do a remote debugging by connecting Jdeveloper (version 10.1.3 production) to AS 10.1.3 mid-tier but the OC4J instance seems to be crashing the moment the jdeveloper makes the connection. However, before the crash, jdeveloper takes about 5minutes to connect to the server.
The OC4J is managed by opmn and not a standalone process. I am not sure if this makes any difference. Here are the changes that I made in the 10.1.3 server:
*) Modified opmn.xml to add the below:
<data id="java-options" value="-server -verbose:gc -Xmx512M -Xms128M -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=43503 -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:ParallelGCThreads=2 -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
(also tried removing "-server" option)
*) Modified orion-web.xml to add the below:
<init-param>
<param-name>debug_mode</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>developer_mode</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>encode_to_java</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>emit_debuginfo</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>jspjavacompiler</param-name>
<param-value>oracle.jdevimpl.jsp.JspOjcCompiler</param-value>
</init-param>
*) Modified global-web-application.xml to add the below:
<orion-web-app
jsp-cache-directory="./persistence"
servlet-webdir="/servlet"
development="true" >
I see the below message in the jdeveloper debug window when the OC4J instance crashes:
Debuggee process virtual machine is Java HotSpot(TM) Server VM.
Debuggee process is application server OC4J.
To test JSPs or servlets, you must start a browser.
Debugger disconnected from remote process.
I do not see any error in application.log file.
By setting up the remote debugging, I am hoping for a better portlet development experience.
Any help is appreciated.
Thanks,
Pandian.
Message was edited by:
apandian

The doc is kind of vague, but here's the root reference:
http://download.oracle.com/docs/cd/B25221_04/core.1013/b15976/opmnxml.htm#sthref144
There's a FAQ document that prescribes how the "restart" algorithm works, see 1.3:
http://www.oracle.com/technology/products/ias/ohs/htdocs/opmn-1013-faq.pdf
So to tweak this behaviour, you specify a speciifc <ping> element inside of the opmn.xml for the managed process you are using -- and set the timeout, interval, retry attributes to some combination that gives you a longer pause time.
http://download.oracle.com/docs/cd/B25221_04/core.1013/b15976/common.htm#CACGAIGH
         <ias-component id="default_group">
            <process-type id="home" module-id="OC4J" status="enabled">
               <module-data>
                  <category id="start-parameters">
                     <data id="java-options" value="-Xrs -server -XX:MaxPermSize=128M -ms512M -mx1024M -XX:AppendRatio=3 -Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
                  </category>
                  <category id="stop-parameters">
                     <data id="java-options" value="-Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
                  </category>
               </module-data>
               <start timeout="600" retry="2"/>
               <stop timeout="120"/>
               <restart timeout="720" retry="2"/>
               <ping timeout="300" />
               <port id="default-web-site" range="8888" protocol="ajp"/>
               <port id="rmi" range="12401-12500"/>
               <port id="rmis" range="12701-12800"/>
               <port id="jms" range="12601-12700"/>
               <process-set id="default_group" numprocs="1"/>
            </process-type>
         </ias-component>Now I did just see something that is either a bug, or a doc error. In the doc, it shows the attributes of the <ping> tag to be: timeout, retry, interval. However when you configure opmn.xml with these, it report an error.
Looking at the $ORACLE_HOME/opmn/conf/opmn.xsd file, it shows that only attributes are timeout and interval. You can't add a retry attribute. I'm not sure if this is a doc bug or an error in the XSD file.
Anyways, using the timeout parameter, for your DEBUGGING phase (not production!) you should be able to bump that up to a higher value to allow OPMN to wait longer for a response from OC4J before it nukes it.
-steve-

Remote debugging

Is it possible to set up IFS to enable remote debugging?
I'd like to be able to attach JDeveloper debugger to the IFS JVM.
I run IFS on a remote machine.
Thanks,
Roman
null

Roman,
Have you checked the online help in Jdeveloper there is a lot of information on remote debugging.
If you use 1.1 you should check the following which I've copied from the online help:
Configuring Apache JServ for Remote Debugging Java Server Pages
If you are using Apache Jserv, you can debug using either the Oracle Java Virtual Machine (JVM) debugging protocol or the Sun Java Platform Debugging Architecture (JPDA). When you start your remote debugging session, you will have to choose which method to use. Depending on which one you choose, your configuration options are a little different.
Using Oracle's JVM
To use Oracle's JVM debugging protocol, you'll need to change the JVM that Apache JServ uses, modify the parameters you send to the JVM, and modify the CLASSPATH for Apache JServ.
These changes must be made on the computer that is hosting Apache JServ. If you do not have permission to make these changes, talk with your administrator.
Changing the JVM
In the jserv.properties file, set the wrapper.bin parameter to the full path of the JDeveloper JVM (java.exe). For example,
wrapper.bin=C:\Program Files\jdeveloper\java1.2\bin\java.exe
Setting parameters
In jserv.properties, set the wrapper.bin parameter to
wrapper.bin.parameters=-XXdebugondemandquietport4000
The -XXdebug parameter options are the following:
ondemand
Start the java program right away and allow a debugger to connect any time. Without this option, the Java program stays halted until a debugger is connected.
port4000
Debugger must connect at the specified port. Without this option, the port is 4000.
quiet
Don't print connection messages. Without this option, connection messages are sent to standard error.
Changing the ApJServerAction entry
In jserv.conf comment out any existing ApJServAction .jsp entries by putting a # at the beginning of the line.]
#ApJServAction .jsp /servlets/org.gjt.jsp.JSPServlet
Add a new ApJServAction .jsp entry
ApJServAction .jsp /servlets/oracle.jsp.JspServlet
Adding servlet init parameters
In the servlet init parameters section of the zone.properties file, add the following lines.
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\java1.2\jre\lib\rt.jar
Setting the CLASSPATH
In jserv.properties, set wrapper.classpath to
wrapper.classpath=C:\Program Files\Oracle\JDeveloper\jswdk-1.0\lib\servlet.jar
Make sure that the location of ApacheJServ.jar is specified.
wrapper.classpath=C:\Program Files\Apache JServ\ApacheJServ.jar
Comment out the location of jsdk.jar.
#wrapper.classpath=C:\jsdk2.0\lib\jsdk.jar
Using JPDA
To use JPDA debugging protocol, you'll need to modify the parameters you send to the JVM, tell the server how to find the JDPA library, and modify the CLASSPATH for Apache JServ.
These changes must be made on the computer that is hosting Apache JServ. If you do not have permission to make these changes, talk with your administrator.
Setting parameters
In jserv.properties, set the wrapper.bin parameter to
wrapper.bin.parameters=-classic -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=4000 -Xdebug -Xnoagent -Djava.compiler=NONE
To see the invocation options for JPDA, see Sun VM Invocation Options.
If you are running on Solaris, you may also need to include stdalloc=y as part of the -Xrunjdwp paramater, like the following:
wrapper.bin.parameters=-classic -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=4000,stdalloc=y -Xdebug -Xnoagent -Djava.compiler=NONE
Adding the JPDA library
In jserv.properties, set wrapper.path to include the location of jdwp.dll. This file is is part of the Java Platform Debugging Architecture.
wrapper.path=D:\jpda\bin
If Apache JServ is running on Unix,
setenv LD_LIBRARY_PATH /home/jpda/lib/sparc:$LD_LIBRARY_PATH
setenv PATH /home/jpda/bin:$PATH
where home/jpda is the path to your JPDA installation. In addition, you will have to pass that environment variable through Apache to the JVM. To do that, in jserv.properties, add the following line:
wrapper.env.copy=LD_LIBRARY_PATH
Setting the CLASSPATH
In jserv.properties, set wrapper.classpath to
wrapper.classpath=C:\Program Files\Oracle\JDeveloper\jswdk-1.0\lib\servlet.jar
Make sure that the location of ApacheJServ.jar is specified.
wrapper.classpath=C:\Program Files\Apache JServ\ApacheJServ.jar
Comment out the location of jsdk.jar.
#wrapper.classpath=C:\jsdk2.0\lib\jsdk.jar
Let me know if this helps

Remote Debugging Help

I have to configure my project to debug an application which is deployed on Weblogic 8.1. I have added these parameter to weblogic start script -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=4000 and i have configure project to Attach to JPDA, but still if start debuggin a JSP its getting stated in Oracle OC4J server.

Under the project run/debug settings make sure you checked the remote debug option.

Internet Sales R/3 remote debugging

Hi,
Can anybody tell me, how to remote debugg a Internet Sales Application? I've read some lines in the Development and Extension Guide, but this is not a lot.
I don't understand how do debug a classfile. Because normaly the classfile will be compiled and deployed on the SAP J2EE. Is it possible to debugg this class with the remote debugging function of Eclipse?
Thank u for every answer,
regards Thomas

What is the solution for remote debugging, can you share.
Also, I have question regarding JSP page. How can I display name of jsp page on the browser for internet sales application. I know there is some variable like showmodulename to be set to true. I want to know how to use it. I tried but could not make it to work.
Thanks

Remote debugging of servlets

Hi there,
can anybody help me with remote debugging servlets and JSP running inside OC4J with JDeveloper 3.2.3? (JDK Version 1.3.1).
Any help would be very welcome!
Thanks in advance!
Stefan

Check out the following matrix for what features are supported from JDev 3.2.3 to OC4J. http://technet.oracle.com/products/jdev/htdocs/jdev323oc4j.html
For remote debugging Servelts check out http://otn.oracle.com/products/jdev/howtos/remotedebugservlet.html
raghu

Remote debugging hang

Have anyone enconter the remote debugging hang when debug using Jdeveloper with UCM? I got this happen sometimes in some enviroment. any solutions?
Thanks

Hi,
Thanks for reminding me to check on this.
Currently you can get to it in the data pane, but it isn't pretty.
Expand "out: oracle.jsp.runtime.OracleJspWriter".
The "buffer" field is what you are looking for. Unfortunately, you only see the first 100 characters as the value shown for a character array or String (it's prohibitively expensive to show more). To see more, you have to expand the array. However, when it is expanded, you only see one character per line, which is awful.
Right click on "buffer: char[8192]..."
Choose Adjust Range...
Make the range as big as you think you've written but be careful as it will be slow if the range is really big. 0 to 1000 seems to work okay for me. You can also make the range start in the middle, like 1000 to 2000.
The default range is 0 to 100.
Expand "buffer: char[8192]..."
You can also add a watch (main menu -> Run -> Add Watch... or Ctrl+F5)
"out.buffer" so you don't have to find the "out" and "buffer" items. You still have to do the Adjust Range part.
I'll work on making this easier in JDev 5.0.
Thanks,
Liz
null

Cannot Remote Debugging Weblogic 10

I can do a remote debugging in a same machine, but not from another machine. It appears to be some security issue. Basically start the machine with JAVA_OPTIONS=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=n option.
I know that the other machine can reach this machine. I can ping, I can connect to a simple test server on a different port. I did open the port 4000 on the firewall. So, it's not a network issue.
I can also use an IDE to connect to the server at port 4000 to debug.
From another machine, if I telnet this machine with port 4000, it gets disconnect after a couple seconds. If I do the same within the same machine, the telnet doesn't disconnect.
So, the 2 machines see each other. It's just Weblogic senses it's another machine and disconnect.
It points to security settings, but why the document here:
http://www.oracle.com/technology/products/jdev/howtos/weblogic/remotedebugwls.html
doesn't say anything about that?
Please help. Regards.

Hi,
Take a look at this webpage:
http://jsp.java.sun.com/javaone/javaone2000/pdfs/TS-1569.pdf
Pages 17-18 and 24-26 are about setting up WebLogic for remote debugging. Classpath information is on page 24.
Liz
null

Remote debugging on WAS 6.20

Hi,
we are running the developer studio for our ISA development on WAS 6.20.
Unfortunately the remote debugging doesn't seem to work, at least not as easilly as hoped. Hopefully this is because of lack of information rather than a non-working product. Hence below are the steps and associated questions:
I Go to Window --> preferences. Select SAP J2EE Engine.
The "...is installed on local host" option, when pressing Browse, only gives an error saying that "No local engine could be found!" and then a few sentences indicating that this would only work on unix using a standard path. This of course does not help for local Windows development.
The second option is to select the "...installed on remote host". This would be fine, but as far as I understand I don't have a messaging server if I am running the WAS 6.20 locally.
Question: If I can use this option for the locally running WAS then what should I put it in the message server host and port?
When this fails the alternative is to go to the server root, open up the \configtool\configtool.bat and tick the debug mode for the server on and set the port to for example 9999.
After this I switch to debug mode in the studio and select Run --> debug... from this screen double click on remote java application and fill in the connection properties with localhost and 9999.
Unfortunately this also ends up in "failed to connect to remote VM".
Are we going down the wrong path here or just missing something in this? I didn't expect it to be very difficult to set the remote debugging in place.
Thanks for any comments!
Cheers,
Kalle

Thank you for getting this sorted.
Just for sake of re-assurance to others who are trying this. It will work, but there are a few things to be aware of.
1. When I did the http://localhost:port/@@@DEBUG@@@
the debugsession screen had an empty port.
I fixed this by using the configtool and setting the port there.
Next time it then worked.
If you use the developer studio the only things you need to do to start the debugging is to select the debug icon --> Debug... and in there create a new remote application.
In the remote application set the server name and port (for me it was localhost and I defined in the deploytool the port to be 12800).
After that hit debug and you can see that you are connected to the server. If you are not then restart the server and try again.
After you have the server running and you try to run, from the IDE a JSP you will get an error, but when you access the application through the browser your IDE will pick that up and off you go!
The rest should now be standard debugging...

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

Debugging for JSP

I do a remote debugging for my j2ee application.
i want to do debugging for JSP ....like breakpoint etc etc
can you tell any such options available which would be compatible with eclipse .
my server is weblogic.
i heard lomboz is a plugin which does that kind of work.
but when i visited lomboz site ...dont see any such capability of jsp debugging .
does it really work ?
please comment

can you tell any such options available which would
be compatible with eclipse .MyEclipse

How to enable remote debugging for a session other than the current one

Hi all,
I am trying to figure out how to enable remote debugging for a session other than the one I am currently using.
More specifically, we have an application that is making database calls to Oracle 11gR2. Something is causing an exception during this invocation. My system is currently not set up to recompile said application, so I can't just add the debug call to the code and recompile. Therefore I would like to be able to log into the database (as sys, if necessary) and invoke dbms_debug_jdwp.connect_tcp on the desired session.
The docs indicate that I should be able to do so:
dbms_debug_jdwp.connect_tcp(
host IN VARCHAR2,
port IN VARCHAR2,
session_id IN PLS_INTEGER := NULL,
session_serial IN PLS_INTEGER := NULL,
debug_role IN VARCHAR2 := NULL,
debug_role_pwd IN VARCHAR2 := NULL,
option_flags IN PLS_INTEGER := 0,
extensions_cmd_set IN PLS_INTEGER := 128);
But when I try (even as sys), I get the following:
exec dbms_debug_jdwp.connect_tcp('1.2.3.4',5678,<session id>,<session serial>);ORA-00022: invalid session ID; access denied
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
00022. 00000 - "invalid session ID; access denied"
*Cause: Either the session specified does not exist or the caller
does not have the privilege to access it.
*Action: Specify a valid session ID that you have privilege to access,
that is either you own it or you have the CHANGE_USER privilege.
I've tried granting the 'BECOME USER' privilege for the relevant users, but that didn't help. I read something about having to set some kind of ACL as of 11gR1, but the reference documentation was very confusing.
Would someone be able to point me in the right direction? Is this even possible, or did I misread the documentation?

Interesting deduction, that would be very useful indeed. I hate recompiling just to add the debug call, and it can't be done in our production environment. But it seems unlikely to me it would be implemented this way.
I would cross-post this in the SQL AND PL/SQL forum though, as this is really a database issue, not with the SQL Developer tool. Do add the links to the other posts in each.
Regards,
K.

Remote debugging a jsp

Similar Messages

Maybe you are looking for