on 09-16-2010 3:25 AM
Hello all
many users reported us TIMEOUT issue in our system
we wanted to extract the report how many users were faced the same issue and why they have received 400 Session time out error.
what parameter needs to be adjusted in SRM to avoid the same problem
any help is appreciated and piece of information on this help .
Muthu
Hi,
If you want to see for how many users TIMEOUT dump has come then you can check the same in ST22 tcode and also in SM21.
The parameter for increasing the Time out value is rdisp/max_wprun_time where you can give the value. Also, I would like you to check if the Time out is coming when you are running any Z program or standard. If its any Z then check with your ABAPER's about fine tunning the same. Also, try to check the report by running it in background.
Regards,
Sharath
Edited by: sharath Babu on Sep 16, 2010 10:22 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Muthuraman,
The error you are experiencing is caused by the icm/conn_timeout parameter being exceeded. You should increase this parameter to solve your issue. Also there are a number of other parameters that will cause the webdispatcher and ICM to close a connection.
Please refer to SAP Note [824554|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383234353534%7d] for additional information in webdispatcher and ICM timeouts.
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This does not necessarily mean that the connection is actually timing out.
We had a similar issue with the Portal and how it communicated with SRM 7.
You may want to have your Portal Admin check into it to make sure all connection settings are correct.
Also, sometimes it helps to stop/restart the ITS services in SICF.
Hi Muthuraman,
Ok. So we dont know exactly why you are getting the 400 error. I would recommend that you increase the trace level of the ICM to 2 (SMICM -> Goto -> Trace level -> Set 2).
Then you can check for a user that is experiencing (via their IP address if its a direct connection to the ICM) and see exactly why the connection was closed.
If you wish you can attach the dev_icm trace with the IP address or timestamp of the issue and I will check.
Michael
I presume you are getting that error in a portal, bsp or similar as its a 400 error rather than a dump or screen error, so check your ICM parameters icm/keep_alive_timeout, icm/conn_timeout.
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.