topic Re: Debugger timout in Application Development and Automation Discussions

Debugger timout

Former Member — Thu, 22 Jan 2009 08:29:39 GMT

Hi,

There is a way to extend the debugger timeout,

Now if i don't do any action after 5 minute he throw out.

Regards

Former Member — Thu, 22 Jan 2009 08:32:44 GMT

It should be dependent on the maximum time allowed for a foreground transaction by your Basis team.

You may not be able to do anything for it.

Former Member — Thu, 22 Jan 2009 08:34:01 GMT

Hi,

You just contact with your BASIS people.

Regards,

Anki Reddy

MarcinPciak — Thu, 22 Jan 2009 08:34:49 GMT

Hi,

Only your basis team can do this, probably you won't have authorization to change profile parameters.

Go to RZ11, look for * timeout * parameter. I think this one abap/timeout is responsible for this.

Regards

Marcin

former_member206439 — Thu, 22 Jan 2009 08:43:51 GMT

You can define this

period of time with the rdisp/max_debug_lazy_time parameter, the default

is 10 minutes.

it can be done by basis people

former_member206439 — Thu, 22 Jan 2009 08:47:35 GMT

these are the 2solutions

1. Implement a timeout for lazy debugging sessions. If a debugging

session is unused for a time, it is reset, meaning that the debugger is

terminated and any existing DB locks are released. You can define this

period of time with the rdisp/max_debug_lazy_time parameter, the default

is 10 minutes.

2. There are functions that the liveCache can use to determine whether

debugging sessions exist and to reset these by program.

These enhancements are available as of 46D patch-level 123. Since the

parameter is known only in the kernel and not in transaction RZ11, the

following warning occurs after you include the parameter when you check

the profile:

"Unknown parameter rdisp/max_debug_lazy_time"