Remote Debug (iPlanet)

Hi,
How to config JDev (3.1) in my WorkStation, to use "iPlanet" WebServer and not "Web-to-go" to debug my servlets ?
I am using:
WorkStation: NTW 4.0(SP3), JDev 3.1 with JDK 1.2.2, JSDK 1.0.1.
Server: NTS 4.0(SP5) and iPlanet 4.0 SP1.
Can anyone help me ?

Hi,
There isn't a way to configure JDeveloper to use a different webserver for local debugging, but you could certainly try using it for 'remote' debugging (even if the webserver is running on your local machine).
See the following section of the online help for more information on configuring your webserver for remote debugging:
User Guides
Working with JDeveloper
Developing Programs with JDeveloper
Debugging Java Programs
Remote Debugging
Remote Debugging of Java Servlets
null

Similar Messages

Remote debugging on iPlanet 60sp5

I'm trying to get remote debugging working on iPlanet (Sun Web Server) version 60sp5 using jdk1.4.1. I think I've set all the setting correctly, but I get the error "Connection refused; Fatal error: Unable to attach to target VM."
Here are how things are set:
jvm12.conf for the server contains:
[JVMConfig]
jvm.enableDebug=1
jvm.compiler=NONE
jvm.option=-classic
jvm.option=-Xnoagent
jvm.option=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=3999
The the $ADMIN_SERV/start-jvm file contains:
# cat start-jvm
NSES_JDK=/usr/j2sdk1.4.1; export NSES_JDK
NSES_JRE=${NSES_JDK}/jre; export NSES_JRE
NSES_JRE_RUNTIME_LIBPATH=${NSES_JRE}/lib/sparc:${NSES_JRE}/lib/sparc/server:${NSES_JRE}/lib/sparc/classic:${NSES_JRE}/lib/sparc/native_threads:${NSES_JDK}/lib/sparc; export NSES_JRE_RUNTIME_LIBPATH
<snipped the rest>
I've stopped and restarted the admin server and the server instance I'm trying to debug.
When I run jdk 1.4 jdb, I get:
#/usr/j2sdk1.4.1/bin/jdb -attach 3999
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
<snip>
com.sun.tools.example.debug.tty.VMConnection.attachTarget(VMConnection.java:346)
at com.sun.tools.example.debug.tty.VMConnection.open(VMConnection.java:168)
at com.sun.tools.example.debug.tty.Env.init(Env.java:63)
at com.sun.tools.example.debug.tty.TTY.main(TTY.java:829)
Fatal error:
Unable to attach to target VM.
What detail am I missing? Or is JDK remote debugging not supported?
Thanks in advance.
Dave

How to perform remote debugging on windows server under Microsoft Live Account?
Host PC runs a Windows 8 signed in with a Microsoft Live Account. Target PC runs a Windows server 2012R2.
I installed Remote tools for Visual Studio 2013.4 on Target PC.
As I known, Windows server doesn't support Microsoft Live Account.
Hello,
Actually, we just need the system user account and the password of target pc, but the microsoft live account is just an account of local pc.
For more details, you could refer to the following blog which is quite similar to VS2013.
Running Visual Studio Remote Debugger in Domain Environment
Regards,
Carl
This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites;
therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from the Internet.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

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

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 eclipse

Hello!
I am new to eclipse...Can someone tell me how to use remote debug? I thought it is done by running "Debug..." after selecting the java file...Sorry for being so ignorant about this...I will really appreciate your help. Thank you.

You do not have to have a main() method in the application. In fact you can have a breakpoint in any Java component. It just has to be in debugger's scope and it'll get visited.
Example: Let's say you're rinning a Tomcat app. You can have a breakpoint inside a servlet's doGet() methof and when you invkoke the servlet from Firefox, Eclipse will pause the excution and will bring the debugger perspective up.
From the article "Eclipse Debug window should automatically pop-up with the stack pointer on your first breakpoint (See Figure 3: Breakpoint hit in Eclipse's debugger). After that, you can use all the various functions that the debugger has to offer, namely variable assignments, step-into, drop to frame, etc."
If you're not seeining anything, chances are that you're not executing that piece of code. Double check that and let me know.
Levent Gurses

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-

How to use Remote Debugging in JDeveloper 3.1 ?

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

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

Remote Debugging with SQL-Developer (APEX)

Hello all,
I have a problem with the Remote Debugging functionality in SQL Developer.
I want to debug a fuction that generate a SQL-Statement. This SQL is the basic of a report in APEX.
I grant the privilege DEBUG CONNECT SESSION and DEBUG ANY PROCEDURE for the user.
This is the PL/SQL in the report region:
declare
v_sql varchar2(32767);
begin
dbms_debug_jdwp.connect_tcp('192.168.2.1', 4200);
v_sql := generate_sql(:P1_TABLENAME);
dbms_debug_jdwp.disconnect;
return v_sql;
end;
When I run the page i get this error:
ora-30677: session is already connected to a debugger
But I can`t debug it in SQL-Developer.
Can you help me please?

Hi Scott,
Yes my call to this is in a on submit after computations and validations page process. Below is the code in which I get the insufficient privileges error:
BEGIN
IF :DEBUG = 'YES' THEN
    dbms_debug_jdwp.connect_tcp('10.200.37.223',4000);
END IF;
species_upload.load_tsv_file(:APP_USER, :P302_SURVEY_BROWSE, 'survey');
--null;
IF :DEBUG = 'YES' THEN
    dbms_debug_jdwp.disconnect;
END IF;
END; I tried running it in SQL workshop in Apex as
begin
   dbms_debug_jdwp.connect_tcp('10.200.37.223',4000);
end;and I still get the insufficient privileges error message.
My parsing schema is: SNHLIVE
And the APEX user is: APEX_PUBLIC_USER I got this by doing select USER from dual in the SQL Commands in APEX.
I have done the following:
grant DEBUG ANY PROCEDURE to SNHLIVE
grant DEBUG ANY PROCEDURE to APEX_PUBLIC_USER
grant DEBUG ANY PROCEDURE to ANONYMOUS
grant DEBUG CONNECT SESSION to SNHLIVE;
grant DEBUG CONNECT SESSION to APEX_PUBLIC_USER;
grant DEBUG CONNECT SESSION to ANONYMOUS
grant DEBUG on SNHLIVE.species_upload TO SNHLIVE;
grant DEBUG on SNHLIVE.species_upload TO APEX_PUBLIC_USER;
grant DEBUG on SNHLIVE.species_upload TO ANONYMOUS;What I followed was David's article: Link: [http://www.oracle.com/technology/oramag/oracle/08-may/o38browser.html?_template=/ocom/print]
Now i can get remote debugging work on the same database using SQL Plus and Java application but not in Apex.
Any ideas why?
Thanks in advance,
Paul.

Remote Debug (iPlanet)

Similar Messages

Maybe you are looking for