cancel
Showing results for 
Search instead for 
Did you mean: 

Still have the problem to debug my BSPs

Former Member
0 Kudos

Hello guys,

First, what I need:

Place a breakpoint somewhere in the eventhandler (for example inputprocessing), start debugging, the debug mode opens (like known from ABAP programming) maybe in a separate mode, jumps directly to my breakpoint (not in endless lon Sap programs), so that I can check for example a parameter.

Second, what is NOT the problem:

- ICM is running

- HTTP debugging is activated for my user

- I don't use a default user for my BSP service (TA SICM)

Third, my environment:

SAP Web AS 6.20

on Win2K Server with MSSQL2000

Patch Level - (ServiceRelease 1) - SAP_Basis 620 Patch 20, SAP_ABA 620 Patch 17, SAP_APPL 470 Patch 6, the Rest does not matter I think...

Fourth, how it behaves when I now start debugging:

He jumps in my session (where the web application builder is open) in the debug mode, he does not open a second session. In debug mode he jumps somewhere in the SAP BSP environment (SAPL...), it does not matter where I put my breakpoints. When I go on with F5 or F6, he takes a long trip through SAP programs, methods, and so on. At the end he opens my BSP in Internet Explorer, without ever shown a part of my program code in the debugger. In the session the debug mode is finished and I'm back in Web application builder. Sometimes my session were shutdown hard and I have to login again to my SAP system.

Regards,

Heiko

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member181879
Active Contributor
0 Kudos

Heiko,

Reading all your points through, I am not sure that we are using the same basis to find the problem and solutions.

One request, please just check the <a href="http://help.sap.com/saphelp_nw04/helpdata/en/17/00ab3b72d5df3be10000000a11402f/frameset.htm">documentation</a> on this topic.

Also, at some stage there was problems with debugging in 620. I would seriously recommend the latest kernel and service packs. (Just to ensure we are not looking at old problems.)

Also, once the BSP application is running, new breakpoints are not considered always.

Please close all browser windows. Then take a simple BSP application, for example IT00/basic_abap.htm, set a breakpoint in the middel of the page. Ensure that at the bottom of the screen you see a message that a breakpoint has been set <b>for your user and you client</b>! Then press F8 to test.

++bcm

Former Member
0 Kudos

Thanks Brian,

I think we fixed the debugging. It's running now without

problems since yesterday afternoon. We tried out so much things, so that I can't say exactly what has fixed the problem.

Best regards,

Heiko

Former Member
0 Kudos

Heiko,

Which patch levels are you running and what debug level "rfc/ext_debugging"

just curious...