cancel
Showing results for 
Search instead for 
Did you mean: 

Keeping break-point(?) in CL_HTTP_SERVER_NET->AUTHENTICATION

Former Member
0 Kudos

Hi,

when testing a WD4A application, I often get something like a break-point in the specified method. There was no break-point set there, I can't deactivate it (once it does not exist) Tried logging-off, /$SYNC, did not help. Is there anything I can try to stop new session-windows with the new debugger coming up?

This is something that happens from time to time, sometimes the debugger opens and stops in a other place (also something like CL_HTTP*). Still it is in standard WD4A code, not customer.

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member184578
Active Contributor
0 Kudos

Hi,

I guess, If some one else using user USer ID and set external break points?

Regards,

Kiran

Former Member
0 Kudos

nope, at the customer, this is my unique ID. In fact, it already (again) stopped doing that stuff, but I'm sure it will come again

former_member184578
Active Contributor
0 Kudos

I'm sure it will come again

Ok. Try this Report: RSBREAKPOINTS. Execute this report and select the option 'delete old break points' both session and HTTP, which removes all the stored break points.

Hope this helps u,

Regards,

Kiran

Former Member
0 Kudos

once this situation happens again, I'll try it, thanks