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.

Similar Messages

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 ?

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.

JVM options for WLS

Where can I find a complete list of available JVM options for WLS?
For example -Dweblogic.security.SSL.protocolVersion is not listed anywhere

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.

SQL Developer Hangs when connecting for Remote Debug

Hello,
I've been trying to use the Remote Debug feature of SQL Developer. We are writing a Web Application that connects to Oracle and I would like to debug a package function on the database server (which is not the same machine as my SQL Developer client).
To test my configuration, I tried connecting on SQLPlus creating a connection (by calling exec dbms_debug_jdwp.connect_tcp('xxx.xxx.xxx.xxx', 'xxxxx'); ) and calling a function which had a breakpoint and the debugging started immediately on SQL Developer. Then I tried putting the dbms_debug_jdwp.connect_tcp('xxx.xxx.xxx.xxx', 'xxxxx'); call inside the stored procedure I was debugging (prior to the line with the breakpoint) and it connected and got to the breakpoint successfully as well. So I'm pretty sure my firewall / user privileges are set up correctly.
So I modified the function that my web application eventually calls to create the connection (in order to remain in the same session) but whenever it gets to the connect_tcp line SQL Developer hangs and I'm unable to debug. I've realized that it only hangs if I have a breakpoint there. If I don't have a breakpoint then it creates a connection just fine. Of course without a breakpoint it's a bit difficult to debug isn't it? :)
My Sql Developer version is 3.0 and I'm connecting to Oracle 11.1.0 Below you can find a dump when running SqlDeveloper with console. My OS is windows XP and my Oracle instance is running on Linux.
I appreciate any help you can provide.
2012-01-27 16:08:30
Full thread dump Java HotSpot(TM) Client VM (11.0-b16 mixed mode):
"JDI Target VM Interface" daemon prio=6 tid=0x3398f800 nid=0x1574 runnable [0x3702f000..0x3702fa14]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.read(SocketInputStream.java:182)
at com.sun.tools.jdi.SocketConnection.readPacket(SocketTransportService.java:393)
- locked <0x097d3528> (a java.lang.Object)
at com.sun.tools.jdi.TargetVM.run(TargetVM.java:99)
at java.lang.Thread.run(Thread.java:619)
"JDI Internal Event Handler" daemon prio=6 tid=0x34a82c00 nid=0x15ac in Object.wait() [0x355ef000..0x355efa94]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at com.sun.tools.jdi.EventQueueImpl.removeUnfiltered(EventQueueImpl.java:171)
- locked <0x097218d0> (a com.sun.tools.jdi.EventQueueImpl)
at com.sun.tools.jdi.EventQueueImpl.removeInternal(EventQueueImpl.java:106)
at com.sun.tools.jdi.InternalEventHandler.run(InternalEventHandler.java:36)
at java.lang.Thread.run(Thread.java:619)
"JPDA Listener" prio=6 tid=0x35806400 nid=0x7b8 runnable [0x3533f000..0x3533fd94]
java.lang.Thread.State: RUNNABLE
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
- locked <0x095ec870> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:453)
at java.net.ServerSocket.accept(ServerSocket.java:421)
at com.sun.tools.jdi.SocketTransportService.accept(SocketTransportService.java:330)
at com.sun.tools.jdi.GenericListeningConnector.accept(GenericListeningConnector.java:136)
at oracle.jdevimpl.debugger.jdi.DebugJDIConnectorListen.run(DebugJDIConnectorListen.java:127)
at java.lang.Thread.run(Thread.java:619)
"Native Directory Watcher" prio=2 tid=0x35e47c00 nid=0x170c runnable [0x34fef000..0x34fefa14]
java.lang.Thread.State: RUNNABLE
at oracle.ide.natives.NativeHandler.enterWatcherThread(Native Method)
at oracle.ide.natives.NativeHandler$2.run(NativeHandler.java:252)
at java.lang.Thread.run(Thread.java:619)
"Background Parser" prio=6 tid=0x35c4a800 nid=0x17e0 waiting on condition [0x3832f000..0x3832fa14]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at oracle.dbtools.raptor.plsql.BackgroundParser$1.construct(BackgroundParser.java:139)
at oracle.dbtools.raptor.utils.NamedSwingWorker$2.run(NamedSwingWorker.java:115)
at java.lang.Thread.run(Thread.java:619)
"status-0" prio=2 tid=0x35d54400 nid=0x1208 waiting on condition [0x3812f000..0x3812fc14]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x064a8cf0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
at java.util.concurrent.DelayQueue.take(DelayQueue.java:160)
at oracle.ide.status.StatusExecutor$StatusQueue.take(StatusExecutor.java:329)
at oracle.ide.status.StatusExecutor$StatusQueue.take(StatusExecutor.java:291)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
"Background Parser" prio=6 tid=0x35dde800 nid=0xa00 waiting on condition [0x3782f000..0x3782fb14]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at oracle.dbtools.raptor.plsql.BackgroundParser$1.construct(BackgroundParser.java:139)
at oracle.dbtools.raptor.utils.NamedSwingWorker$2.run(NamedSwingWorker.java:115)
at java.lang.Thread.run(Thread.java:619)
"WeakDataReference polling" prio=2 tid=0x35f59c00 nid=0x1144 in Object.wait() [0x3802f000..0x3802fb14]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x08554ba8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x08554ba8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at oracle.ide.util.WeakDataReference$Cleaner.run(WeakDataReference.java:88)
at java.lang.Thread.run(Thread.java:619)
"Background Parser" prio=6 tid=0x35d00400 nid=0xe1c waiting on condition [0x37e2f000..0x37e2fc94]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at oracle.dbtools.raptor.plsql.BackgroundParser$1.construct(BackgroundParser.java:139)
at oracle.dbtools.raptor.utils.NamedSwingWorker$2.run(NamedSwingWorker.java:115)
at java.lang.Thread.run(Thread.java:619)
"TextBufferScavenger" prio=6 tid=0x35df1c00 nid=0xabc in Object.wait() [0x37c2f000..0x37c2fd94]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x0842dfe0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x0842dfe0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at oracle.ide.model.TextNode$FacadeBufferReference$PollingThread.run(TextNode.java:1949)
"pool-4-thread-1" prio=6 tid=0x33a11c00 nid=0x444 waiting on condition [0x33f0f000..0x33f0fa94]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x07ba2040> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1963)
at java.util.concurrent.DelayQueue.take(DelayQueue.java:164)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
"IconOverlayTracker Timer" prio=6 tid=0x3491a000 nid=0x1750 in Object.wait() [0x3792f000..0x3792fb94]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at java.util.TimerThread.mainLoop(Timer.java:483)
- locked <0x07b36968> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
"Timer queue for AWT thread" daemon prio=6 tid=0x34913c00 nid=0xdfc in Object.wait() [0x3772f000..0x3772fd94]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x075b5cc8> (a java.lang.Object)
at java.lang.Object.wait(Object.java:485)
at ice.util.awt.TimedAWTExecutor.nextElem(TimedAWTExecutor.java:108)
- locked <0x075b5cc8> (a java.lang.Object)
at ice.util.awt.TimedAWTExecutor.runScheduler(TimedAWTExecutor.java:130)
at ice.util.awt.TimedAWTExecutor$1.run(TimedAWTExecutor.java:19)
"WaitCursor-Timer" prio=6 tid=0x35ca5800 nid=0x1230 in Object.wait() [0x3752f000..0x3752fa14]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at java.util.TimerThread.mainLoop(Timer.java:483)
- locked <0x0719c1c0> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
"Timer queue for AWT thread" daemon prio=6 tid=0x35a1f800 nid=0x1444 in Object.wait() [0x3692f000..0x3692fb14]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x0719c240> (a java.lang.Object)
at java.lang.Object.wait(Object.java:485)
at ice.util.awt.TimedAWTExecutor.nextElem(TimedAWTExecutor.java:108)
- locked <0x0719c240> (a java.lang.Object)
at ice.util.awt.TimedAWTExecutor.runScheduler(TimedAWTExecutor.java:130)
at ice.util.awt.TimedAWTExecutor$1.run(TimedAWTExecutor.java:19)
"pool-2-thread-1" prio=6 tid=0x35a75800 nid=0x135c waiting on condition [0x3742f000..0x3742fc14]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x06d72e80> (a java.util.concurrent.SynchronousQueue$TransferStack)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:422)
at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:323)
at java.util.concurrent.SynchronousQueue.take(SynchronousQueue.java:857)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
"BaseTreeExplorer.NodeOpeningExecutor" prio=6 tid=0x359c6800 nid=0x1618 waiting on condition [0x3732f000..0x3732fc94]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x06d492a8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
"Scheduler" daemon prio=6 tid=0x35a44400 nid=0x131c in Object.wait() [0x3722f000..0x3722fd14]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x06d493e0> (a oracle.dbtools.raptor.backgroundTask.TaskLinkedList)
at java.lang.Object.wait(Object.java:485)
at oracle.dbtools.raptor.backgroundTask.TaskLinkedList.takeNextTask(TaskLinkedList.java:47)
- locked <0x06d493e0> (a oracle.dbtools.raptor.backgroundTask.TaskLinkedList)
at oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$SchedulerThread.run(RaptorTaskManager.java:429)
"Thread-8" daemon prio=6 tid=0x35a01400 nid=0x1390 in Object.wait() [0x3712f000..0x3712fd94]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x06d49460> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x06d49460> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at org.tmatesoft.svn.core.javahl.SVNClientImplTracker.run(SVNClientImplTracker.java:65)
at java.lang.Thread.run(Thread.java:619)
"ChangeSetService" prio=2 tid=0x3595dc00 nid=0x11d8 in Object.wait() [0x3682f000..0x3682fa94]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x06a26d80> (a oracle.jdevimpl.vcs.changeset.ChangeSetService)
at java.lang.Object.wait(Object.java:485)
at oracle.jdevimpl.vcs.changeset.ChangeSetService.awaitEvents(ChangeSetService.java:178)
- locked <0x06a26d80> (a oracle.jdevimpl.vcs.changeset.ChangeSetService)
at oracle.jdevimpl.vcs.changeset.ChangeSetService.eventLoop(ChangeSetService.java:199)
at oracle.jdevimpl.vcs.changeset.ChangeSetService.access$200(ChangeSetService.java:56)
at oracle.jdevimpl.vcs.changeset.ChangeSetService$2.run(ChangeSetService.java:138)
at java.lang.Thread.run(Thread.java:619)
"Thread-6" daemon prio=6 tid=0x3590e400 nid=0x1520 runnable [0x36b2f000..0x36b2fb14]
java.lang.Thread.State: RUNNABLE
at sun.print.Win32PrintServiceLookup.notifyPrinterChange(Native Method)
at sun.print.Win32PrintServiceLookup.access$100(Win32PrintServiceLookup.java:32)
at sun.print.Win32PrintServiceLookup$PrinterChangeListener.run(Win32PrintServiceLookup.java:302)
"TimerQueue" daemon prio=6 tid=0x330a9c00 nid=0x11b0 in Object.wait() [0x3672f000..0x3672fc94]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at javax.swing.TimerQueue.run(TimerQueue.java:236)
- locked <0x06887680> (a javax.swing.TimerQueue)
at java.lang.Thread.run(Thread.java:619)
"TimedCache-Timer" daemon prio=6 tid=0x33a85000 nid=0x76c in Object.wait() [0x3460f000..0x3460fa94]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x05f36890> (a java.util.TaskQueue)
at java.util.TimerThread.mainLoop(Timer.java:509)
- locked <0x05f36890> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
"JarIndex Timer" daemon prio=6 tid=0x33a83c00 nid=0x15a8 in Object.wait() [0x3410f000..0x3410fb14]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.util.TimerThread.mainLoop(Timer.java:509)
- locked <0x05e824b0> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
"AWT-EventQueue-0" prio=6 tid=0x33a6a400 nid=0x15e8 in Object.wait() [0x3400f000..0x3400fb94]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at com.sun.tools.jdi.TargetVM.waitForReply(TargetVM.java:281)
- locked <0x02fa0320> (a com.sun.tools.jdi.Packet)
at com.sun.tools.jdi.VirtualMachineImpl.waitForTargetReply(VirtualMachineImpl.java:1015)
at com.sun.tools.jdi.PacketStream.waitForReply(PacketStream.java:51)
at com.sun.tools.jdi.JDWP$Method$LineTable.waitForReply(JDWP.java:3651)
at com.sun.tools.jdi.JDWP$Method$LineTable.process(JDWP.java:3627)
at com.sun.tools.jdi.ConcreteMethodImpl.getBaseLocations(ConcreteMethodImpl.java:343)
at com.sun.tools.jdi.ConcreteMethodImpl.getLocations(ConcreteMethodImpl.java:262)
at com.sun.tools.jdi.ConcreteMethodImpl.locationsOfLine(ConcreteMethodImpl.java:120)
at com.sun.tools.jdi.ReferenceTypeImpl.locationsOfLine(ReferenceTypeImpl.java:893)
at oracle.jdevimpl.debugger.jdi.DebugJDI.getLocationsOfLine(DebugJDI.java:5254)
at oracle.jdevimpl.debugger.jdi.DebugJDIBreakpointFileLine.verify(DebugJDIBreakpointFileLine.java:71)
at oracle.jdevimpl.debugger.jdi.DebugJDIBreakpointPackageFileLine.verify(DebugJDIBreakpointPackageFileLine.java:83)
at oracle.jdevimpl.debugger.jdi.DebugJDI.breakpointAfterChange(DebugJDI.java:2546)
- locked <0x09721d70> (a oracle.jdevimpl.debugger.jdi.DebugJDI)
at oracle.jdevimpl.debugger.jdi.DebugJDIBreakpoint.afterChange(DebugJDIBreakpoint.java:386)
at oracle.jdevimpl.debugger.jdi.DebugJDI.putBreakpoint(DebugJDI.java:2426)
- locked <0x09721d70> (a oracle.jdevimpl.debugger.jdi.DebugJDI)
at oracle.jdevimpl.debugger.jdi.DebugJDI.putBreakpointPackageFileLine(DebugJDI.java:893)
- locked <0x09721d70> (a oracle.jdevimpl.debugger.jdi.DebugJDI)
at oracle.jdevimpl.runner.debug.Breakpoint.putBreakpoint(Breakpoint.java:1701)
at oracle.jdevimpl.runner.debug.DebuggingProcess.afterConnection(DebuggingProcess.java:1352)
at oracle.jdevimpl.runner.debug.DebuggingProcess.accept(DebuggingProcess.java:1704)
at oracle.jdevimpl.runner.debug.DebuggingListener$2.run(DebuggingListener.java:231)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
"AWT-Windows" daemon prio=6 tid=0x33a64000 nid=0x12e8 runnable [0x33e0f000..0x33e0fc94]
java.lang.Thread.State: RUNNABLE
at sun.awt.windows.WToolkit.eventLoop(Native Method)
at sun.awt.windows.WToolkit.run(WToolkit.java:291)
at java.lang.Thread.run(Thread.java:619)
"AWT-Shutdown" prio=6 tid=0x33a31c00 nid=0xd4c in Object.wait() [0x33d0f000..0x33d0fd14]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x05e826a0> (a java.lang.Object)
at java.lang.Object.wait(Object.java:485)
at sun.awt.AWTAutoShutdown.run(AWTAutoShutdown.java:259)
- locked <0x05e826a0> (a java.lang.Object)
at java.lang.Thread.run(Thread.java:619)
"Java2D Disposer" daemon prio=10 tid=0x33a41400 nid=0x1294 in Object.wait() [0x33c0f000..0x33c0fd94]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x05e82730> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x05e82730> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at sun.java2d.Disposer.run(Disposer.java:125)
at java.lang.Thread.run(Thread.java:619)
"Low Memory Detector" daemon prio=6 tid=0x33076000 nid=0x688 runnable [0x00000000..0x00000000]
java.lang.Thread.State: RUNNABLE
"CompilerThread0" daemon prio=10 tid=0x3306fc00 nid=0x910 waiting on condition [0x00000000..0x336df7bc]
java.lang.Thread.State: RUNNABLE
"Attach Listener" daemon prio=10 tid=0x3306e400 nid=0x162c runnable [0x00000000..0x00000000]
java.lang.Thread.State: RUNNABLE
"Signal Dispatcher" daemon prio=10 tid=0x3306d000 nid=0x17a4 waiting on condition [0x00000000..0x00000000]
java.lang.Thread.State: RUNNABLE
"Finalizer" daemon prio=8 tid=0x3305d400 nid=0xe3c in Object.wait() [0x333df000..0x333dfc94]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x05e00298> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x05e00298> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x33058800 nid=0x1228 in Object.wait() [0x332df000..0x332dfd14]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x05e00320> (a java.lang.ref.Reference$Lock)
"main" prio=6 tid=0x00bc7c00 nid=0x10e0 waiting on condition [0x00000000..0x0012fae8]
java.lang.Thread.State: RUNNABLE
"VM Thread" prio=10 tid=0x33055000 nid=0x194 runnable
"VM Periodic Task Thread" prio=10 tid=0x33077800 nid=0xfd0 waiting on condition
JNI global references: 2649
Heap
def new generation total 9216K, used 3904K [0x02cd0000, 0x036c0000, 0x05e00000)
eden space 8256K, 35% used [0x02cd0000, 0x02fb0330, 0x034e0000)
from space 960K, 100% used [0x035d0000, 0x036c0000, 0x036c0000)
to space 960K, 0% used [0x034e0000, 0x034e0000, 0x035d0000)
tenured generation total 121024K, used 61455K [0x05e00000, 0x0d430000, 0x2acd0000)
the space 121024K, 50% used [0x05e00000, 0x09a03eb0, 0x09a04000, 0x0d430000)
compacting perm gen total 71168K, used 70950K [0x2acd0000, 0x2f250000, 0x32cd0000)
the space 71168K, 99% used [0x2acd0000, 0x2f219bf8, 0x2f219c00, 0x2f250000)
No shared spaces configured.
Edited by: 910659 on Jan 27, 2012 7:45 AM

What I mean is that I put the connect_tcp command inside the package function I want to debug in order to ensure it's going to remain in the same session. e.g.:
Function GetValue Return Varchar2 Is
Begin
dbms_debug_jdwp.connect_tcp('xxx.xxx.xxx.xxx', '25255');
return 'My Value';
End;
I'm afraid I cannot post our code which causes this problem due to our information security policies and simple console and web applications failed to replicate the problem. The function creates a connection to Oracle SQL Developer (which can be seen in the environment with the small ladybug icon) if no breakpoints are set which obviously doesn't allow breaking into the function. However if a breakpoint is also specified in the Return line the connection seems to freeze Oracle SQL Developer. No ladybug icon is shown and no Remote Debug Session seems to open.

Weblogic service pack 4 debug mode, for remote debugging

Hi there,
I am using WebLogic Enterprise 5.1 Service Pack 4 on NT. I would
like to launch it in debug mode, so that I can debug some EJBs
using JBuilder4. JBuilder supports WL SP 4 only.
I installed JPDA and it is in path. When I try this command:
java
-ms64m
-mx64m
-classpath d:\weblogic\lib\weblogic510sp4boot.jar;.\classes\boot;
.\eval\cloudscape\lib\cloudscape.jar;
-Dweblogic.class.path=d:\weblogic\lib\weblogic510sp4.jar;.\lib\weblogicaux.jar;
.\license;.\classes;.\myserver\serverclasses;d:\weblogic\lib\jConnect.jar
-Dweblogic.home=.
-Djava.security.manager
-Djava.security.policy==.\weblogic.policy
-Xdebug
-Xnoagent
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=7001,suspend=y,server=y
weblogic.Server
the process hangs and nothing happens.
I included other newsgroup postings on the same subject below.
Thanks,
Ramesh
Subject: Re: Remote Debugging with WLE (JPDA)
Date: Wed, 16 Aug 2000 08:54:36 -0300
From: Wendell MacKenzie <[email protected]>
Newsgroups: weblogic.developer.interest.weblogicenterprise
I made a mistake. BEA's JavaServer DOES NOT today support the
JPDA debugger platform. Only the "old" Sun one which uses the agent
password stuff.
Sorry to have mislead you.
unless of course a BEA WLE guru in engineering has a trick that
allows this to work...?
Wendell MacKenzie wrote:
This works under Solaris7 using jpda1_0.
LD_LIBRARY_PATH=/opt/wle/5.1/lib:/usr/Solaris_JDK_1.2.2_05a/jre/lib/sparc:/usr/jpda1_0/lib/sparc>
export LD_LIBRARY_PATH
edit according to your host's installation dirs
get the startup args to your JavaServer's boot requirementsvia:
>
tmboot -n -d1 -i <ID> (where ID is the numeric id ofthe Java Server you want
to debug)
and then launch the process from the shell as in:
JavaServer -C dom=<DOMAIN> -i 6 -i 81 -u nodename -U<ULOG_PATH_PREFIX> -m 0
-A --
-Xbootclasspath:/usr/Solaris_JDK_1.2.2_05a/lib/tools.jar:/usr/Solaris_JDK_1.2.2_05a/jre/lib/rt.jar
-Xrunjdwp:transport=dt_socket,address=<PORT>,server=y,suspend=n-Xdebug
<SERVERIMPL>.jar <SERVER_SPECIFIC_ARGS>
Change each <XXXXX> as appropriate for your configuration.
Be sure to check your ULOG for the password generated, you'llneed it when
you launch your client
that will connect to the Java server at debug time.
Hope this helps.
Wendell
Scott Jones wrote:
Help,
Need to information on connecting TogetherJ or VisualCafe
to WLE. I have
been told to install JavaTM Platform Debugger Architecture,version 1.0
(JPDA 1.0).
Has anyone done this?
Any pointers,
Thanks,
[email protected]

WLE does not have service packs, you must be using WLS - you should post this in a WLS newsgroup. WLE
and WLS are 2 separate products.
Ramesh Babu wrote:
Hi there,
I am using WebLogic Enterprise 5.1 Service Pack 4 on NT. I would
like to launch it in debug mode, so that I can debug some EJBs
using JBuilder4. JBuilder supports WL SP 4 only.
I installed JPDA and it is in path. When I try this command:
java
-ms64m
-mx64m
-classpath d:\weblogic\lib\weblogic510sp4boot.jar;.\classes\boot;
.\eval\cloudscape\lib\cloudscape.jar;
-Dweblogic.class.path=d:\weblogic\lib\weblogic510sp4.jar;.\lib\weblogicaux.jar;
.\license;.\classes;.\myserver\serverclasses;d:\weblogic\lib\jConnect.jar
-Dweblogic.home=.
-Djava.security.manager
-Djava.security.policy==.\weblogic.policy
-Xdebug
-Xnoagent
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=7001,suspend=y,server=y
weblogic.Server
the process hangs and nothing happens.
I included other newsgroup postings on the same subject below.
Thanks,
Ramesh
Subject: Re: Remote Debugging with WLE (JPDA)
Date: Wed, 16 Aug 2000 08:54:36 -0300
From: Wendell MacKenzie <[email protected]>
Newsgroups: weblogic.developer.interest.weblogicenterprise
I made a mistake. BEA's JavaServer DOES NOT today support the
JPDA debugger platform. Only the "old" Sun one which uses the agent
password stuff.
Sorry to have mislead you.
unless of course a BEA WLE guru in engineering has a trick that
allows this to work...?
Wendell MacKenzie wrote:
This works under Solaris7 using jpda1_0.
LD_LIBRARY_PATH=/opt/wle/5.1/lib:/usr/Solaris_JDK_1.2.2_05a/jre/lib/sparc:/usr/jpda1_0/lib/sparc
export LD_LIBRARY_PATH
edit according to your host's installation dirs
get the startup args to your JavaServer's boot requirementsvia:
tmboot -n -d1 -i <ID> (where ID is the numeric id ofthe Java Server you want
to debug)
and then launch the process from the shell as in:
JavaServer -C dom=<DOMAIN> -i 6 -i 81 -u nodename -U<ULOG_PATH_PREFIX> -m 0
-A --
-Xbootclasspath:/usr/Solaris_JDK_1.2.2_05a/lib/tools.jar:/usr/Solaris_JDK_1.2.2_05a/jre/lib/rt.jar
-Xrunjdwp:transport=dt_socket,address=<PORT>,server=y,suspend=n-Xdebug
<SERVERIMPL>.jar <SERVER_SPECIFIC_ARGS>
Change each <XXXXX> as appropriate for your configuration.
Be sure to check your ULOG for the password generated, you'llneed it when
you launch your client
that will connect to the Java server at debug time.
Hope this helps.
Wendell
Scott Jones wrote:
Help,
Need to information on connecting TogetherJ or VisualCafe
to WLE. I have
been told to install JavaTM Platform Debugger Architecture,version 1.0
(JPDA 1.0).
Has anyone done this?
Any pointers,
Thanks,
[email protected]

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;

Best option for remote downlinking

I am going to be streaming video/audio to some clients all over the US, all of which will be using PC's.
90% of the time they are going to be in locations where a hardline to the internet isn't possible.
What is the best option for them to access my stream as well as provide me back a webcam feed?
Is a cell phone card as good as it gets now?
Thanks,
Chris

Your options here are entirely and completely dependent on the local network services. This could include cellular data packet networks (and there are various flavors), WISP, satellite data (Iridium, GlobalStar and such), dial-up at speeds anywhere from roughly 50 kilobaud down to unusable, local WiFi networks, or otherwise.
Satellite networks are the most pervasive, though do have technical limits and do have among the highest of the high prices. I'd not want to stream video (on a budget) on such networks.
If these clients are going to be located are fixed sites or specific geographic areas, you can potentially set up backhaul wireless networks. If local network coverage is bad (and the local terrain allows it), you can potentially set up your own WISP, and provide coverage for yourself and potentially others.
If this is the United States, you're going to encounter some rather severe limitations and network fragmentation outside the metropolitan areas. Inside the metropolitan areas, there are almost always options. Outside those areas, you'll find that some countries will tend to have more pervasive network services, and better wireless coverage. (DSL and cellular data coverage is very far from pervasive locally, and this is located in one of the most populous counties in a small US state. And the local geography is not particularly amenable to a WISP operating on a budget.)

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

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

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

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.

JVM options for remote debugging

Similar Messages

Maybe you are looking for