Enabling tracing in remote debugging

Hello,
I am wondering how to enable tracing in remote
debugging. Here is what I now how to do:
1) how to attach to JDPA,
2) run till the breakpoint.
Next, when I try to step in, or step over
the process is always run until the next break
point regardless of whether I have the
required classes in the source path and
in the "tracing ... include" list.
I would appreciate any help,
Vadim
P.S. 1) Thanks for answering my previous question
about customizing ant. I figured how to do it earlier
on my own and wanted to post a reply but
couldn't do it. The system wouldn't find the
topic.
2) As far as JB concerned, the whole process of remote
debugging is pretty straight forward. I can help if anyone intersted.

Hi Vadim,
well, I am a newbie and would like some help how to setup the Jdeveloper and IAS for remote debugging my java portlets.
If you like to contact me privatly: [email protected]
Thanks
Erik

Similar Messages

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

Issue getting Edge Code Preview 3 to enable Remote Debugging

Hi all,
I am using the latest version of Chrome as my default browser. I opened up ECP3 and pointed to the project I wanted to use it for (WordPress site on WAMP server). I then clicked live preview and it opened the URL up properly in Chrome. Moments later, a notification in Edge Code Preview 3 pooped up saying I needed to re-launch Google Chrome with remote debugging enabled. So I clicked Relaunch. Minutes passed, and nothing happened. So I relaunched Chrome myself, clicked live preview again, and the same message comes up.
I have tried launched Chrome via Live Preview, I have restarted my computer, and closed all Pinned Tabs in Chrome. What is going on here?

Hmm, this seems like a smiliar issue to this - http://forums.adobe.com/thread/1159001?tstart=0
Can you try forcing Chrome to run with remote debugging enabled? http://www.chromium.org/developers/how-tos/run-chromium-with-flags - and see if Live Preview works? That's not a solution but will help in figuring out where the break is.
I'm also going to log an issue on this so we can start tracking it.
Sorry about the hassle!
=Ryan
[email protected]

Remote debug instructions. can't find Toolbox, hence no settings, hence no enable remote, FF34.0.5

FF34.0.5
https://developer.mozilla.org/en-US/docs/Tools/Remote_Debugging/Firefox_for_Android
instructions lead me to no "Toolbox". Can't find.
Developer toolbar has "Tools" but no "Settings therein.
Tools>Edit Tools &/or Options>options not appropriate.

Thanx - I will try that wheeze, it may work on FF Portable 34.
in desperation I installed Firefox Developer edition because I was using Firefox Portable (34.0.5) as my main development engine on sticks & fast external HDDs..
Hmmmmmmm
Let us just say that the Developer Edition can't give me working breakpoints (within functions) on my 600 line JavaScript, locally. When connected to the internet and running similar pages on the web I get erratic breaks where no breakpoints exist. Maybe it can't handle the other 500 code lines ( a lexicon) and it has exceeded some limit that was not there before. eg http://stroudvoices.co.uk/c/
The original problem was to do remote debugging on an Android phone. That failed completely. Worse - I can't run my pages on Chrome/Android now because FF/Android was defaulted and after removing that default Chrome is no longer offered.
Looks like I have to abandon all updates on Portable Firefox as a precaution. That at least behaves as a debugging environ. Or make IE &/or Chrome as my preferred SDK. I am not looking forward to future "improvements".

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.

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

CF Builder w/ Coldfusion 9 remote debugging problem

Have coldfusion9 installed on my linux server, everything works fine, can access the admin page, run basic files, etc.
Have CF Builder Beta installed on mac, can write CF files and run them from linux server.
Trying to get remote debugging working and following the directions for starting up the Authentication server via adminstart.sh, runs fine, changed security.properties ips to be *. When I create the server definition in CF Builder I see on the Authentication server:
error Authentication failed: Login Failed
Even though I have enabled RDS, Debugging, etc via server config and i enter same name/pw (admin/mypassword) as when I login via web.
Therefore, I'm unable to control the server and when I try to debug, it says it launches but refuses to stop at any breakpoints.
Any help appreciated as I've read through as many docs as I can find and haven't been able to resolve this.
Thanks

Make sure that the port is not blocked by the firewall. Also, check this : http://forums.adobe.com/message/2636413

Remote Debug - .SDA File or Adapter

I have configured PCK Server and deployed sample Adapter. I have enabled debug mode on server to debug java code on NWDS.
.SDA file consists of .rar and inturnally consists of .jar file (JAva Application). I have manually build .rar from NWDS JAva Application generated .jar file, and also manually generated .sda file. These file generations are 100% successful and deployed 100% Successful.
Now I want to debug java code enabling remote debug, however, after I attached to remote server, it is not kicking java code even I put any breakpoints.
Server environment is on SAP PI 7.0 PCK Environment.
NOTE: You get double points for right answer with my subscription.

Hi Ravi,
Could you tell me how did you achieve this? I am trying to do the same.
VJ

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

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

Remote debug listening socket failure

I am getting the following error when starting Weblogic with remote debugging enabled:
Error [4] in accept() call!
err:: Interrupted system call
Socket transport failed to init.
dt_socket transport error; accept failed, rc = -1
My java startup parameters include:
-Xdebug -Xnoagent -Xms64m -Xmx64m -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=3998
,suspend=n
I am using JDK1.2.2 and am running with the JDK opposed to JRE which I understand
is required when trying to remote debug with 1.2. I have $JPDA/lib/sparc in my
LD_LIBRARY_PATH and jpda.jar in my classpath.
Can anyone help please?

Problem resolved, thanks.
"Moby" <[email protected]> wrote:
>
I am getting the following error when starting Weblogic with remote debugging
enabled:
Error [4] in accept() call!
err:: Interrupted system call
Socket transport failed to init.
dt_socket transport error; accept failed, rc = -1
My java startup parameters include:
-Xdebug -Xnoagent -Xms64m -Xmx64m -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=3998
,suspend=n
I am using JDK1.2.2 and am running with the JDK opposed to JRE which
I understand
is required when trying to remote debug with 1.2. I have $JPDA/lib/sparc
in my
LD_LIBRARY_PATH and jpda.jar in my classpath.
Can anyone help please?

Remote debugging issue: Address already in use

First, I want to explain that to use remote debugging in oracle UCM server (IdcServerNT.exe), I add these lines at */server/bin/intradoc.cfg*:
JAVA_OPTIONS_debug_enable=-Xdebug
JAVA_OPTIONS_debug_options=-Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
and since the JAVA_OPTIONS is shared between admin server (IdcAdminNT.exe) and non-admin server (IdcServerNT.exe), to prevent "Address already in use" error, I added same lines but with empty value into */server/admin/bin/intradoc.cfg*:
JAVA_OPTIONS_debug_enable=
JAVA_OPTIONS_debug_options=
or alternatively enable it but use different port for the "address=xxx".
Now the issue is when I had run the non-admin UCM server with remote debugging enabled, then I tried to run the Component Wizard, I got "Address already in use" error:
ERROR: transport error 202: bind failed: Address already in use ["transport.c",L41]
I found out that's possible because Component Wizard (ComponentWizard.exe) is using same setting file with non-admin server (IdcServerNT.exe): */server/bin/intradoc.cfg*. It's obvious that happened because of ComponentWizard.exe is in same location with IdcServerNT.exe, so I think other tools like Batch Loader and System Properties will be affected with same issue too.
Because of this issue, everytime I want to open Component Wizard, I had to stop the non-admin server which is inconvenient.
So, the question is there a way to define separately or disable the JAVA_OPTIONS_debug_enable & JAVA_OPTIONS_debug_options for Component Wizard?

WillT wrote:
My run method was being called somewhere else and I can't find out whereOkay, but changing from implementing Runnable to extending Thread won't change that one whit. You must've also changed something else.
Extending Thread is the wrong approach, since you're not creating a special kind of Thread.

Remote debugging in sun one application server 8.1 options

Hello Techies,
I want to remote debug sun one application server 8.1
I had followed remote debugging documentation on MyEclipse site. My sun one server is running under 8080 port. so I had done the modifications in domain.xml as follows
debug-enabled="true" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8080"When i change this address to 8080, I am unable to start up the server. Can you guys tell me am i missing any thing ??
Why I am unable to start up the server?? If i change the port no to 8000 I am able to start up the server.
regards,
Krishna

And just to make an unfounded guess: do you have to specify the debug port or the request port there? If it's the former, it'll stand in its own way.

Enabling tracing in remote debugging

Similar Messages

Maybe you are looking for