JDeveloper 10.1.3.1 Debug Problem

Now Debug mode while running Junit tests has been running fine for me. Now all of a sudden there is a problem. When in Debug mode, it stops only at break points. When it stops at the break point, I would like to either step over, or into a method, but what happens is it just either goes to the next breakpoint or finishes running the Junit test. What could be the cause of this and how do I go about fixing it?

Thanks for your reply. But the problem is the webpage is not showing up.
Usually the default page will show up once the debugger is started, but now its not doing so.
Any thoughts on this.
Thanks

Similar Messages

  • JApplet debugging problem

    Hi there all:
    I'm having a problem with debugging a JApplet. I created a new workspace, project and applet and didn't make any changes to anything. When I try to debug the applet, I get these messages:
    System Error: java.security.AccessControlException: access denied (java.lang.RuntimePermission modifyThreadGroup )
    System Error: java.lang.Object java.lang.Class.newInstance0()
    System Error: java.lang.Object java.lang.Class.newInstance()
    System Error: java.applet.Applet sun.applet.AppletPanel.createApplet(sun.applet.AppletClassLoader)
    System Error: void sun.applet.AppletPanel.runLoader()
    System Error: void sun.applet.AppletPa
    System Error: nel.run()
    System Error: void java.lang.Thread.run()
    If I change the object from a JApplet class to an Applet class, I can debug just fine.
    Anyone know what's going on here?
    Thanks
    Jeff

    Me again. Was doing some searching on the net about this one since I've gotten no response.
    Found this at Inprise (Borland) about a debugging problem with JBuilder3 (I assume that the base of jdev is still JBuilder).
    http://community.borland.com/article/0,1410,19739,00.html
    To quote from their document--------
    Question:
    I can't seem to debug Applets with JBuilder3 Standard. If I attempt to debug my Applet
    I recieve the following error:
    java.security.AccessControlException: access denied (java.lang.RuntimePermission
    modifyThreadGroup )
    at java.security.AccessControlContext.checkPermission(AccessControlContext.java:195)
    at java.security.AccessController.checkPermission(AccessController.java:403)
    at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
    Why?
    Answer:
    In a nutshell this is an installation problem with JBuilder3 Standard edition.
    The install for JBuilder3 Standard did not provide the file 'DebugApplet.policy'.
    To resolve this problem download the file from the following URL:
    http://www.borland.com/devsupport/jbuilder/downloads/DebugApplet.policy
    After you have downloaded the file, copy the file to your JBuilder3\bin directory.
    This will fix the problem.
    You can also cut and paste the following:
    (NOTE: create the file DebugApplet.policy in your JBuilder3\bin directory)
    //DebugApplet.policy
    // These policy permissions are needed for the AppletViewer used by sun.tools.debug.
    grant {
    permission java.lang.RuntimePermission "accessClassInPackage.*";
    permission java.lang.RuntimePermission "modifyThread";
    permission java.lang.RuntimePermission "modifyThreadGroup";
    permission java.net.SocketPermission "*", "accept, connect, listen, resolve";
    permission java.util.PropertyPermission "appletviewer.version", "read";
    permission java.io.FilePermission "<>", "read";
    permission java.security.AllPermission;
    Could this be a problem in JDev3 too?
    Jeff
    null

  • Debug problem in JDeveloper 3.0

    Has anybody come across a problem when debugging an application that causes JDeveloper to go into an infinite loop (until my machine runs out of memory) when a breakpoint is hit.
    This only seems to happen on certain files
    I've removed JDeveloper 2.0. I've reinstalled JDeveloper 3.0. I've recreated my workspace and project from scratch but I still get the problem.
    My project has ~1200 files.
    I've also noticed that sometimes the breakpoint is hit and the application being debugged will be paused but JDeveloper does not gain control (i.e. the 'step', 'step into' etc. buttons are still disabled). This is possibly related to the above problem.

    Has anybody come across a problem when >debugging an application that causes >JDeveloper to go into an infinite loop >>(until my machine runs out of memory) when a >breakpoint is hit.This is not a known issue but if anyone has a reproducable test case then we'll be happy to follow it up.
    Thanks,
    Arun

  • JDeveloper 3.0 debugging problem

    I switched JDeveloper to use JDK 1.1.7 and I got a message that the debugger does not support that JDK version. Then I switched back to the original preconfigured JDK1.1.8_JDeveloper. This was done by setting the value in field Project/Project properties/Target JDK version. Now I get following error message when starting the debugger: Cannot debug with Target JDK "java version JDK1.1.8_JDeveloper", can only debug with target JDK java version "1.1.7".
    1.1.7 is the name of the JDK that I added to JDeveloper.
    How can I get the debugger back in action? What I would really like to do is to debug with JDK 1.1.7. Is that possible with JDeveloper3.
    I have JDeveloper 3.0 build 532 running on NT 4.0 sp6.
    Please help and thank you for reading my post!

    Question was answered in another thread

  • Plsql debugging problem with jdeveloper

    hi
    i have an oracle server name tiger and a client machine the packages and stored procedure exists on the server machine. but when i try to debug i get the following error
    Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
    Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '0.0.0.0', '1421' )
    ORA-30683: failure establishing connection to debugger
    ORA-12545: Connect failed because target host or object does not exist
    ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
    ORA-06512: at line 1
    Process exited.
    amir

    I don't think JDev is able to debug with other application server. I can't see any server settings except embedded oc4j. you can only debug your application with embedded oc4j which JDev has. but you can create deployment profile for other server such as weblogic, jboss, and tomcat with JDev.
    -correct me if i'm wrong, thanks-

  • JDeveloper v10.1.3.0 - Debugging Mode - Unable to fiind source file

    I just upgraded to a newer (10.1.3.0) version of JDeveloper.
    When I'm stepping through Java code in the debugger and I need to step into code that is in another project, I get a dialog box telling me "Unable to find source file".
    The dialog box has four radio buttons and in the past, I chose the "Look for the file in project: " which had a drop down box where I could select the project that the Java file was in.
    With the new vesion, this does not work. I have to select the second option, which is "Let me find the file myself with the open file dialog".
    This latter method works, but it is much more time consuming than the former. Has anyone else noticed this problem before and found out a way to fix it?
    Thanks in advance for any help on this matter.
    Greg

    Just some more information from me, the original poster...........
    When I try to do the remote debugging....
    Under the project's Run Configuration, Launch Settings, I check the "Remote Debugging and Profiling"
    Under Debugger, Remote, I select the "Listen for JPDA
    Then I select the project and chose "Start Remote Debugger"
    Then I set a breakpoint in the PL/SQL
    Then at the SQLPLUS command line, I enter "exec DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', 4000 );"
    Response from SQLPLUS is:
    BEGIN DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', 4000 ); END;
    ERROR at line 1:
    ORA-12571: TNS:packet writer failure
    ===========================================================
    When I try debugging locally............
    I uncheck "Remote Debugging and Profiling"
    In Run Config, Debug, Remote, I select Attach to OJVM as the protocol
    I then select the PL/SQL function that I would like to debug and select "Debug"
    Here are the results from JDev....
    Connecting to the database QF.
    Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
    Executing PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED
    Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', '3263' )
    ORA-30683: failure establishing connection to debugger
    ORA-12541: TNS:no listener
    ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
    ORA-06512: at line 1
    Process exited.
    Disconnecting from the database QF.
    =========================================================
    Any help would sure be appreciated.
    Thanks,
    Greg

  • JDev Debugging problem

    Dear sirs,
    I would like to be able to debug my JDeveloper project and trace into the J2SE source files, but JDeveloper will not let me.
    The project JVM is currently set to "Java 1.3.1"
    with the path : "E:\java\jdk1.3.1\jre\bin\java.exe"
    and with the classpath:
    E:\java\jdk1.3.1\lib\dt.jar;E:\java\jdk1.3.1\jre\lib\rt.jar;E:\java\jdk1.3.1\jre\lib\i18n.jar
    I have tried to set the path to
    "E:\java\jdk1.3.1\bin\java.exe" instead, but JDeveloper switches the path back to "E:\java\jdk1.3.1\jre\bin\java.exe" for no apparent reason.
    I have tried to uncompress the src.jar and set the
    source path: E:\java\jdk1.3.1\src\ but to no avail.
    I have tried to set the classpath to
    E:\java\jdk1.3.1\lib\dt.jar;
    E:\java\jdk1.3.1\src.jar;
    E:\java\jdk1.3.1\jre\lib\i18n.jar;
    E:\java\jdk1.3.1\jre\lib\rt.jar
    to try and force it to use the source files instead of the runtime files, but then I get a System Error when trying to run my compiled project and execution is halted :
    System Error:     java version "1.3.1"
    System Error:     Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
    System Error:     Java HotSpot(TM) Client VM (build 1.3.1-b24, interpreted mode)
    System Error:     
    Please help me, as I am running out of ideas on how to trace into the Java source code.
    Best regards,
    Christian Loft
    "E:\java\jdk1.3.1\jre\bin\java" -mx50m -showversion -classpath "E:\Program Files\Oracle\JDeveloper 3.2\myprojects\RMI2\myclasses;E:\Program Files\Oracle\JDeveloper 3.2\jdbc\lib\oracle8.1.7\classes12.zip;E:\Program Files\Oracle\JDeveloper 3.2\lib\connectionmanager.zip;E:\Program Files\Oracle\JDeveloper 3.2\lib\jdev-rt.zip;E:\java\jdk1.3.1\lib\dt.jar;E:\java\jdk1.3.1\src.jar;E:\java\jdk1.3.1\jre\lib\i18n.jar;E:\java\jdk1.3.1\jre\lib\rt.jar" -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=2103 RMI_Client_Application

    Dear Christophe,
    thank you for your reply. I have included the src.jar in the source path. But there is no "tracing classes and packages to Exclude" under the "Run/Debug" tab (I use JDeveloper 3.2.2 (Build 915)), but under the "Compiler" tab I have made sure that there is no files mentioned in the "Exlude class" and the "Exclude Sources".
    The problem remains. I can run the application, but when I try to debug, the application window never appears.
    Do you have any other things I can try?
    Best regards,
    Christian
    You need to make sure sure of a couple of things:
    - have src.jar added to your java source path (Project settings Input path)
    - also you need to go into the debugger pane of project Settings and remove from "tracing classes and packages to Exclude" all the classes you want to trace into. For example if you want to trace into java.lang.String remove the java package.
    Hope it helps, Christophe [JDeveloper team]

  • Upgrading JDeveloper 9052 to 1012 and centrino problems?

    I have recently purchased a new laptop with the following specification:
    Dell 9300
    Centrino 1.8
    1Gb DDR2
    ATI x300 128Mb
    60Gb Hard Drive
    Windows XP SP2 + all updates
    to replace my previous development machine.
    I have experienced the following problems when running JDeveloper on it and I'd appreciate your assistance in rectifying them.
    1. I installed JDeveloper 9052 on my laptop and tried to run an ADF based application that I have got running on many other development machines and a 904 server. When I ran the application on my laptop it worked fine until it reached the point within the application that created an inputStream from a URL - where it failed. I know that it fails exactly at this point after spending some time debugging the code. I found this very strange as I could successfully view the content of the URL in a web browser.
    2. In an attempt to find a solution to point 1. (see above) I installed version 1012 of JDeveloper. I tried to open the existing project that I had created in 9052 and when prompted agreed to convert it to the new format. Then without opening or editing any of the files I successfully ran the applicaiton by right clicking on the view controller within the project (applicaiton navigator panel) and selecting run from the context menu. The application ran successfully without any problems at this stage.
    HOWEVER, I then opened up the struts-config pageflow diagram and tried running it from there, the project failed.
    After studying the struts-config file both before and after I had opened it within 1012 I found the following discrepancy:
    BEFORE: - - - - -
    <action path="/getParams" className="oracle.adf.controller.struts.actions.DataActionMapping" type="view.GetParamsAction" name="DataForm">
    AFTER: - - - - -
    <action path="/getParams" className="oracle.adf.controller.struts.actions.DataActionMapping" type="view.GetParamsAction" name="DataForm" parameter="unknown">
    After manually removing this line of code I was able to get the application to run again. However every time I edit/view the struts config file or indeed save changes and reboot JDeveloper the parameter="unknown" line is added again and prevents the project from running.
    3. After further investigative work following point 2. I came across what I believe to be a further bug.
    When I reopened JDeveloper I noticed that the struts-config pageflow diagram had changed. A dataAction had been replaced by a dataPage as well as the extra line of code being added as described in point 2. The pageflow diagram should be dataPage --> dataAction --> dataPage but now it was dataPage --> dataPage --> dataPage.
    After further investigation I found a descrepancy in the following file before and after I had opened it in 1012. The nominalHeaderXml4\ViewController\model\StrutsPageFlow.oxd_struts file changed from this ....
    <shape name="/getParams">
    <elemRef name="" value="3d2b2d0e-0104-1000-8008-c222e564ea8e::/getParams::StrutsDataAction" type="StrutsDataAction" class="o:b:CID"/>
    </shape>
    to this when I had opened it 1012.
    <shape name="/getParams">
    <elemRef name="" value="51d65a60-0104-1000-8003-c222e56470a8::/getParams::StrutsDataForwardAction" type="StrutsDataForwardAction" class="o:b:CID"/>
    </shape>
    I have speant the last 2 days looking into these problems. I have found that both points 2 and 3 happen consistantly when opening 9052 projects in the 1012 environment. And have elimated the following things when trying to get JDeveloper 9052 to work correctly, firewalls, antivirus, windows updates, and software conflicts. The only difference that I can identify is that my new machine uses a centrino chip and my old one used a P4.
    I hope that someone will be able to shed some light on these problems for me as soon as possible. Thanks in advance for your help.
    David
    David Ferguson

    The struts-related observation is noted in the JDeveloper 10.1.2 Release Note Addendum:
    http://www.oracle.com/technology/products/jdev/htdocs/10.1.2.0.0/readme_10.1.2.0.0_addendum.html#jan1
    For the 1st issue, I'd recommend opening a TAR with metalink so our worldwide support engineers can help diagnose the problem. I've not heard of any Centrino specific issues to date.

  • Sun Studio Debugging problem

    Hello
    I need help configuring the Sun studio debugger to work in fedora 8. The project is loaded from a make file, compiles fine, and runs fine. However, I can not place break points, and when I start the visual debugger, it gives a message box titled progress, and hangs on saying: starting debugger: /lib/libc.so.6
    Running from the command line gives me:
    $dbx <my program>
    For information about new features see `help changes'
    To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc
    Reading <my program>
    Reading ld-linux.so.2
    Reading libm.so.6
    Reading libmpich.so.1.1
    Reading libpthread.so.0
    Reading librt.so.1
    Reading libc.so.6
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
    I have another problem in debugging an mpi problem in another installation of Sun Studio on Solaris 10 on a Sun machine. The visual debugger is working fine there, however, I need to debug with mpirun
    to decide the number of processors, because by default it loads the application on one processor. Iwill need to do this as well later on the linux machine I am using now, which doesn't even start the debugger on a sequential code so far.
    I appreciate your help a lot.
    Thank you very much in advance.
    Manal

    mhelal wrote:
    Hi
    Thank you for your reply. you said 2 problems,Yes, basically I meant these two:
    1. dbx: warning: unknown location expression code (0xe0)
    2. dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
    First one should be fixed in dbx itself, but the second looks like an incompatibility between Fedora's libc and dbx; unless distros in "supported" list upgrade to the same version of libc, dbx can't be changed to match it.
    In other words, I'm sorry to say that you will probably not succeed in using dbx on Fedora 8 for the time being.

  • Debug problem using JDK 1.2.2

    Hello,
    I set up remote debugging in J-Dev 3.1.1.2 and was using it successfully for several days.
    I then did some local debugging on a servlet that was compiled using 1.1.8 JDK. Now none of my servlets that are compiled under 1.2.2 can be debugged either locally or remotely. I get a message telling me that the class cannot be debugged.
    Can anyone offer suggestions on what could be wrong?
    Thanks

    I had this problem earlier today. I deleted the old workspace, created a new one, added my projects in again, recompiled and things were fine. Every now and then my workspaces seem to corrupt and I have to do this, although I don't always get the "can't debug class message"
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Bill:
    Hello,
    I set up remote debugging in J-Dev 3.1.1.2 and was using it successfully for several days.
    I then did some local debugging on a servlet that was compiled using 1.1.8 JDK. Now none of my servlets that are compiled under 1.2.2 can be debugged either locally or remotely. I get a message telling me that the class cannot be debugged.
    Can anyone offer suggestions on what could be wrong?
    Thanks <HR></BLOCKQUOTE>
    null

  • Migration from Jdeveloper 11g r1 to 11g r2 problem

    Hi all
    I have a project initially created in Jdeveloper 11g r1
    after migrating it to Jdeveloper 11g r2 i tried to replace lookup ejb invocation to dependency injection.
    So i used @EJB annotation in my managed bean. I'm shure there could be no mistakes in the way how i used this anno, i did it many times
    it looks something like this
    @EJB(name="StatelessSessionEJBEx",beanInterface =StatelessSessionEJBEx.class, beanName = "StatelessSessionEJBEx")
    as a result it generated an exception which said that the EJB interface could not be found, though all dependencies between business and view projects are in place. After a while i figured out that the problem is it used JSF 1.2 specification instead of 2.0 so i replaced the version of JSF in managed been source code
    <?xml version="1.0" encoding="windows-1251"?>
    <faces-config version="2.0" xmlns="http://java.sun.com/xml/ns/javaee"> ....
    but it seemed to make no effect at all.
    So are there any guesses what i did wrong
    Thanks. Alex.

    Hi,
    the server used by JDeveloper 11g R2 is a patched WLS 10.3.5 or 10.1.3.6 server (depends on teh JDeveloper version), which is not a Java EE 6 version but Java EE 5 (which explains why CDI doesn't work as expected). To read up on how to get annotated EJBs work from JSF managed beans, see http://buttso.blogspot.de/2011/03/jsf-with-managed-beans-and-dependency.html.
    The upcoming 12c release will solve all of this. My suggestion therefore is to keep on going with the web.xml reference and then replace it later with @EJB annotation references
    Frank

  • Java debugging - problems with standard input

    Hi
    I hope somebody can help me with this problem.
    I'm developing a Java app that reads from the standard input. I use System.in.read() to do that. When I debug it, I use the Standard I/O window instead of the Run Log window to pass in values, but nothing happens (i.e. the line following the read() is never reached). I also tried to run the app and then attach the debugger to use the Run Log window as standard input, with the same result. If I add a breakpoint before the call to read(), the debugger pauses the execution, so I suppose the breakpoints are OK.
    In the executable Info window, Debugging tab, I use the pseudo terminal with the Java debugger.
    So my question is: how can I enter values from the standard input in debugging mode?

    I believe that you are seeing these problems because we have found the
    current versions of RMI found in the JDK to be inherently unscalable -- we
    do not listen for them. As you noticed, we recommend that you use our
    packages for now, and then do the simple change that you found if you decide
    that you do not like WLS. (If you do decide that you do not like us, please
    definitely let us know why you chose the way you did!)
    Thanks,
    Michael
    Michael Girdley
    Product Manager, WebLogic Server & Express
    BEA Systems Inc
    "Tim Dawson" <[email protected]> wrote in message
    news:397b8cc2$[email protected]..
    We're developing a J2EE application on NT using WLS 5.1, SP3, but we don't
    want to be tied to any particular J2EE server, so we're making sure that
    none of our code is weblogic specific.
    In keeping with this philosophy, I created an RMI service that used the
    standard java.rmi.* imports instead of weblogic.rmi.* and used thestandard
    RMIC compiler rather than the weblogic.rmic compiler.
    Unfortunately, I couldn't get the system to work. I kept getting
    "java.rmi.MarshalException: Error marshaling transport header; nested
    exception is: java.io.EOFException" whenever I'd call Naming.lookup().
    Of course, when I did the search & replace with java.rmi.* with
    weblogic.rmi.*, and switched from the standard rmic to weblogic.rmic,
    everything started working just fine. This is the ONLY change I made!
    Has anyone else run into similar problems?
    Tim Dawson
    Sr. Software Architect
    is.com

  • Debugging problem, in inbound function module.

    Hi Experts,
                  R/3 system is receiving data through an IDOC called WPUUMS[sales data]. It has been seen that when this data is posted in R/3 through XI the data gets reflected in WE02 / WE05, and is similar to when a manual entry is done the transaction WPUK. But the difference is , when manual idoc generation is done, it is updating correct data in database, but when same data is posted from XI, it is updating data base with in correct data!
       what I cant get to understand is in both the cases, IDOC is posted, and same data is there in the DATA records, but database is getting upated with diff data.
        Also , when I am putting a break point on the inbound function module IDOC_INPUT_POS_SALES_ACCOUNT, it is not hitting the break-point but idoc gets generated successfully with status records like
    53 Application Document posted
    62 Idoc Passed to application
    64 Idoc ready to be transferred to application
    50 Idoc added.
    Also , i want to know, wether these messeges come step by step or randomly, because, why is the messege 62, before messege 64.
    Lastly when I am taking the same IDOC and trying the same in WE19, then it hits the break-point function module IDOC_INPUT_POS_SALES_ACCOUNT successfully.
    Experts, comments pls.!
    Regards,
    Arnab.

    Hi,
    You are supposed to read the ststus messages from bottom to top. So the actual sequence is:
    50 Idoc added.
    64 Idoc ready to be transferred to application
    62 Idoc Passed to application
    53 Application Document posted
    Which is correct.
    And it is correct that the system bypasses any breakpoint in the background mode. So when the IDoc is coming from XI the posting FM IDOC_INPUT_POS_SALES_ACCOUNT is called in background and so the breakpoint is not called.
    Only way to debug the problem is via transaction WE19 in Debug mode.
    Regards,
    Prakash Pandey

  • Debugging problems on iPad

    I have two applications, and 4.7 installed in two different PCs (64 bits one and 32 bits the other one).
    In one PC (32 bits) both apps can be tested with no problem at all. In the other one (64 bits) I debugged one of them once, but now I can't debug any of them.
    Problem description: device is there and connected, debug begins, says it's installing and seems to finish it well. It waits for me to initiate the app, but the app is not there. No app for debugging in the iPad.

    Hi,
    A similar issue has been logged and is being tracked. Please refer to below bug for more description.
    http://bugs.adobe.com/jira/browse/FB-33478
    Workaround: Even though ipa is not installed on the device, ipa will be generated in the specified output folder(bin-debug).Using iTunes install the ipa on the device and launch the app to make a debugger session.
    Let me know if you require more information.
    Thanks,
    Sanjay

  • Debug problem

    I installed the sneak preview Enterprise portal on my machine. Yesterday i was able to debug my portal application. But today i wasn't. This problem was after the moment I deleted the old portal application.
    Can someone tell my how i can fix this problem
    Message was edited by: Edward Kust

    It could be that your IP address has changed?! In this case, the Developer Studio/Eclipse might not be able to find the portal anymore. I had the same problem, and the strange thing about it is that IE still connects to the portal.

Maybe you are looking for