Skip to Content
author's profile photo Former Member
Former Member

How to (can I?) debug EJB called from ABAP?

I have developed a small bean that I am calling remotely from ABAP. I have done the development work in the WebAS 6.40 Sneak Preview NetWeaver Dev. Studio. I cannot figure how (or even if it's possible) to debug this bean.

I have followed the instructions on debugging referred to elsewhere in this forum, but I'm hung up at the point where I'm to create a debug configuration. E.g., what kind of configuration should I specify? (EJB is not one of the choices.) If I try any of those that <i>are </i> available, I always get to a point where it says that it can't connect to the JVM. Well, that's not what I'm trying to do, is it?

Has anybody successfully done such debugging? If so, can you get me past this sticking point?


Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Aug 28, 2004 at 10:57 PM

    Hi David,

    prerequisite to use debugging is, that the server you want to connect to runs in debug mode:

    Open "Window->Show View->Other->J2EE->J2EE Engine". The configurated J2EE engine is displayed. Use the context menu of the "server0" entry to "Enable debugging of process". The server restarts then. If it's (already) running in Debug Mode, this is visible on the right side "Debug Mode = ON".

    I suggest to define a "Remote Java Application" configuration like this:

    Name: Whatever you like

    Project: The project containing the classes to debug.

    Connection Type: Standard

    Host: Hostname or IP of J2EE server host

    Port: 50021

    Choose "Apply" and "Debug".

    Set breakpoints for example by double-clicking on the frame on the left side of the Java editor (or using the context menu -> Add Breakpoint there). There's a very good documentation about debugger usage in the NWDS online help.

    Trigger the remote call from the ABAP system. As soon as a line with a breakpoint is hit, the debugger displays the line and stops the active thread.

    Hope that helps.



    PS: As soon as you don't need debugging any longer, disable debug mode of the engine, since it slows down everything.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks so much, Stefan - your answer was spot on.

      For others who may be experiencing difficulty similar to mine, my problem was in the specification of the port. I had been taking the default (I think it was '80000'), and once I changed it to '50021', I was able to get into debug just fine.

  • author's profile photo Former Member
    Former Member
    Posted on Dec 16, 2004 at 10:11 PM

    I have a similar problem, but when I try to enable debug from SAP DS as described above, the option is greyed out.

    Anyone know how I can fix this?

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.