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
          >>
          >

Similar Messages

Cannot remote debug from JDev 10.1.3 on AS 10.1.2 running hotspot

Hi,
I've set up an embedded OC4J instance in an application server as described in the help topic, "Remote Debugging in OC4J" (with a few changes, such as the fact that I added startup options using the OC4J instance Admin page of EM, rather than at the command line (since the instance is embedded in a full AS). I followed the directions specifically for HotSpot, because that's the JVM the instance was set up to use, and I can't change it (I know OJVM enables lots more features, but that's the situation I'm in).
I've also configured my project for remote debugging, ensuring the host name and port matches, and trying both "Attach to JDPA" and "Attach to OJVM" (these being the only two options, except for starting a listener, which I don't think will help with a web application).
When I try to debug, though, I get:
Debugger unable to connect to remote process.
Should I be doing something differently?
Thanks much,
Avrom

I had the delete key quit working after accidentally pressing a key sequent that included the delete key. I don't know what keys were involved, but the delete key from that point on did nothing.
I am running JDeveloper 10.1.3.0.4 on Window XP.
To resolve the problem, I set the keyboard Accelerators back to 'Default' in JDeveloper.
I selected... Tools->Preferences->Accelerators
then click on 'Load preset' then I chose 'Default'
You may need to select something other than default for your platform, but that did the trick for me.

Remote Debugging in Jdev EA1.

Hey guys, what happen to remote debugging in Jdev EA1?
Thanks,
Tony

The remote debugging was moved to tools/project properties select run/Debug and then edit.
Thanks,
Tony

Remote debugging from Windows to Linux

Is there a full description of every step needed to do remote cross-platform C++ debugging? I'm using the Indigo version of Eclipse CDT on Windows and would like to debug an application on a remote Linux machine.
On Windows, I do not have the ability to install a compiler or cygwin, but I do have plink and ssh on Windows. I am able to access the remote machine via RSE SFTP (a la stackoverflow.com/questions/4216822/work-on-a-remote-project-with-eclipse-via-ssh). I do have VNC but I find that the Eclipse IDE is very unresponsive under that setup, hence the desire to develop and debug from a native Windows app.
This FAQ is the most complete (wiki.eclipse.org/CDT/User/FAQ#How_do_I_debug_a_remote_application.3F), but doesn't discuss how to deal with Windows using backslash paths and having a different filesystem root compared to Linux and its forward slashes.
I am able to get a remote connection by playing around with the suggestions here (www.eclipse.org/forums/index.php?S=5e54b35462bb80f79ebb9fbbaf93a288&t=msg&th=173880), resulting in console output that looks like:
Last login: Fri Apr 6 20:19:09 2012 from foo.bar.com
echo $PWD'>'
/usr/bin/gdbserver :12345 /linux/path/to/my/binary args_to_my_binary;exit
but it fails with "Error while launching command: gdb --version"
The old FAQ is very incomplete and seems out of date: wiki.eclipse.org/TM_and_RSE_FAQ#How_can_I_do_Remote_Debugging_with_CDT.3F
This suggests it's possible but does not have sufficient details on how to set the myriad configuration options in Eclipse: stackoverflow.com/questions/6044138/remote-debugging-in-eclipse-cdt
I suspect many people would benefit if there was a clear set of instructions in one place on how to make this happen.
--Gerald Dalley

OK. I just spent the last two days figuring this out, so here are step-by-step instructions that hopefully will help others (This list is unusually anal by the standards of this group, but really simple concrete instructions would have helped me).
on the target linux box, make sure you have gdbserver. If you don't, get the gdb sources. Note: Making gdb does not build gdbserver. Instead, you have to go into the gdbserver directory and configure/make there.
Run gdb on the linux box. In the startup banner, it will say what its target is. This will be something like x86_64-unknown-linux-gnu or i686-pc-linux-gnu. Remember this for later.
Install MinGW on your Windows box (I had trouble building gdb on cygwin, so I recommend MinGW).
Download expat from http://sourceforge.net/projects/expat/files/expat/2.1.0/.Note: Do not download the Windows expat installer. Download the sources instead.
In the expat directory. "./configure --enable-shared", make, make install.
Download the gdb sources
../gdb-7.4/configure --with-expat --target=x86_64-unknown-linux-gnu --host=i686-pc-mingw32
make, make install
Time to test. On your linux box, create and compile hello.cpp to hello.
On your linux box, gdbserver :4444 hello
Note:If you are on a corporate network, non-standard ports may be blocked. Set up an ssh tunnel if necessary.
Copy hello.cpp and hello to your Windows machine
From the MinGW prompt, run "x86_64-unknown-linux-gnu-gdb ./Hello" Note: Substitute the name of the gdb you built as appropriate based on the target platform you got in step 2.
In gdb, load the executable with "file hello"
target remote localhost:4444 Note: This assumes that you have an ssh tunnel on localhost. Modify appropriately.
Verify that gdb commands like break, cont, and run work here.
Now we want to run it from outside of MinGW. In Control Panel/System/Advanced/Environment Variables add something like E:\MinGW\bin to the path. This is necessary for the loader to find libiconv_2.dll, etc. Now verify that you can do the preceding step from an ordinary Windows command prompt.
Launch Eclipse (finally!). New debug configuration C/C++ attach to process.
In Main, give path to the copy of the Linux executable on the Windows system.
In Debugger tab, set Debugger dropdown to gdbserver. Set "GDB debugger" to something like "E:\MinGW\msys\1.0\local\bin\x86_64-unknown-linux-gnu-gdb.exe" based on where your gdb is. For Connection, choose TCP and fill in the hostname and port number you've been using from gdb in the previous steps.
Make sure gdbserver is running (it often quits when the program ends) and launch the debug configuration
In the gdb console, enter "file hello," "break main," and cont or run (sometimes it wants one. Sometimes the other) and voila, you should be there.
Let me know if this works, and I'll post it somewhere better.
Good luck,
Mike

Can not test, run or debug from JDev 10.1.3

Hi,
Just starting to play with latest JDeveloper 10.1.3 (installed latest version + patch), I've then created a new application (ADF BC + JSF), a new ViewObject and an app module.
When I try to test the app module, I'm getting the following error:
"C:\Oracle\Jdev\jdk\bin\javaw.exe" -classpath "C:\Oracle\Jdev1013\BC4J\jlib\bc4jtester.jar;C:\Oracle\Jdev1013\jlib\jdev-cm.jar;C:\Oracle\Jdev1013\lib\xmlparserv2.jar;C:\Oracle\Jdev1013\jlib\help4.jar;C:\Oracle\Jdev1013\jlib\share.jar;C:\Oracle\Jdev1013\jlib\jewt4.jar;C:\Oracle\Jdev1013\jlib\oracle_ice.jar;C:\Oracle\Jdev1013\jlib\ojmisc.jar;C:\Oracle\Jdev\jdk\jre\lib\rt.jar;C:\Oracle\Jdev\jdk\jre\lib\i18n.jar;C:\Oracle\Jdev\jdk\jre\lib\sunrsasign.jar;C:\Oracle\Jdev\jdk\jre\lib\jsse.jar;C:\Oracle\Jdev\jdk\jre\lib\jce.jar;C:\Oracle\Jdev\jdk\jre\lib\charsets.jar;C:\Oracle\Jdev\jdk\jre\classes;D:\Projects\jdev1013\SizzleFlowBuilder\Model\classes;C:\Oracle\Jdev1013\jdev\lib\jdev-rt.jar;C:\Oracle\Jdev1013\BC4J\lib\adfshare.jar;C:\Oracle\Jdev1013\BC4J\lib\bc4jmt.jar;C:\Oracle\Jdev1013\BC4J\lib\collections.jar;C:\Oracle\Jdev1013\BC4J\lib\bc4jct.jar;C:\Oracle\Jdev1013\jlib\commons-el.jar;C:\Oracle\Jdev1013\jlib\jsp-el-api.jar;C:\Oracle\Jdev1013\jlib\oracle-el.jar;C:\Oracle\Jdev1013\BC4J\lib\adfm.jar;C:\Oracle\Jdev1013\BC4J\jlib\adfui.jar;C:\Oracle\Jdev1013\BC4J\lib\adfbinding.jar;C:\Oracle\Jdev1013\jdbc\lib\ojdbc14dms.jar;C:\Oracle\Jdev1013\jdbc\lib\orai18n.jar;C:\Oracle\Jdev1013\jdbc\lib\ocrs12.jar;C:\Oracle\Jdev1013\diagnostics\lib\ojdl.jar;C:\Oracle\Jdev1013\lib\dms.jar;C:\Oracle\Jdev1013\BC4J\lib\bc4jdomorcl.jar;C:\Oracle\Jdev1013\BC4J\jlib\bc4jdatum.jar;" oracle.jbo.jbotester.MainFrame -X 10A4B929471 -H "jar:file:/C:/Oracle/Jdev1013/jdev/doc/studio_doc/ohj/bc4j_f1.jar!/bc4j_f1.hs"
java.lang.NoClassDefFoundError: oracle.jbo.jbotester.Res
     void oracle.jbo.jbotester.MainFrame$FileConnectAction.<init>(oracle.jbo.jbotester.MainFrame)
          MainFrame.java:829
     void oracle.jbo.jbotester.MainFrame.$init$()
          MainFrame.java:109
     void oracle.jbo.jbotester.MainFrame.<init>()
          MainFrame.java:132
     void oracle.jbo.jbotester.MainFrame.main(java.lang.String[])
          MainFrame.java:391
Then I added a new JSP and when I try to run or debug it, I'm getting:
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
**** Unable to obtain password from principals.xml. Using default.
C:\Oracle\Jdev1013\jdev\system\oracle.j2ee.10.1.3.36.73\embedded-oc4j\config>
C:\Oracle\Jdev\jdk\bin\javaw.exe -ojvm -classpath C:\Oracle\Jdev1013\j2ee\home\oc4j.jar;C:\Oracle\Jdev1013\jdev\lib\jdev-oc4j-embedded.jar -Dhttp.proxyHost=proxy.us.oracle.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=*.oracle.com|*.oraclecorp.com -Dhttps.proxyHost=proxy.us.oracle.com -Dhttps.proxyPort=80 -Dhttps.nonProxyHosts=*.oracle.com|*.oraclecorp.com -Xverify:none -DcheckForUpdates=adminClientOnly -Doracle.application.environment=development -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 -Doc4j.jms.usePersistenceLockFiles=false oracle.oc4j.loader.boot.BootStrap -config C:\Oracle\Jdev1013\jdev\system\oracle.j2ee.10.1.3.36.73\embedded-oc4j\config\server.xml
[waiting for the server to complete its initialization...]
OC4J startup failed
java.lang.NoClassDefFoundError: oracle.classloader.ClassLoaderQuery
     void oracle.oc4j.loader.boot.BootConfigurationFactory.<init>(java.lang.String[])
          BootConfigurationFactory.java:63
     oracle.classloader.util.InitialLoadersConfiguration oracle.oc4j.loader.boot.BootConfigurationFactory.create(java.lang.String[])
          BootConfigurationFactory.java:57
     void oracle.oc4j.loader.boot.BootStrap.main(java.lang.String[])
          BootStrap.java:22
Process exited with exit code 0.
Does anyone already see that?
Thanks.

My J2SE version was wrongly set to 1.3 instead of 1.5.
Now it works.

Could not configure Remote Debugging (JDev - AS 10g)

I'm trying to make work remote debugging from JDeveloper 10.1.2 on Oracle AS 10g, but I'm stuck. I tried to do every step from JDeveloper help:
1. Create remote debugging process.
- Done (I hope)
2. In the <jdev_install>/lib directory, copy xmlparserv2.jar to <OC4J_HOME>/lib. In the <jdev_install>/jdev/lib directory, copy ojc.jar and jdev-rt.jar to <OC4J_HOME>/home/lib
- If ORACLE_HOME is C:\Oracle\oracleas, then where is OC4J_HOME ? c:\Oracle\oracleas\j2ee\home ? But it means to create another 'home' directory, right ? But I have already created one OC4J instance called FirstOC4J, where our applications are deployed and it is located in c:\Oracle\oracleas\j2ee\FirstOC4J. Now what ? Which one?
3. Edit global-web-application.xml, but it is both in c:\Oracle\oracleas\j2ee\FirstOC4J\config and in c:\Oracle\oracleas\j2ee\home\config directory. Which one ?
4.Start OC4J in debug mode from a command line
- Why from command line? I always managed our FirstOC4J from Enterprise manager. I tried to put there the parameters from the command
java -ojvm -XXdebug,port4000,detached,quiet -jar oc4j.jar
but parameters inserted into OC4J Options or Java Options were rejected (OC4J wouldn't start). A little succes was running OC4J like this
how to set up for remote debugging?
But it required our FirstOC4J stopped and it meant our application won't run.
Please , could somebody make some step-by-step instructions for begginners or at least comment some above points ? Thanks.

I'm trying to make work remote debugging from JDeveloper 10.1.2 on Oracle AS 10g, but I'm stuck. I tried to do every step from JDeveloper help:
1. Create remote debugging process.
- Done (I hope)
2. In the <jdev_install>/lib directory, copy xmlparserv2.jar to <OC4J_HOME>/lib. In the <jdev_install>/jdev/lib directory, copy ojc.jar and jdev-rt.jar to <OC4J_HOME>/home/lib
- If ORACLE_HOME is C:\Oracle\oracleas, then where is OC4J_HOME ? c:\Oracle\oracleas\j2ee\home ? But it means to create another 'home' directory, right ? But I have already created one OC4J instance called FirstOC4J, where our applications are deployed and it is located in c:\Oracle\oracleas\j2ee\FirstOC4J. Now what ? Which one?
3. Edit global-web-application.xml, but it is both in c:\Oracle\oracleas\j2ee\FirstOC4J\config and in c:\Oracle\oracleas\j2ee\home\config directory. Which one ?
4.Start OC4J in debug mode from a command line
- Why from command line? I always managed our FirstOC4J from Enterprise manager. I tried to put there the parameters from the command
java -ojvm -XXdebug,port4000,detached,quiet -jar oc4j.jar
but parameters inserted into OC4J Options or Java Options were rejected (OC4J wouldn't start). A little succes was running OC4J like this
how to set up for remote debugging?
But it required our FirstOC4J stopped and it meant our application won't run.
Please , could somebody make some step-by-step instructions for begginners or at least comment some above points ? Thanks.

Remote Debugging Java Portlets

Dear experts,
I am a newbie to JDeveloper and Oracle9iAS Portal.
I created some Java Portlets with the JDev and the Portlet Wizard and would like to debug them when they are executed in the Portal.
Any help on how to setup the remote debugging? Are there any documents about this out there?
Your help is much appreciated.
Cheers,
Erik

Erik,
This is something we are looking at for enhancements for the Java Portlet Wizard, but for now you remote debugging from the Oracle9iAS OPMN. You can find out more about it here:
http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-logging-debugging-technote.html
Sue Vickers

Oracle application server 10g -remote debugging

We have oracle application server 10g with oc4j. How do we configure App server to start in debug mode so remote debugging from different machine can be done.
i configured remote debugging options in opmn.xml .in the jdeveloper i attached to JPDA .when i start remote debugging i have given hostname as localhost and portnumber as 5000.
i am getting this error
Debugger attempting to connect to remote process at localhost 5000......................
Debugger unable to connect to remote process.
I have done already remote debugging using oc4j stadalone app server.but this is the first time i am trying to connect with oracle application server 10g
opmn.xml
<ias-component id="OC4J">
<process-type id="home" module-id="OC4J" status="enabled">
<module-data>
<category id="start-parameters">
<data id="java-options" value="-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5000 -Xdebug -Xnoagent -Djava.compiler=NONE -Xms512m -Xmx1024m -Xss128k "/>
<data id="oc4j-options" value="-userThreads -properties -out log/out.log -err log/err.log"/>
</category>
<category id="stop-parameters">
<data id="java-options" value="-Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless=true"/>
</category>
<category id="restart-parameters">
<data id="no-reverseping-failed-ping-limit" value="2"/>
<data id="reverseping-failed-ping-limit" value="10"/>
</category>
</module-data>
<start timeout="600" retry="2"/>
<stop timeout="120"/>
<restart timeout="720" retry="2"/>
<port id="ajp" range="3301-3400"/>
<port id="rmi" range="3201-3300"/>
<port id="jms" range="3701-3800"/>
<process-set id="default_island" numprocs="1"/>
</process-type>
</ias-component>

Please refer
Re: Remote debugging with OC4J

Linux remote debug - can't load jdwp helper lib

Running RedHat 7.1 and jetty web server with jdk 1.3.1_09(?) (and ultimately trying to do a remote
debug from a Windows Eclipse machine).
Running jetty with cmd line args:
-Xmx256m -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Djava.compiler=NONE
linux says:
unable to configure JVMDI events
unable to initialize JVM helper library jdwp
loadJVMHelperLib failed
could not create the Java virtual machine
The linux jdk has /bin/libjdwp.so and /bin/libjdwp_g.so

silly me: I forgot the -Xdebug option. Now it works. Never mind.

JVM options for remote debugging

I'm run Tomcat 5.0.28 using service wrapper and i need help with set the required JVM options for remote debugging from ECLIPSE 3.0.0.

Where can I find a complete list of available JVM options for WLS?
For example -Dweblogic.security.SSL.protocolVersion is not listed anywhere
That is NOT a JVM options as I just explained in your other thread - see that thread for details.
JVM options
That "-Dxxx" syntax means you are specifying a system property on the Java command-line when launching Java.
That property can now be accessed in the Java app
You can make up and use ANYTHING you want when you write your own apps - those command line entries will just get added to the standard/default System properties as I explain in your other thread.
Consult the WebLogic documentation (or onliine help if WLS has such a thing) for info on the system properties that have been defined for WLS.

Not able to start remote debug listener

HI,
I'm using SQL Developer 1.1.0.23.64 and have read this article explaining remote pl/sql debugging.
http://sueharper.blogspot.com/2006/07/remote-debugging-with-sql-developer_13.html
When i try to start the debugger listener in SQL Developer (right click the database connection and choosing "remote debug") it seems like that the SQL Developer tries to connect to a listener instead of start listening. This is what console displays:
Debugger attempting to connect to remote process at LocalHost 4000...............Debugger unable to connect to remote process.
I thought that it should start listening instead of trying to connect to some other listener. What do I do wrong?
When I'm using remote debugging from JDeveloper every thing is fine!
Regards
Jacob

Hi
Has someone find an answer to this?
Debugger attempting to connect to remote process at localhost 4000.
...............................Debugger unable to connect to remote process.This is the same message you get when you try to run a debug session under JDeveloper, but with OJVM, not JPDA.
If this is a bug and will be fixed, can the SQL Developer team please make a post?

Debugging w/ JDev and iPlanet

Just curious if anyone has been successful with remote debugging from JDeveloper 3.1 where iPlanet 4 is the web-server?
I've tried the "General Settings" as described in the help files, but they cause the web-server to not restart.

Sorry!
          the debug option was NOT enabled (seems that my ant script is too
          complex at this stadium...)
          Cheers,
          Jan.
          [email protected] (Jan-Friedrich Mutter) wrote in message news:<[email protected]>...
          > Hi,
          >
          > I'd like to debug my Servlets/EJB's running on a Weblogic 6.1 SP4. My
          > IDE is Eclipse 2.1
          > To enable remote debugging I start Weblogic with that additional JVM
          > options:
          >
          > -classic -Xdebug -Xnoagent
          > -Xrunjdwp:transport=dt_socket,address=5000,suspend=y,server=y
          >
          > and configured my Remote Application in Eclipse accordingly.
          >
          > The connection successes.
          >
          > Problem: When I reach my breakpoint, Eclipse pops up an error message:
          > "Attempting to install a breakpoint in the type
          > com.xxx....
          > that has no line number attributes. The breakpoint cannot be
          > installed. Class files must be generated with the line number
          > attributes.
          > Reason:
          > Absent Line Number Information"
          >
          > I compiled my sources with enabled debug option.
          >
          > Any comments and ideas are appreciated.
          >
          > Cheers,
          > Jan.

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 (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 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

JSP Remote debugging from Jdev to WL 7.0

Similar Messages

Maybe you are looking for