Remote Debugging WLS v. 8.1/ Windows: How to set JAVA_OPTIONS?

How does one set JAVA_OPTIONS with no "startWebLogic.bat" supplied with WLS v. 8.1, for remote debugging?
(Note: Prefer to not have to run in unix emulation.)

WebLogic 8.1 has the startWebLogic script file in user_projects/domains/<WLS_Domain>
 directory. <WLS_Domain> is the WebLogic Server Domain directory.
 Marvin Toll <[email protected]> wrote:
 >How does one set JAVA_OPTIONS with no "startWebLogic.bat" supplied with
 >WLS v. 8.1, for remote debugging?
 >
 >(Note: Prefer to not have to run in unix emulation.)

Similar Messages

Remote debugging wls 7

I'm having a problem trying to debug a WLS application. Using intellij to attach
to the WLS 7 instance it takes an infinitely long time to remote process.
i had a similar problem in v6 that was solved by changing the VM from hotspot to
classic.
Any help
Simon

 WebLogic 8.1 has the startWebLogic script file in user_projects/domains/<WLS_Domain>
 directory. <WLS_Domain> is the WebLogic Server Domain directory.
 Marvin Toll <[email protected]> wrote:
 >How does one set JAVA_OPTIONS with no "startWebLogic.bat" supplied with
 >WLS v. 8.1, for remote debugging?
 >
 >(Note: Prefer to not have to run in unix emulation.)

Remote Debugging WLS

Has anyone set up a script (Windows) to run WLS in debug mode (-Xdebug)
according to the JPDA spec using JDK1.2.2? I want to step into EJB from
JBuilder.
Thanks, Jon

Hi.
I modified one of our standard start scripts for WL 4.5.1 to do this. The
server does start with this script, but I haven't used it to step into an
EJB from an IDE.
Hope this helps,
Michael Young
BEA Systems
levyjj wrote:
Has anyone set up a script (Windows) to run WLS in debug mode (-Xdebug)
according to the JPDA spec using JDK1.2.2? I want to step into EJB from
JBuilder.
Thanks, Jon[startdebug12.cmd]

[OT: Windows] How to set Browser View Menu to Thumbnail?

Viewing a folder of jpg's is much nicer if I browse using the;
View Menu >>> Thumbnail mode
Does anyone know how to make LabIEW's File Path Browser assume this mode programatically?
Thank you,
Ben
Message Edited by Ben on 05-29-2008 11:11 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction
Attachments:
Path_Control.PNG ‏275 KB
Preview_Thmbnail_mode.PNG ‏80 KB
Set_Thmbnail_mode.PNG ‏34 KB

Thank you Andrey!
I'll use your link to highlight that request as definate scope creep!
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Remote debugging of a CVI DLL running on PXI with visual studio

Hello!
I would like to build my application using the CVI "module" for Visual studio but my problem is that i'm only capable to build DLLs which are able to run on the PXI but i can't remote debug them.
Is it possible to somehow set visual studio to remote debug the PXI?
Thanx in advance! (:

Hi,
What do you mean by debugging the PXI? What exactly is the dll doing ?
I will need more details before I can make any suggestions.
Kind regards,
Ion R.

How to set transaction isolation level for a method in a Local Interface

 By reference at:
 http://e-docs.bea.com/wls/docs61/ejb/reference.html#1071267,
 the value for method-intf can only be "Remote" or "Home".
 My question is--
 How to set transaction isolation level for a method inside a Local Interface or
 Local_Home Interface?
 Thanks.
 Xing


I'd try 6.1SP2. I'm pretty sure this works now.
 -- Rob
 Xing wrote:
 > I tried "Local", but got an error when deploying the EJB jar, saying that only
 > "Remote" or "Home" is allowed.
 >
 > Any idea?
 >
 > Xing
 >
 > Rob Woollen <[email protected]> wrote:
 > >
 > >
 > >Use LocalHome or Local.
 > >
 > >-- Rob
 > >
 > >Xing wrote:
 > >
 > >> By reference at:
 > >> http://e-docs.bea.com/wls/docs61/ejb/reference.html#1071267,
 > >> the value for method-intf can only be "Remote" or "Home".
 > >>
 > >> My question is--
 > >>
 > >> How to set transaction isolation level for a method inside a Local
 > >Interface or
 > >> Local_Home Interface?
 > >>
 > >> Thanks.
 > >>
 > >> Xing
 > >
 > >--
 > >
 > >----------------------------------------------------------------------
 > >
 > >AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
 > >
 > >by Michael Girdley, Rob Woollen, and Sandra Emerson
 > >
 > >http://learnWebLogic.com
 > >
 > >
 > >
 > >
 > ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 > ><html>
 > >Use LocalHome or Local.
 > >-- Rob
 > >Xing wrote:
 > ><blockquote TYPE=CITE>By reference at:
 > > http://e-docs.bea.com/wls/docs61/ejb/reference.html#1071267,
 > > the value for method-intf can only be "Remote" or "Home".
 > >My question is--
 > >How to set transaction isolation level for a method inside a Local
 > >Interface
 > >or
 > > Local_Home Interface?
 > >Thanks.
 > >Xing</blockquote>
 > >
 > ><pre>--
 > >
 > >----------------------------------------------------------------------
 > >
 > >AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
 > >
 > >by Michael Girdley, Rob Woollen, and Sandra Emerson
 > >
 > >http://learnWebLogic.com</pre>
 > > </html>
 > >
 > >
 AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
 by Michael Girdley, Rob Woollen, and Sandra Emerson
 http://learnWebLogic.com
 [att1.html]

How can I enable remote debug in weblogic to use with Rational RSA IDE?

How can I enable the remote debugging technique so that I can work with my IDE.
I use RSA by IBM as the IDE
What should be the changes in the setdomainenv or startweblogic?
I use 10.3
Please help.. ur help is appreciable...

Hi,
I did not make any console adjustments for debugging on my WebLogic 10.3.2.0 - however I am running in development mode on an "adminServer" (an option during the install)
In the console there is a debug setup page - that seems to have no effect for me (I can always debug) - so either it is a combination of development mode and/or the startWeblogic script from the Eclipse plugin.
However, these debug settings are likely for debugging into the server - you only want to debug your own app code right?
On the console page goto
http://localhost:7001/console/console.portal?_nfpb=true&_pageLabel=ServerDebugPage
servers | AdminServer | configuration-debug | expand weblogic
I see...
"Use this page to define debug settings for this server.
Debug settings for this Server
EnableDisableClear Showing 1 to 2 of 2 Previous Next
Debug Scopes and Attributes State
default Disabled
weblogic Disabled
EnableDisableClear Showing 1 to 2 of 2 Previous Next
Try expanding the whole tree and selecting the root to enable everything.
You will see the following
10-Dec-2009 11:53:46 o'clock AM EST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute DebugAbbreviation on weblogic.management.configuration.ServerDebugMBeanImpl@47a32e1b([base_domain]/Servers[AdminServer]/ServerDebug[AdminServer]) has been changed. This may require redeploying or rebooting configured entities>
<10-Dec-2009 11:53:46 o'clock AM EST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server AdminServer. This server must be rebooted in order to consume this change.>
<10-Dec-2009 11:53:46 o'clock AM EST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerDebugPage.>
When I debug WebLogic 10.3.2.0 from Eclipse 3.5 EE - I see the following in my server startup log which includes the "-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453" you mentioned.
Starting WLS with line:
c:\opt\wls10320\JROCKI~1.5-3\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\opt\wls10320\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\opt\wls10320\WLSERV~1.3 -Dwls.home=C:\opt\wls10320\WLSERV~1.3\server -Dweblogic.home=C:\opt\wls10320\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=c:\opt\wls10320\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
Listening for transport dt_socket at address: 8453
The server process listening on debug portl 8453 ooks like this
Oracle WebLogic Server 11gR1 PatchSet 1 at localhost [Oracle WebLogic Launch Configuration]
 BEA JRockit(R)[localhost:8453]
 Thread [Main Thread] (Running)
 Daemon Thread [Timer-0] (Running)
 Daemon Thread [Timer-1] (Running)
 Daemon Thread [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] (Running)
 Daemon Thread [weblogic.time.TimeEventGenerator] (Running)
 Daemon Thread [JMAPI event thread] (Running)
 Daemon Thread [weblogic.timers.TimerThread] (Running)
 Daemon Thread [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] (Running)
 Daemon Thread [Thread-7] (Running)
 Daemon Thread [ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'] (Running)
 Daemon Thread [ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'] (Running)
I hit a breakpoint and see
Daemon Thread [[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'] (Suspended (breakpoint at line 56 in ApplicationService))
 ApplicationService_5ptwty_Impl(ApplicationService).insertObjects(List<Cell>) line: 56
 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
 NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
 Method.invoke(Object, Object...) line: 597
 AopUtils.invokeJoinpointUsingReflection(Object, Method, Object[]) line: 310
 ReflectiveMethodInvocation.invokeJoinpoint() line: 182
 ReflectiveMethodInvocation.proceed() line: 149
 DelegatingIntroductionInterceptor.doProceed(MethodInvocation) line: 131
 DelegatingIntroductionInterceptor.invoke(MethodInvocation) line: 119
 ReflectiveMethodInvocation.proceed() line: 171
 MethodInvocationVisitorImpl.visit() line: 37
 EnvironmentInterceptorCallbackImpl.callback(MethodInvocationVisitor) line: 55
 EnvironmentInterceptor.invoke(MethodInvocation) line: 50
 ReflectiveMethodInvocation.proceed() line: 171
 ExposeInvocationInterceptor.invoke(MethodInvocation) line: 89
 ReflectiveMethodInvocation.proceed() line: 171
 DelegatingIntroductionInterceptor.doProceed(MethodInvocation) line: 131
 DelegatingIntroductionInterceptor.invoke(MethodInvocation) line: 119
 ReflectiveMethodInvocation.proceed() line: 171
 JdkDynamicAopProxy.invoke(Object, Method, Object[]) line: 204
 $Proxy68.insertObjects(List) line: not available
 ApplicationService_5ptwty_ApplicationServiceLocalImpl.insertObjects(List<Cell>) line: 306
 FrontController.generateGlider(PrintWriter) line: 240
thank you
/michael
http://www.eclipselink.org

How do I connect the debugger for remotely debugging PL/SQL?

Hi everyone,
Remotely debugging PL/SQL from JDeveloper and SQL Developer is something I have tried unsuccessfully to do.
The steps I took were to right-click my connection, select Remote Debug... and specify "4000" for the Port and "n.n.n.n" for the Local address which seems to correctly start the listener. (I used ipconfig to double-check the address.) Then, I run the anonymous block you see below.
begin
dbms_debug_jdwp.connect_tcp( 'n.n.n.n', 4000 );
end;
But, I always get the following error:
Error starting at line 18 in command:
begin
dbms_debug_jdwp.connect_tcp( 'n.n.n.n', 4000 );
end;
Error report:
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 2
30683. 00000 - "failure establishing connection to debugger"
*Cause:    An error was indicated when trying to establish a connection
           to a debugger. Usually a TNS error will display along with
           this message to further explain the problem, although this
           TNS error will likely be hidden if you choose to trap the error.
*Action:   Correct the indicated parameter value and try again.
Additionally, my firewall in Windows 7 is disabled, and I work remotely from home via VPN.
The instructions are thatI followed: Sue's Blog... again...: Remote Debugging with SQL Developer.
Any help would be greatly appreciated. Thanks!
James

I found the answer.
Object classes are missing.
The right insert code is down but I have a new question.
-How can I assign Resource acces to user in PL/SQL?
Right insert code:
declare
vn_retval pls_integer;
emp_session dbms_ldap.session;
emp_dn varchar2(256);
emp_array dbms_ldap.mod_array;
emp_vals dbms_ldap.string_collection ;
vv_ldap_host varchar2(256);
vv_ldap_port varchar2(256);
vv_ldap_user varchar2(256);
vv_ldap_passwd varchar2(256);
vv_ldap_base varchar2(256);
begin
vn_retval := -1;
vv_ldap_host := 'XXXXXXX';
vv_ldap_port := '389');
vv_ldap_user := 'LDAP_USER';
vv_ldap_passwd:= 'LDAP_PASSWD';
vv_ldap_base := 'LDAP_BASE';
dbms_ldap.use_exception := true;
-- Initialize ldap library and get session handle.
emp_session := dbms_ldap.init(vv_ldap_host, vv_ldap_port);
-- Bind to the directory
vn_retval := dbms_ldap.simple_bind_s(emp_session, vv_ldap_user, vv_ldap_passwd);
-- Process New Entry in the database
-- Create and setup attribute array for the New entry
emp_array := dbms_ldap.create_mod_array(4);
emp_vals(1) := 'NAME';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'cn', emp_vals);
emp_vals(1) := 'NAME';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'sn', emp_vals);
emp_vals(1) := 'top';
emp_vals(2) := 'person';
emp_vals(3) := 'organizationalPerson';
emp_vals(4) := 'orcluserv2';
emp_vals(5) := 'orcluser';
emp_vals(6) := 'inetOrgPerson';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'objectclass', emp_vals);
emp_vals.delete;
emp_vals(1) := 'NAME' || '1';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'userpassword', emp_vals);
-- DN for Entry to be Added under 'ldap_base'
emp_dn := 'cn=' || 'NAME' || ', ' || vv_ldap_base ;
-- Add new Entry to ldap directory
vn_retval := dbms_ldap.add_s(emp_session, emp_dn, emp_array);
-- Free attribute array (emp_array)
dbms_ldap.free_mod_array(emp_array);
-- Unbind from ldap directory
vn_retval := dbms_ldap.unbind_s(emp_session);
end;

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

How do I disable remote debugging in JDeveloper??

I am having a problem disabling the remote debugging feature inside JDeveloper 9i. I currently have a workspace in which I has set up a remotely debuggable project and another "normal" project which contains the client application that accesses my remote application. When I start the remote application, I am able to attach the remote debugger inside JDeveloper and it works just fine. However, when I attempt to debug my local project, it starts with the following JVM parameters :
java -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=1552
and fails to start since it cannot attach to a remote process. I have double-checked the project settings and the remote debugging checkbox is NOT select for the local project. I have even resorted to restarting JDeveloper, but that failed to resolve the problem.
Does anybody have any suggestions as to how to fix this problem?

Hi David,
Some things concern me about the java command you show in your post:
1. On Windows, JDeveloper should be starting javaw, not java. In your post, you show a java command. Is it really java or is it javaw?
2. JDeveloper should be specifying which JVM to use. In your post, you show a java command where there is no JVM specified (there is no -ojvm or -hotspot). Check your project settings - on the Libraries panel, what J2SE (JDK) are you using? on the Runner panel, what Virtual Machine is selected?
Other than that, the command you show in your post (the command that JDev launches when you try to debug your local project) contains (mostly) the correct command options for local debugging with a JVM which supports JPDA debugging (for example, classic or hotspot).
Let me explain the command options:
java -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=1552-Xdebug Enables debugging.
-Xnoagent Disables old debugging agent (also called sun.tools.debug).
-Djava.compiler=NONE Disables the JIT compiler.
-Xrunjdwp Loads the JPDA JDWP library.
:transport=dt_socket Use sockets for communicating with the debugger.
,server=y Listen for a debugger to attach.
,address=1552 Use port 1552.
JDev will use the above command options when you do local debugging with a JVM other than OJVM. (Note that -Xnoagent and -Djava.compiler=NONE are not required for HotSpot, but are accepted and ignored.)
The command that you show is not trying to connect to anything.
When JDev does remote debugging, it does not start the java process at all.
I think there is some other reason why your program does not start up. What other messages are displayed in the Log Window? Do you see messages like "Debugger attempting to connect to local process." or "Debugger connected to local process." or "Debugger unable to connect to local process."?
-Liz

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.

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

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.

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

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

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

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

Remote Debugging WLS v. 8.1/ Windows: How to set JAVA_OPTIONS?

Similar Messages

Maybe you are looking for