Documents

sapnote_0000507776.pdf

Categories
Published
of 3
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Share
Description
19.07.2013 Page 1 of 3 SAP Note 507776 - Status SLEEP in SM50 Note Language: English Version: 12 Validity: Valid Since 13.01.2003 Summary Symptom In SM50, the update or batch work processes remain in the SLEEP status.This can last up to 15 minutes. Other terms qRFC, tRFC, SLEEP, SM50, stop cpic, RFC, stop RFC, maxwait_for_dia_wp, abap/maxwait_for_dia_wp Reason and Prerequisites You call tRFC or qRFC in update or batch work processes and a resource bottleneck occurs so that no more di
Transcript
  19.07.2013Page 1 of 3  SAP Note 507776 -Status SLEEP in SM50  Note Language: EnglishVersion: 12 Validity: Valid Since 13.01.2003 Summary Symptom  In SM50, the update or batch work processes remain in the SLEEP status.Thiscan last up to 15 minutes. Other terms qRFC, tRFC, SLEEP, SM50, stop cpic, RFC, stop RFC, maxwait_for_dia_wp,abap/maxwait_for_dia_wp Reason and Prerequisites You call tRFC or qRFC in update or batch work processes and a resourcebottleneck occurs so that no more dialog work processes are available fortRFC/qRFC.As of qRFC version 6.20.043, when a resource bottleneck occurs, the systemwaits for a maximum of 15 minutes for a free dialog work process (a checkis performed once a second).If no interactive work process becomesavailable within this time, the tRFC/qRFC is processed in synchronous mode(rather than asynchronous mode) after 15 minutes.During this wait time (15minutes maximum), the update and batch process display the status 'SLEEP'.A resource bottleneck can be caused by poorly configured dialog workprocesses for tRFC/qRFC in RZ12 (see note 74141 for more information). SolutionThe following solutions are possible: oUsing note 74141, first check the resource distribution in RZ12 torule out incorrect configuration.oThe above-mentioned wait time of 15 minutes was introduced to avoida deadlock while queuing for a dialog and update work process.Sincethis only occurs for applications that call tRFC recursively, thequeue time should be set to '0'.The system thus immediatelyswitches to synchronous processing in the event of a resourcebottleneck.Change required:In the LARFCTOP include, set the variable maxwait_for_dia_wp to 0. Prerequisite: This is only useful if you are using supplement 8 ofqRFC version 6.20.045.This change is delivered as standard with supplement 9 of qRFC version6.20.045.oIf the above-mentioned deadlock problem occurs as a result of thischange, you must set a wait time value that corresponds to yourapplication requirements and existing resources. There are nogenerally applicable rules for this value. You must determine the  19.07.2013Page 2 of 3  SAP Note 507776 -Status SLEEP in SM50 value empirically.However, the value should not exceed 900 seconds(=15 minutes). Header Data SAP Note No.:507776Note Language:EnglishMaster Language:GermanVersion:12Valid Since:07.10.2008Release Status:To Be ArchivedReleased on:07.10.2008 07:50:46Released by:Omar-Alexander Al-HujajPriority:Recommendations/additional infoAuthor:Wolfgang BaurEntered by:Sasan Memar-ZahedaniProcessed by:Wolfgang BaurLast Changed by:Omar-Alexander Al-HujajOn:07.10.2008 07:50:47Category:Help for error analysisStandard Note:NoPrimary Component:BC-MID-RFC RFC The Note is release-independent Related Notes NumberShort Text577368Deadlock due to blocked update processes74141Resource Management for tRFC and aRFC  Attributes  19.07.2013Page 3 of 3  SAP Note 507776 -Status SLEEP in SM50 AttributeValueTransaction codesRZ12Transaction codesSM50Transaction codesSM58Transaction codesSMQS Internal Memos  Memo from Omar-Alexander Al-Hujaj On 07.10.2008 09:50:47 Da Supplement 11 Voraussetzung ist, ist dieser Hinweis obsolet.
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks