on 07-30-2019 12:46 PM
Hi Everyone,
The suppliers are confronting a 500 Connection timed out error on SRM Portal 7.4(MM SUS) system.
I know that there are some threads to this error but I can´t find a solution for this.
Other threads suggest changing the PROCTIMEOUT parameter. However, after changing the parameter values to 600 at both web dispatcher and Portal os level, the problem still persists. This issue is coming for BSP as well as WDA Components. Backend is SRM system(MM SUS) to fetch data and Portal is 7.4 . We have tried restarting Web Dispatcher and Portal System, still no luck.
Please suggest a way forward.
Hi Ali.
Could you enable the http trace where it getting delayed kindly refer the SAP note
1431064 - How to take a HttpWatch trace in IE and Chrome
Regards
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Yes, we did the http watch analysis and back end rumtime SAT analysis, we found that the fm BBP_PD_SUSASN_GETDETAIL is taking a long time to process. Actually, this is inside a loop of table having over 13k records. The ideal solution would be to rewrite an optimized code, however the same code runs perfectly fine at times and sometimes it gets stuck in the wp. We took SRM DB restart and application restart, the issue till continues to occur at times.Oddly, the same code runs fine for all other users except for 3-4 users .
Regards,
Ali
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.