external debugging in a multiple server environment

[former_member186444]

We are having issues with external debugging in a multiple server environment. In order that external debugging works, as well as setting a breakpoint, we also have to activate debugging on each server. So, we log onto each server and do this. However, as soon as we then log off the server, debugging on that server becomes inactive. This means that, due to load balancing, we need to remain logged onto each server while debugging...which also means we have to have quite a number sessions open at the same time.

Does anyone know if there is a way of keeping debugging active on each server after we have logged off it (ie, gone back to SM51) ? Maybe there is a parameter we can set ?

Also, is there any way of activating debugging on every server at the same time without having to log on to each one individually ?

thanks,

Malcolm.

[former_member186444]

I've just found function module SRDEBUG_FRAMEWORK_ACTIVATE (and SRDEBUG_FRAMEWORK_DEACTIVATE) which activates debugging across all servers. I've tested it out and it seems to work fine. Has anyone used these function modules and are aware of any downside to using them ? I'm assuming they will time out after a couple of hours but don't know for sure yet.

[former_member186444]

Further to this, there is a transaction code that calls this function module: SRDEBUG (see OSS Note 1004248). It's a little quirky but it does work.

1) Set your external breakpoint.

2) run transaction SRDEBUG. This will display a pop-up asking if you want to stop debugging. This pop-up must remain active until you want to stop debugging, so just leave it hanging there while you debug.

[bbalci]

Hello Dear Malcolm,

This information was very useful for me.

Thanks a lot.

Bulent