引起SAP WebClient UI页面出现超时(time out)错误的另一个原因
Sometimes you would see the following page if you are clicking anywhere in a page which is idle for quite a long time.
However, there are definitely some other causes which would also lead to this timeout page – the session itself is not timeout, instead within the session, there are some exceptions raised in the backend and caught by the UI framework. As a result you could not see any dumps in ST22, and this timeout page would sometimes lead you to the wrong way of trouble shooting. For example in this thread, some friend is suggesting to enlarge the related timeout profile in RZ10. For sure that would definitely not work, since the issue in the thread is nothing to do with the real timeout issue, but instead the exception caused by a custom enhancement.
I would share with you my example how to find the root cause of this kind of I call it “pseudo” time out issue in an efficient way:
My example
click the Service Order ID for the first time, nothing happened. Click it again( or any other clickable part in the UI), I get the above timeout page.
How to figure out the root cause
I have two different approaches. The first one will take several minutes to find the root cause via debugging.
(1) Create a breakpoint based on exception class CX_ROOT( for detail see this blog )
Launch UI and click hyperlink for the first time, the breakpoint is triggered and debugger stopped. In the status bar we get the hint that exception CX_BSP_WD_EXC_WRAPPER occurs. Set another breakpoint in its CONSTRUCTOR method.
(2) Relaunch the UI, the breakpoint in exception class CONSTRUCTOR is triggered, telling us there is something wrong with a custom UI component ZCUSTOM/MainWindow. In line 51 we know the exception class CX_BSP_WD_INCORRECT_IMPLEMENT. Set the breakpoint in its CONSTRUCTOR again.
(3) Relaunch the UI, now we find root cause: The overview page tries to display the view defined in ZCUSTOM/MainWindow, however it is not in the parsed component usage repository table ( me->usages in line 4)
Double check it in UI workbench it is because the custom UI component is added as component usage based on enhancement set A, however currently enhancement set B is active in current client.
The second approach is even more efficient. You could enable the UI framework to persist the exception which are raised and caught somewhere for example your own Z table with little effort so that it is convenient for you to check them afterwards. For detail steps please see my blog How to persist the UI exception so you can view them later.
In my example, I could immediately know this issue is caused by incorrect component usage with the exact usage name without debugging.
If you would like to know why timeout page is always displayed, although it is not a timeout issue at all, please find reason here.
要获取更多Jerry的原创文章,请关注公众号"汪子熙":
相关文章
- SAP UI5应用在SAP WebIDE里clone之后出现404 not found error for sap-ui-core.js错误的原因分析
- SAP Fiori Launchpad 错误消息 - 400 File is not contained in a resource root
- SAP云平台部署HTML5应用时的错误消息Failed to report quota consumption
- UI5应用clone到webIDE后,如何处理无法加载sap-ui-core.js的错误
- SAP UI5 attachment绑相对url
- SAP ABAP 通过 https 消费外部 API 遇到错误消息 SSSLERR_SSL_CONNECT
- SAP CRM Enterprise Search initial load 遇到错误该如何处理
- SAP ABAP OData 服务诊断工具 /IWFND/ERROR_LOG 的使用方法试读版
- 外部系统调用PO的webservice服务,往SAP系统发送数据,用的XISOAPAdapter的方式,出现错误
- 遇到SAP WebClient UI的白屏错误,应该如何分析?
- SAP CRM中间件Generic stop set的错误如何解决
- SAP CRM WebClient UI,如何快速定位到抛出错误消息的那一行代码
- 在SAP Spartacus产品明细页面用outlet显示自定义数据
- SAP 电商云 Spartacus UI production build 时遇到和 orderCore 相关的错误
- 如何在SAP Cloud for Customer的Silverlight UI中找到后台错误的明细
- SAP Commerce Cloud OCC API UnknownResourceError 错误
- 使用Eclipse连接SAP Netweaver系统遇到的错误消息和解决办法
- 使用SAP WebIDE往Github上推送代码修改时遇到错误消息 Commit request failed Commit failed. Ref must be HEAD and is HEAD
- SAP Cloud Application Studio里试图创建Lead扩展字段失败的错误消息
- SAP UI5应用在SAP WebIDE里clone之后出现404 not found error for sap-ui-core.js错误的原因分析
- SAP Fiori Elements edit按钮的实现细节
- SAP odata消费失败的故障排错
- 如何通过 ABAP 代码给 SAP OData 元数据增添注解试读版