cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP session timeouts

Former Member
0 Kudos

It seems like BW users running web reports are constantly getting timed out of their sessions. I'm not certain if the ICM timeout setting in the instance profile (currently set at 1 hour) is the root cause. Some users seems to be timing out within 10 minutes.

We have set 7200 value for rdisp/plugin_auto_logout.

3600 value is set for icm/keep_alive_timeout.

Any solution of this problem?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi amarjit

What about icm/conn_timeout parameter?

As per your message, you have icm/keep_alive_timeout in 3600 seconds (10 minutes). In BW sometimes you should increase this value, because maybe you don't have good response times for those queries.

Check in ST03n / Bi statistics, the time spend for the top queries, and if you see large values, you should think in "query tunning with aggregates, cache" in order to reduce that.

(sorry for my english)

saludos !

Former Member
0 Kudos

The cause of "HTTP Session timeout" problem has been found. After a period of inactivity in the front end system, the connection to the back end system (auto logout) is interrupted. However, the screen (BSP Web-Frontend) remains unchanged and user believe that entries can still be processed, even though the session has actually terminated (oss note 821539).

Yesterday morning , i changed the value of "rdisp/plugin_auto_logout" parameter from 1 hour to unlimited (0) and after that no

HTTP session has been timed out in server, but with unlimited value, users could get the error message of "max. number of connected terminal".