PI - Stuck queues due to system dumps

[jorge_biritxinaga]

When processing messages one by one, the queues are working fine, with very good performance times.

When the messages get growing, the system does not process them and we get a short dump with this info:

If I delete all the messages from the queue and execute the failed message individually again, it works fine.. so it doesn't seem a config problem...

Short dump description:

How to correct the error

Long running programs should generally be run as batch jobs.

If that is not possible, the system profile parameter "rdisp/max_wprun_time"

can be

enlarged.

Depending on the cause of the error, you may have to take one of the

following measures:

- Endless loop: Correct program;

- Dataset resulting from database access is too large:

Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table

(for example);

- Database has unsuitable index: Check index generation.

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

please use the following search criteria:

"TIME_OUT" " "

"CL_XMS_PERSIST================CP" bzw.

"CL_XMS_PERSIST================CM035"

"READ_MSG_MASTER_VIA_TID_PUB"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem (short dump).

To obtain this, select "System->List->Save->Local File (unconverted)"

on the current screen.

2. A suitable hardcopy printout of the system log.

To obtain this, call the system log with Transaction SM21

and set the time interval to 10 minutes before and 5 minutes after

the short dump. In the display choose "System->List->Save->

Local File (unconverted)"

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, choose "More Utilities->Upload/Download->Download" in the

Editor.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

Information on where terminated

Termination occurred in the ABAP program "CL_XMS_PERSIST================CP" -

in "READ_MSG_MASTER_VIA_TID_PUB".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 43

of the (Include) program "CL_XMS_PERSIST================CM035".

Thaniks for your help!

Jorge

[jorge_biritxinaga]

Hi Wayne,

Thanks for your help. Yes, the error I am getting is a time out. But normally these messages are processed in 2 or 3 seconds.

Only when it takes longer I receive the time out error message.

I will increase the parameter you sayto test it and will tell you the result. Bu¡t I think the problem is in the reason why sometimes takes much longer, if it should take fewseconds to process each message.

[Former Member]

Hi Jorge,

Yes, you are correct, most of the time these messages only take a few seconds to process unless they are very large. If you are using Oracle, make sure the database statistics are up to date. Monitor SM50 after you increase the timeout parameter and watch for long sequential read times. If you see that, check the stats on the tables being read using DB20.

Let me kno how it goes.

WL

[Former Member]

Hi Jorge,

Are you getting a TIME_OUT short dump? If so, increase the value of the rdisp/max_wprun_time parameter.

If it's not a TIME_OUT, what error message are you getting?

WL.