Automatically restart messages stuck in smq2

[Former Member]

Hi,

I am having a problem that messages are getting stuck in the inbound queue and I need to manually restart it.

I have searched on this and have found that RSQIWKEX job can be used for this. I have tried testing it but the messages are still stuck in queue. It is having the status as SYSFAIL. Is it not possible to restart messages having this status?

The error which is there for SYSFAIL is Time Limit exceeded.

Please help me to restart such messages automatically which I am now doing manually.

Thanks and regards,

Siji Anup

[Former Member]

Also

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"

We had raised OSS regarding the same and they said this as database error.

[Former Member]

Hi,

Please help me regarding this issue. Whenever I execute this program RSQIWKEX the status of the messages stuck in queue changes from SYSFAIL to READY.

Is there any method to push these messages automatically from XI?

Regards,

Siji

[Former Member]

Hi ,

Pasting below the content of st22

The program "CL_XMS_PERSIST================CP" has exceeded the maximum

permitted uninterrrupted

runtime and has therefore been terminated.

The system profile contains the maximum runtime of a program.

When this time limit has been exceeded, the program is terminated

to make way for other users who may be waiting.

In the case of a work area, this means that

- endless loops (DO, WHILE, ...),

- database accesses producing an excessively large result set,

- database accesses without a suitable index (full table scan)

do not block the processing for too long.

The maximum runtime of a program is limited by the system profile

parameter "rdisp/max_wprun_time". The current setting is 1800 seconds. After

this limit has

been exceeded an attempt is made to interrupt the SQL statement running

or to tell the ABAP processor to interrupt the current program. A

maximum of 60 seconds is then waited. If after this time the program is

still active then the work process is restarted.

Thanks and regards,

Siji

[Former Member]

Hi,

Thank you so much for the quick replies

But I have gone through the above blog and thats how I got the name of the program RSQIWKEX

And we have already increased the time out parameter. But still its giving this error and getting stuck.

Thanks and regards

Siji

[Former Member]

Hello,

If you have increased the timeouts in all systems involved in the scenario, and the error is still occurring, could you please

go to trx ST22. Check for the TIME_OUT shortdumps there and let me know what information is in them.

Thanks,

Sarah

[Former Member]

Hello

If the error is SYSFAIL Time limit exceeded, you could try increasing the ICM timeout parameters:

- PROCTIMEOUT

- rdisp/max_wprun_time

Note ref:

#824554 ICM and SAP Web Dispatcher Timeout Parameter

Kind regards,

Sarah

[Former Member]

Hi Anup

Please refer the blog below; it might help you

regards