Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

ADT 3.8.2 Debugger not triggering

matt
Active Contributor

ABAP Business Object Tools (Developer Edition)1.99.1

SAP ABAP Connectivity And Integration Development Tools (Developer Edition)1.115.1

ABAP Core Development Tools (Developer Edition)3.8.3

ABAP Development Tools for SAP HANA (Developer Edition)3.8.2

ABAP Development Tools for Web Dynpro (Developer Edition)1.115.1

BW Modeling Tools Integration with SAP HANA Studio (Developer Edition)

BW Modeling Workbench (Developer Edition)

BW Query Designer (Developer Edition)

Eclipse: Version: 2019-12 (4.14.0) Build id: 2019 1212-1212

Backend: SAP_ABA 750 0013 SAPK-75013INSAPABA Cross-Application Component

Everything up to date (at time of writing).

See mike.pokraka's question here: https://answers.sap.com/questions/12688037/did-the-latest-adt-324-break-the-eclipse-debugger.html (Also pinging armin.beil.2 )

I'm in the same state as Mike was: debugger has stopped working in most cases. I'm setting break points in ABAP Unit test methods. The only way they trigger, is if open a SAPGui session in eclipse, and run the unit tests from there - then I get into the Eclipse debug perspective. Otherwise, even BREAK... is ignored.

And I have the same issue as Mike regarding opening incidents.

1 ACCEPTED SOLUTION

Armin_Beil
Advisor
Advisor

Hi Matthew,

sorry for the inconvenience. According to your description and also for other reasons, I currently assume that the root cause of your issue actually differs from the one that Mike had.

I was not able to reproduce your problem with Eclipse 2019-12, ADT 3.8.3 & ABAP Backend 7.50 SP 16 (You use SP13, but it's very unlikely that this makes the relevant difference). Debugging a unit test started from ADT works fine for me in this setup.

Your hint that the same unit test actually brings up the ADT debugger when started from embedded GUI, is already quite valuable. But I need to ask some more questions to narrow it down:

1) Is the issue occuring only during execution of ABAP unit from ADT or also in other scenarios?
2) Is it occuring only for certain unit tests or for each and every unit test?
3) Is it occuring only for your user or also for other users in that system?
4) Is it occuring only in one certain backend system or also in different backends?
5) After the issue occurred once: Do you have 100% reproducible failures when re-executing the unit test or does the debugger also work sporadically for your unit test?
6) Please right click on a breakpoint and choose "Refresh Breakpoint Activation". Retry running the unit test and let me know whether that changed anything.
7) Do you have the debug view (not debug perspective) opened and visible when triggering the unit test?
😎 Is anything written to the view "Error log" when you execute that unit test from ADT?

Without ticket / remote access it's more difficult for me to provide support, so we will probably need a couple of questions and iterations. We can also do this via mail if you prefer.

Best regards,
Armin

Edit: Could you please also check the profile parameter "rfc/ext_debugging" via transaction RZ11. The value should be 3, not 0. For more details on the values see https://launchpad.support.sap.com/#/notes/668256

11 REPLIES 11

FredericGirod
Active Contributor
0 Kudos

Is there an option to set debbuging for other user-id like in SAPGui ? maybe could be something like that

Armin_Beil
Advisor
Advisor

Hi Matthew,

sorry for the inconvenience. According to your description and also for other reasons, I currently assume that the root cause of your issue actually differs from the one that Mike had.

I was not able to reproduce your problem with Eclipse 2019-12, ADT 3.8.3 & ABAP Backend 7.50 SP 16 (You use SP13, but it's very unlikely that this makes the relevant difference). Debugging a unit test started from ADT works fine for me in this setup.

Your hint that the same unit test actually brings up the ADT debugger when started from embedded GUI, is already quite valuable. But I need to ask some more questions to narrow it down:

1) Is the issue occuring only during execution of ABAP unit from ADT or also in other scenarios?
2) Is it occuring only for certain unit tests or for each and every unit test?
3) Is it occuring only for your user or also for other users in that system?
4) Is it occuring only in one certain backend system or also in different backends?
5) After the issue occurred once: Do you have 100% reproducible failures when re-executing the unit test or does the debugger also work sporadically for your unit test?
6) Please right click on a breakpoint and choose "Refresh Breakpoint Activation". Retry running the unit test and let me know whether that changed anything.
7) Do you have the debug view (not debug perspective) opened and visible when triggering the unit test?
😎 Is anything written to the view "Error log" when you execute that unit test from ADT?

Without ticket / remote access it's more difficult for me to provide support, so we will probably need a couple of questions and iterations. We can also do this via mail if you prefer.

Best regards,
Armin

Edit: Could you please also check the profile parameter "rfc/ext_debugging" via transaction RZ11. The value should be 3, not 0. For more details on the values see https://launchpad.support.sap.com/#/notes/668256

matt
Active Contributor
0 Kudos

Thanks Armin for getting back so quickly. I can answer some questions now:

2) Every one

5) 100% reproducible

6) Done that - nothing changed

7) It behaves the same whether the debugger view is open or not

I won't be working with the particular client until probably next Tuesday, so I'll look get back to you about that. Tomorrow, I'll be using the same Eclipse version etc (different installation) at a different client. I'll check there as well.

matt
Active Contributor
0 Kudos

Value of rfc/ext_debugging is 1 in one backend, and 0 in another!

I guess that's probably it - but just in case:

1) I loaded a report program, set a breakpoint and ran it. The perspective changed to debug and the program stopped in debug mode as expected.

2) I tested with another report program I have with unit tests. The unit test run did not stop. (It does stop at a breakpoint when I execute it normally).

3) I'll need to ask someone to do it when I'm next in the office

4) I've tried with two different backends. Same issue. The other system is 750/10.

5) 100% reproducible

6) Done that - nothing changed

7) It behaves the same whether the debugger view is open or not

😎 I get an error generated in the error log upon loading the context menu:

Unable to generate parameterized command for com.sap.xst4e.mta.natureRemove.handledmenuitem=org.eclipse.e4.ui.model.application.ui.menu.impl.HandledMenuItemImpl@75e43c0f (tags: null, contributorURI: platform:/plugin/com.sap.xst4e.cba) (widget: null, renderer: org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer@633a6f00, toBeRendered: true, onTop: false, visible: true, containerData: null, accessibilityPhrase: null) (label: %fragment.command.mtaNatureRemove, iconURI: null, tooltip: null, enabled: true, selected: false, type: Push) (mnemonics: null) (wbCommand: null). ElementId is not allowed to be null.

But nothing when running the unit tests directly from the view.

Yes, that's the root cause. Parameter rfc/ext_debugging should be 3 in all systems. I would actually call both systems misconfigured, so please ask the customer admins to change the values to 3. Details are described in note 668256.

Also, this configuration issue is not limited to ADT. If you create an external breakpoint in SAP GUI then it will also not stop for external requests like RFC or HTTP (OData). At least for the system where the value is 0 the SAP GUI debugger will also not work. Debugging your report from ADT worked because the embedded SAP GUI (just like the standalone SAP GUI) connects to the ABAP server via DIAG, not via RFC or HTTP.

A colleague from ABAP kernel will also follow up on this topic:
- The default value for this parameter is already 3, but it seems that the "recommended value" is actually 0. He will double check whether we can change that recommended value also to 3, in order to avoid future misconfigurations by admins.
- He will also check whether it's possible to just remove this quite old profile parameter completely and just "hard code" the value to 3 in the kernel
- I will check whether we should extend the ADT backend configuration guide

matt
Active Contributor
0 Kudos

Thanks Armin - I'll get onto the Basis teams as soon as I can figure out who they are... client is a very large organisation!

matt
Active Contributor
0 Kudos

There is such an option. But it doesn't help.

Sandra_Rossi
Active Contributor
0 Kudos

When it happens suddenly after hour(s) of correct debugging, this bug drives me crazy... Usually it happens during my ABAP Unit tests. The only solutions that seem to work: restarting Windows or wait for something like an hour and it works again, I don't know why...

Armin_Beil
Advisor
Advisor

Hi Sandra,

for upcoming backlog plannings, I will try to argue for getting some dev capacity for ADT debugger robustness & automated tests. Unfortunately our current dev capacity for debugger improvements is very limited.

Best regards,
Armin

matt
Active Contributor

Automated tests are so much nice in Eclipse than SAPGui. I hope it can be sorted.

Armin_Beil
Advisor
Advisor
0 Kudos

Thanks for the feedback Matthew. I actually meant that we should improve our automated Java tests, that test the functionality of the ADT debugger 😉