Dialog WP is not restarted after abap/heaplimit reached and step terminated

[Former Member]

Hello,

ECC6 : SP12

Solaris 10

Oracle 10g

We're facing a very disturbing problem over the past few weeks, in our

formation environnement.

When Dialog Work Processes exceed the amount specified in

the parameter abap/heaplimit, and the dialog step is

terminated, the work process is restarted, the memory then becomes

available for other processes, that's the normal behaviour.

BUT sometimes, the work process is not restarted, and keeps the status "on hold" indefinitely, the memory still remains occupied by the process, despite the fact that the user that was using that process is no more connected !!!

SM 51 trace log of work process 1

M Thu Oct 18 10:32:34 2007

M ***LOG R2G=> ThPlgTimeout, Timeout () [thxxplg.c 5385]

M

M Thu Oct 18 10:33:34 2007

M ***LOG R2G=> ThPlgTimeout, Timeout () [thxxplg.c 5385]

M

M Thu Oct 18 10:35:34 2007

M ***LOG R2G=> ThPlgTimeout, Timeout () [thxxplg.c 5385]

A

A Thu Oct 18 10:37:48 2007

A WP has reached abap/heaplimit = 40000000 bytes

And then nothing during hours ...

This happens with both GUI users and with http users (EP6 portal

requests).

The process is NOT killed after the timeout specified in

rdisp/gui_auto_logout or rdisp/plugin_auto_logout.

The work process keeps the status "on hold", in the meantime others

dialog work processes, have the same behaviour : their abap/heaplimit is reached,

and they get the status "on hold PRIV".

After a while, short dumps TSV_TNEW_PAGE_ALLOC_FAILED are generated, and we have to kill manually the users sessions (sm04) to release the heap memory.

At that moment ONLY the work process is restarted, and becomes available to other user sessions.

Any Idea ?

Thank you in advance for any help.

Frod.

[JPReyes]

Hi Indus,

Dialog process go into PRIV when the system does not have enough memory to keep them going... basically the process will wait until the system can give them more resources...

Basically this is a memory tweaking issue...

Check parameters..

PHYS_MEMSIZE

abap\buffersize

heap paremeters

Regards

Juan

Please reward with points if helpful

[Former Member]

Thank you for your answer Juan ,

I've just noticed that only one red process out of five is in PRIV mode

The others process are just "On Hold" status and they're waiting indefinitely ...

0DIA 8719 On Hold GUI Yes5117SAPLSMTR_NAVIGATION

1DIA 24481 On Hold GUI Yes4841 SAPLSMTR_NAVIGATION

2DIA 8736 On Hold GUI Yes4740 SAPLSMTR_NAVIGATION

The trace files of the process show that :

A

A Mon Oct 22 15:51:23 2007

A WP has reached abap/heaplimit = 40000000 bytes

and then nothing ...

The users are no more connected, and the processes aare not restarted after the timeout.

any idea ?

[Former Member]

Hi Indus,

We are also facing the same issue i.e; Most of the Dialog work processes are going in to PRIV mode but after some time these are getting free ,

This has been happening frequently.

Did you resolve your issue ? If so can you please share the same?

[Sriram2009]

Hi Reddy

Basically you have to check which reports/program are going to PRIV mode? based on that you may require to do the fine tune & some of the standard program may require  SAP note to apply the fixes 2. Kindly check case-to-case which are the Program / Report having issues. it may be problem in the memory setting as said by Juan Reyes.

Could you share  your T code - ST02 screen shot?

Thanks & Regards

Srriam