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

Similar Messages

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

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

Jdeveloper remote debugging - Unable to find source error message

Hi,
I am trying to remote debug a simple Java application (non-web) using Jdeveloper. The Jdev debugger can connect to the remote debuggee, but unfortunately it throws me a message saying: 'Unable to find source file'. As a result, if I ignore this message, it simply ignores my source breakpoints.
Can anybody please help with any tips?
My project source is checked out from CVS and does not follow a conventional source path as such.
Thanks,
Neil.

The warranty entitles you to complimentary phone support for the first 90 days of ownership.

Can i run remote memory profiling and remote debugging at the same time .

can i run remote memory profiling and remote debugging at the same time .
i am using jdev9.0.5 and oc4j9.0.4 standalone server.
how to write the batch file to run both at the same time

Thanks for your help!
Another question. How do you turn off the ATT wireless transmitter? Also, there are more computers connected to the 2Wire network. I will have to set up a wireless pc to work with the Base Station after disconnecting the ATT transmitter. Easy answers for both, I hope?

Can i run remote profiling and remote debugging at the same time

can i run remote profiling and remote debugging at the same time .
i am using jdev9.0.5 and oc4j9.0.4 standalone server.

i think i am wrong

Remote debug in jdev3.1 and ias1.0

We want to remote debug in our web app. Our
env is Jdev3.1 for nt and ias1.0 for aix4.3.3
We use jpda(java platform debug architecture from sun) for remote debug, We found that jpda1.0 for solaris doesn't work in aix4.3.3. Where can we find jpda for aix? It's very important for us to set remote debug in ias1.0 for aix4.3.3.
Who can help me?

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

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.

(PC and Surface 8.1)bad pool header error: remote debugging using ARM device

Tools used:
Microsoft Visual Studio Professional 2013
Remote Debugger Monitor (Surface RT 8.1)
I have successfully activated the developer license as administrator.
I have attempted to run the test app on remote device but my pc crashes before or when reaching certification.
So far, I have attempted to run an app software for the ARM device; however, ever since I have upgraded the surface to 8.1, I constantly get the bad pool header crash, even after successfully connecting the pc to rt device.
is there any way I can resolve the issue so I can successfully to remote debugging?
any help is appreciated.

Hi,
Considering that the issue should be related to Windows RT 8.1, and Since we have limited testing environment, I suggest you submit a new case on Windows RT forum as they will be more professional on your issue:
This is the Windows RT 8.1 forum link.
http://answers.microsoft.com/en-us/windows/forum/windowsrt8_1?sort=lastreplydate&dir=desc&tab=Threads&status=&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&tm=1392101458999
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
Kelvin hsu
TechNet Community Support

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.

How to start listener in sql developer for remote debug

how to start listener in sql developer for remote debug ? Since the new version 1.1.0.23 is different with the old version for remote debug, I don't know how to start the listener on the new version for remote debug.
even follow the user guide below and not work . Experts on sql developer please help me with this.
Remote Debugging
To debug a procedure or function for a connection where the database is on a different host than the one on which you are
running SQL Developer, you can perform remote debugging.
Remote debugging involves many of the steps as for local debugging; however, do the
following before you start the remote debugging: Use an Oracle client such as SQL*Plus to issue the debugger connection command. Whatever
client you use, make sure that the session which issues the debugger connection commands is the same session which executes your PL/SQL
program containing the breakpoints.
For example, if the name of the remote system is remote1, use the following SQL*Plus command to open a
TCP/IP connection to that system and the port for the JDWP session:
EXEC DBMS_DEBUG_JDWP.CONNECT_TCP('remote1', '4000'); The first parameter
is the IP address or host name of the remote system, and the second parameter is the port number on that remote system on which the debugger
is listening.
Right-click the connection for the remote database, select Remote Debug, and complete the information in the Debugger - Attach
to JPDA dialog box. Then, follow the steps that you would for local debugging (for example, see Debugging a PL/SQL Procedure).
Debugger - Attach to JPDA This dialog box is displayed when you right-click a database connection name and select Remote Debug.
Use this
dialog box if you are using the Sun Microsystem's Java Platform Debugger Architecture (JPDA) and you would like the debugger to listen so
that a debuggee can attach to the debugger.
For more information about remote debugging, see Remote Debugging.
Host: Name or IP address of
the remote host on which SQL Developer should listen for the database to connect.
Port: Listening port number on the remote host. You can
choose any valid port number that is not in use by another process.
Timeout: The number of seconds that SQL Developer will wait for the
remote database to make a debugging connection. Don't Show Dialog Box Before Connecting: If this option is checked, this dialog box will not
be displayed before future connections for remote debugging

You're not the only one:
Not able to start remote debug listener
Re: remote debug question at version 1.1.0.23 64

Remote Debug mode while starting Weblogic server using my eclipse plugin

Hi
When am starting the Weblogic server via my eclipse it is opening in Remote Debug mode. Can anyone tell me how do I change the preferences/configure so that it doesnt run in debug mode.
NOTE:I have deployed the application and ran number of times, till yesterday it wasn't starting in this mode, though I haven't changed any settings since then, it is starting in Remote Debug mode.
Thanks,

The above issue is resolved by adding this to setDomainEnv.sh :
ALTERNATE_TYPES_DIRECTORY="${WLPORTAL_HOME}/portal/lib/security"
export ALTERNATE_TYPES_DIRECTORY
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.alternateTypesDirectory=${ALTERNATE_TYPES_DIRECTORY}"
# weblogic extension directories (system jars)
if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
WEBLOGIC_EXTENSION_DIRS="${WEBLOGIC_EXTENSION_DIRS}${CLASSPATHSEP}${WLPORTAL_HOME}/p13n/lib/system"
export WEBLOGIC_EXTENSION_DIRS
else
WEBLOGIC_EXTENSION_DIRS="${WLPORTAL_HOME}/p13n/lib/system"
export WEBLOGIC_EXTENSION_DIRS
fi
WEBLOGIC_EXTENSION_DIRS="${WEBLOGIC_EXTENSION_DIRS}${CLASSPATHSEP}${WLPORTAL_HOME}/light-portal/lib/system${CLASSPATHSEP}${WLPORTAL_HOME}/portal/lib/system${
CLASSPATHSEP}${WLPORTAL_HOME}/info-mgmt/lib/system${CLASSPATHSEP}${WLPORTAL_HOME}/analytics/lib/system${CLASSPATHSEP}${WLPORTAL_HOME}/apps/lib/system${CLASSP
ATHSEP}${WLPORTAL_HOME}/info-mgmt/deprecated/lib/system"
export WEBLOGIC_EXTENSION_DIRS
WEBLOGIC_EXTENSION_DIRS="${WEBLOGIC_EXTENSION_DIRS}${CLASSPATHSEP}${WLPORTAL_HOME}/content-mgmt/lib/system"
export WEBLOGIC_EXTENSION_DIRS
if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.ext.dirs=${WEBLOGIC_EXTENSION_DIRS}"
export JAVA_OPTIONS
fi

How to Network Interface for Remote Debugging in Adobe Flash Professional CS6?

How to Network Interface for Remote Debugging in Adobe Flash Professional CS6?

Check out : http://helpx.adobe.com/flash/using/whats-new-cs6.html
In that click on "Choose network interface for remote debugging for AIR" section.
Hope it helps.

Advantages of using Oracle JVM over JPDA for Remote Debugging?

What are the "additional features" that the documentation hints at when using the Oracle JVM for remote debugging vs. the JPDA protocoL? Can a member of the JDEV briefly address this? What exactly am I losing when using JPDA?

I am not getting anywhere with 'NCOMPing' the stuff. Attempts to NCOMP keeps erroring out . The first of the errors is
'Error while determining classes contained in jsch-1.29_minimalClassListAndTCD
mper.java
Exception oracle.aurora.sqljdecl.ParseException: Encountered "-" at line 14
column 18.
Was expecting one of:
"extends" ...
"implements" ...
The following operations failed
jsch-0.1.29_minimalClassListAndTCDumper.java: creation
exiting : Failures occurred during processing
Kuassi, I have looked at a few of your posts where you make mention of a file titled 'Settings_os.properties'. I see no such file in my Oracle installation. What am I missing here ?

WD Java Remote Debug problem: Release Process from debugging

Hi Community,
when I used to debug Web Dynpro Java from the SAP Developer Studio (eclipse) to a remote host (Portal AS NW Java), it works fine for the first run. After disconnecting the remote debug session (server0), I changed the coding and try to debug again with the effect that the old coding is still used from the server process (server0) even though the parameter "Create and Deploy archive" is set (enabled) in the debug configuration. Furthermore the funktionality of "Relase process from debugging" option in the J2EE Engine dosn't react / work.
I think that the debug session is still running and the Developer Studio is not able to send any "Kill" statement to the server process for ending this session.
I tried following:
A. Rebuild Project and Deploy the archive on the "normal" way
B. Reopen the Developer Studio itself
C. Start the Project in debugmode again and chose the option "Terminate All"
...all without any success.
The only way is to restart the whole server process server0 again with the same trouble after the first debug.
Did any of you have a clue or experience to clear or kill the debugsession from the process so that next debugsessions can be started, please reply.
Thanks
Used Basic Manuell
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/849170e3-0601-0010-d59e-ddfce735fac5

So, I'm having the same issue, but it's like I'm chasing down a port. The first time I got these error messages
Connecting to the database DEV.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '555.12.18.288', '5950' )
ORA-30683: failure establishing connection to debugger
ORA-12535: TNS:operation timed out
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database DEV.Our network staff found a bunch of other denials in the firewall logs
/5185
/5200
/5236
/5815
/5950 Now that they've those allowed, I tried to start debug again, and this time I got
Connecting to the database DEV.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP('555.12.18.288', '6266' )
ORA-30683: failure establishing connection to debugger
ORA-12535: TNS:operation timed out
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database DEV.What gives? Do I just keep trying until I get all of the ports allowed?
Thanks,
---=Chuck

Remote Debug in oas 4.0.8.2 using JDeveloper3.1

Similar Messages

Maybe you are looking for