Should I tick remote debugging in ff v.27.0?

I am using ff for android v.27.0 and have been getting quite a few freezes. Am I supposed to tick remote debugging? I don't even know what it does.

Nope, but for the freezes we are happy to further investigate.
*Are there specific websites that this happens for?
Many site issues can be caused by corrupt cookies or cache. In order to try to fix these problems, the first step is to clear both cookies and the cache.
The Firefox cache temporarily stores images, scripts, and other parts of websites while you are browsing. <br>
Note: ''This will temporarily log you out of all sites you're logged in to.''
To clear cache and cookies, do the following:
#Tap the menu icon located at the top right corner. This is the icon with 3 bars. On older Android devices you'll have to press the hardware menu key and then tap More.
#Tap '''Settings'''.
#After that, you will be taken to the settings screen. In the settings screen, look under the section '''''Privacy & Security''''' and select '''Clear private data'''.
#You will then be taken to a list of what can be cleared. Select the following 2 for deletion:
#*Cookies & active logins
#*Cache
#After those have been selected, tap the '''Clear data''' button to actually clear the cache and cookies.
Did this help you with your problems? Please let us know!

Similar Messages

Remote Debug in oas 4.0.8.2 using JDeveloper3.1

Now I can do remote debug using JDeveloper3.1 in Tomcat or WebLogic!
But I can not do remote debug in Oralce Application Server 4.0.8.2.
Who knows how to remote debug in OAS, mainly for how to configure OAS to support remote debug, please tell me as quickly as possible!
I appreciate ... very much!!!!!!
We are using JDeveloper3.1 and OAS for our business application. So we must know how to remote debug in OAS with JDeveloper3.1.

In the JAva Environment settings for your OAS Application you should add the remote debugging name-value pairs using
X_OPTION
X_OPTION
runjdwp:transport=dt_socket,server=y,suspend=n,address=4000
X_OPTION debug
X_OPTION noagent
JAVA_COMPILER NONE
INITIAL_HEAP 32m
MAX_HEAP 32m
After adding the configuration start the OAS and try to connect to remote OAS VM for JDeveloper
raghu

Remote debug in jdev3.1 and ias1.0

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

In the JAva Environment settings for your OAS Application you should add the remote debugging name-value pairs using
X_OPTION
X_OPTION
runjdwp:transport=dt_socket,server=y,suspend=n,address=4000
X_OPTION debug
X_OPTION noagent
JAVA_COMPILER NONE
INITIAL_HEAP 32m
MAX_HEAP 32m
After adding the configuration start the OAS and try to connect to remote OAS VM for JDeveloper
raghu

Remote debugging on WAS 6.20

Hi,
we are running the developer studio for our ISA development on WAS 6.20.
Unfortunately the remote debugging doesn't seem to work, at least not as easilly as hoped. Hopefully this is because of lack of information rather than a non-working product. Hence below are the steps and associated questions:
I Go to Window --> preferences. Select SAP J2EE Engine.
The "...is installed on local host" option, when pressing Browse, only gives an error saying that "No local engine could be found!" and then a few sentences indicating that this would only work on unix using a standard path. This of course does not help for local Windows development.
The second option is to select the "...installed on remote host". This would be fine, but as far as I understand I don't have a messaging server if I am running the WAS 6.20 locally.
Question: If I can use this option for the locally running WAS then what should I put it in the message server host and port?
When this fails the alternative is to go to the server root, open up the \configtool\configtool.bat and tick the debug mode for the server on and set the port to for example 9999.
After this I switch to debug mode in the studio and select Run --> debug... from this screen double click on remote java application and fill in the connection properties with localhost and 9999.
Unfortunately this also ends up in "failed to connect to remote VM".
Are we going down the wrong path here or just missing something in this? I didn't expect it to be very difficult to set the remote debugging in place.
Thanks for any comments!
Cheers,
Kalle

Thank you for getting this sorted.
Just for sake of re-assurance to others who are trying this. It will work, but there are a few things to be aware of.
1. When I did the http://localhost:port/@@@DEBUG@@@
the debugsession screen had an empty port.
I fixed this by using the configtool and setting the port there.
Next time it then worked.
If you use the developer studio the only things you need to do to start the debugging is to select the debug icon --> Debug... and in there create a new remote application.
In the remote application set the server name and port (for me it was localhost and I defined in the deploytool the port to be 12800).
After that hit debug and you can see that you are connected to the server. If you are not then restart the server and try again.
After you have the server running and you try to run, from the IDE a JSP you will get an error, but when you access the application through the browser your IDE will pick that up and off you go!
The rest should now be standard debugging...

How to enable remote debugging for a session other than the current one

Hi all,
I am trying to figure out how to enable remote debugging for a session other than the one I am currently using.
More specifically, we have an application that is making database calls to Oracle 11gR2. Something is causing an exception during this invocation. My system is currently not set up to recompile said application, so I can't just add the debug call to the code and recompile. Therefore I would like to be able to log into the database (as sys, if necessary) and invoke dbms_debug_jdwp.connect_tcp on the desired session.
The docs indicate that I should be able to do so:
dbms_debug_jdwp.connect_tcp(
host IN VARCHAR2,
port IN VARCHAR2,
session_id IN PLS_INTEGER := NULL,
session_serial IN PLS_INTEGER := NULL,
debug_role IN VARCHAR2 := NULL,
debug_role_pwd IN VARCHAR2 := NULL,
option_flags IN PLS_INTEGER := 0,
extensions_cmd_set IN PLS_INTEGER := 128);
But when I try (even as sys), I get the following:
exec dbms_debug_jdwp.connect_tcp('1.2.3.4',5678,<session id>,<session serial>);ORA-00022: invalid session ID; access denied
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
00022. 00000 - "invalid session ID; access denied"
*Cause: Either the session specified does not exist or the caller
does not have the privilege to access it.
*Action: Specify a valid session ID that you have privilege to access,
that is either you own it or you have the CHANGE_USER privilege.
I've tried granting the 'BECOME USER' privilege for the relevant users, but that didn't help. I read something about having to set some kind of ACL as of 11gR1, but the reference documentation was very confusing.
Would someone be able to point me in the right direction? Is this even possible, or did I misread the documentation?

Interesting deduction, that would be very useful indeed. I hate recompiling just to add the debug call, and it can't be done in our production environment. But it seems unlikely to me it would be implemented this way.
I would cross-post this in the SQL AND PL/SQL forum though, as this is really a database issue, not with the SQL Developer tool. Do add the links to the other posts in each.
Regards,
K.

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

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

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

Cannot remote debug from JDev 10.1.3 on AS 10.1.2 running hotspot

Hi,
I've set up an embedded OC4J instance in an application server as described in the help topic, "Remote Debugging in OC4J" (with a few changes, such as the fact that I added startup options using the OC4J instance Admin page of EM, rather than at the command line (since the instance is embedded in a full AS). I followed the directions specifically for HotSpot, because that's the JVM the instance was set up to use, and I can't change it (I know OJVM enables lots more features, but that's the situation I'm in).
I've also configured my project for remote debugging, ensuring the host name and port matches, and trying both "Attach to JDPA" and "Attach to OJVM" (these being the only two options, except for starting a listener, which I don't think will help with a web application).
When I try to debug, though, I get:
Debugger unable to connect to remote process.
Should I be doing something differently?
Thanks much,
Avrom

I had the delete key quit working after accidentally pressing a key sequent that included the delete key. I don't know what keys were involved, but the delete key from that point on did nothing.
I am running JDeveloper 10.1.3.0.4 on Window XP.
To resolve the problem, I set the keyboard Accelerators back to 'Default' in JDeveloper.
I selected... Tools->Preferences->Accelerators
then click on 'Load preset' then I chose 'Default'
You may need to select something other than default for your platform, but that did the trick for me.

How to start listener in sql developer for remote debug

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

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

Remote Debug in eclipse

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

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

Remote Debugging (Jdev 10.1.3 to AS 10.1.3)

Hi,
I have been trying to do a remote debugging by connecting Jdeveloper (version 10.1.3 production) to AS 10.1.3 mid-tier but the OC4J instance seems to be crashing the moment the jdeveloper makes the connection. However, before the crash, jdeveloper takes about 5minutes to connect to the server.
The OC4J is managed by opmn and not a standalone process. I am not sure if this makes any difference. Here are the changes that I made in the 10.1.3 server:
*) Modified opmn.xml to add the below:
<data id="java-options" value="-server -verbose:gc -Xmx512M -Xms128M -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=43503 -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:ParallelGCThreads=2 -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
(also tried removing "-server" option)
*) Modified orion-web.xml to add the below:
<init-param>
<param-name>debug_mode</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>developer_mode</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>encode_to_java</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>emit_debuginfo</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>jspjavacompiler</param-name>
<param-value>oracle.jdevimpl.jsp.JspOjcCompiler</param-value>
</init-param>
*) Modified global-web-application.xml to add the below:
<orion-web-app
jsp-cache-directory="./persistence"
servlet-webdir="/servlet"
development="true" >
I see the below message in the jdeveloper debug window when the OC4J instance crashes:
Debuggee process virtual machine is Java HotSpot(TM) Server VM.
Debuggee process is application server OC4J.
To test JSPs or servlets, you must start a browser.
Debugger disconnected from remote process.
I do not see any error in application.log file.
By setting up the remote debugging, I am hoping for a better portlet development experience.
Any help is appreciated.
Thanks,
Pandian.
Message was edited by:
apandian

The doc is kind of vague, but here's the root reference:
http://download.oracle.com/docs/cd/B25221_04/core.1013/b15976/opmnxml.htm#sthref144
There's a FAQ document that prescribes how the "restart" algorithm works, see 1.3:
http://www.oracle.com/technology/products/ias/ohs/htdocs/opmn-1013-faq.pdf
So to tweak this behaviour, you specify a speciifc <ping> element inside of the opmn.xml for the managed process you are using -- and set the timeout, interval, retry attributes to some combination that gives you a longer pause time.
http://download.oracle.com/docs/cd/B25221_04/core.1013/b15976/common.htm#CACGAIGH
         <ias-component id="default_group">
            <process-type id="home" module-id="OC4J" status="enabled">
               <module-data>
                  <category id="start-parameters">
                     <data id="java-options" value="-Xrs -server -XX:MaxPermSize=128M -ms512M -mx1024M -XX:AppendRatio=3 -Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
                  </category>
                  <category id="stop-parameters">
                     <data id="java-options" value="-Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
                  </category>
               </module-data>
               <start timeout="600" retry="2"/>
               <stop timeout="120"/>
               <restart timeout="720" retry="2"/>
               <ping timeout="300" />
               <port id="default-web-site" range="8888" protocol="ajp"/>
               <port id="rmi" range="12401-12500"/>
               <port id="rmis" range="12701-12800"/>
               <port id="jms" range="12601-12700"/>
               <process-set id="default_group" numprocs="1"/>
            </process-type>
         </ias-component>Now I did just see something that is either a bug, or a doc error. In the doc, it shows the attributes of the <ping> tag to be: timeout, retry, interval. However when you configure opmn.xml with these, it report an error.
Looking at the $ORACLE_HOME/opmn/conf/opmn.xsd file, it shows that only attributes are timeout and interval. You can't add a retry attribute. I'm not sure if this is a doc bug or an error in the XSD file.
Anyways, using the timeout parameter, for your DEBUGGING phase (not production!) you should be able to bump that up to a higher value to allow OPMN to wait longer for a response from OC4J before it nukes it.
-steve-

How to use Remote Debugging in JDeveloper 3.1 ?

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

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

What's the purpose of SQL Developer's remote debug?

AS per SQL Developer's "Remote debuggin", the user guide says "To debug a function or procedure 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."
I'm confused what's the prupose to do a remote debugging? Could you please give me a
scenario to help me clarify this term?
Thank you!
Jeff

Mmm, don't know if the database should really be on another host, but anyway it would be a characteristic, not a definition.
Remote debugging differs from normal debugging in the origin of the debugged session:
For normal debugging, you start a new session from within sqldev (local) and hook into the debugger (pretty easy and automated). For remote debugging, you hook whatever existing session (started from whatever program) on whatever host (remote) into the debugger (a bit more manual as you have to include the call to hook into the debugger yourself). Very useful for debugging remote sessions over a database link or a particular remote user situation which cannot be reproduced locally.
Have fun,
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

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

Should I tick remote debugging in ff v.27.0?

Similar Messages

Maybe you are looking for