RFC receiver channel message remains in status "being processed"

[former_member301120]

Hello to all,

I've got a RFC-receiver channel. normally all works fine. But sometimes a message remains in status "being processed" (SMQ2) but there is no process neither in SM66 nor SM51.

In runtime work bench the message is in status wait, when you choose in message monitoring integration server.

In fact the message is never delivered an all other queuing messages in the same queue will not be processed.

Is there any solution for this problem?

Best regards

Christian

[Former Member]

hi christian

WAITING means here

The first LUW of this queue has dependencies to other queues, and at least one of these queues currently still contains other LUWs with higher priorities.

Just deregister it and Register once again.

If there is no entry in the SMQ2, then it is good, so that message will be processing. ANd there is no message is in Queue.

But in your case, there may be some other problem.

Can you check this SAP link-

http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/df5f3c8dde1c67e10000000a114084/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/96/8412417301ee6fe10000000a1550b0/frameset.htm

reward points if helpfull

regards

kummari

[rodrigoalejandro_pertierr]

hi Christian.

does the queue stuck of few minutes later it release.

maybe the server is proccessing a large file so the queue stuck until the procces finish

[former_member301120]

Yes it's a large file ca 10MB.

After ca. 1,5h the queues goes in status sysfail, time exceeded.

Regards

[Former Member]

Hi,

restart the message...

first check the SXMB_ADM-> Configuration-->Integration Engine Configuration --> Specific Configuration...under category.... Runtime the parameter QRFC_RESTART_ALLOWED is set to value 1.

then you can restart the message.

as the message is in large size that got stuck and failed in queue.

thanks,

madhu

Edited by: Madhu sudhan Reddy on Jul 15, 2008 2:17 PM

[Former Member]

hi christian

SYSFAIL

A serious error occurred while the first LUW of this queue was being executed. The execution was interrupted. When you double-click on this status, the system displays an error text. For more information on this error, see the corresponding short dump in the target system (transaction ST22). No background job is scheduled for a retry and the queue is no longer processed. To solve the problem, information from the affected application is required. See SAP Note 335162 for the error text "connection closed".

regards

kummari

[rodrigoalejandro_pertierr]

hi Christian

SXMB_ADM...integration engine configuration set the parameter QRFC_RESTART_ALLOWED is set to value 1.

some tunning parameters should be set, its not a queue problem.

see this links

Thanks

Rodrigo

PS:rewards points if useful

[Former Member]

hi christian,

The main problem is here

1)The tRFC/qRFC sender always expects a defined response from the receiving system. This response is send when the executing LUW is completed.

2)Even if the RFC connection was terminated because of network problems, this error situation is reported from the RFC layer to tRFC/qRFC and the respective error text is also displayed in the monitors.

3)However, if no response is reported and instead the connection from the RFC view (not tRFC/qRFC view) is released 'normally', the system enters the error text "connection closed" in the current LUW.

and

Unfortunately there are different causes which can lead to a "normal" RFC close connection. The following list contains some of them:

1. tRFC/qRFC receiver is an external program

The external program closes the RFC connections with RfcClose during processing of a LUW, it returns no result.

2. tRFC/qRFC receiver is an R/3 System

a) During debugging a LUW from within the tRFC/qRFC monitors, you press F3/BACK. Then all RFC connections in this application are closed "normally".

b) The currently executed LUW in the receiving system is terminated by an external event. For example, this can happen if it exceeds the max. allowed runtime (rdisp/max_wprun_time). During this error the system triggers a short dump with error "TIME_OUT". Note, this event can only be caused by an external event and no internal event. tRFC/qRFC can recognize if an exception is triggered within a LUW and it will send a response to the sender.

so,

you need to solve the problem in the APPLICATION SYSTEM

reward points if helpfull

regards

kummari

[rodrigoalejandro_pertierr]

hi Christian

SXMB_ADM...integration engine configuration set the parameter QRFC_RESTART_ALLOWED is set to value 1.

some tunning parameters should be set, its not a queue problem.

see those SAP Notes

SAP Note 384971

SAP Note 74141

SAP Note 539917

SAP Note 369007

SAP Note 723909

SAP Note 552522

Thanks

Rodrigo

PS:rewards points if useful

[former_member301120]

Hello Kummari,

where is the dump "TIME_OUT" triggered? I get this dump on my XI host.

Regards

[rodrigoalejandro_pertierr]

hi Christian,

thats right. the time out is in PI server because the server doesnt finish the process in the max time defined in PI

Thanks

PS: Rewards points if useful please