Hi,
One more thing noticed with the time out errors in system while trying to debug. We noticed run time errors "Debugging Impossible" . It says maximum number of WPs in debugging has been reached. The value of rdisp/wpdbug_max_no is st to 1. Same is set in other systems. But its working fine there. Dump details are given below:
"Short text
ABAP programs cannot currently be debugged.
What happened?
The running program is supposed to be debugged by the ABAP Debugger (for
example, by a BREAK-POINT statement).
Since you are in a production system or client (table T000), you can
only jump to the ABAP Debugger if the work process is able to switch to
debugging mode.
The maximum number or work processes in debugging mode has already been
reached, however, which means that debugging is not currently possible.
Error analysis
This runtime error is expected in certain situations and no further
analysis is required.
Dialog work processes that are running in debugging mode are assigned
exclusively to a single user, which protects the user context from the
process being switched. In general, however, users contexts that are
waiting for user input are rolled out of the old work process and
prepared to be rolled in to another work process. This requires a COMMIT
WORK.
Work processes that are in debugging mode cannot be used by other users.
This reduces the amount of free dialog work processes, which affects
system performance. This is why there is a maximum number of work
processes in this state in each system.
Only if this runtime error starts occurring frequently do you need to
check why so many dialog work processes are in debugging mode in this
system.
"
Regards,
Varun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.