cancel
Showing results for 
Search instead for 
Did you mean: 

Limiting the number of plugin HTTP sessions for a single user

Former Member
0 Kudos

We had an issue with the CRM UI in IE6 where the screen flashed repeatedly; Opening page http://crmhost:8000/sap/bc/bsp/sap/crm_bm/cockpit.do

With each attempt a new Plugin-HTTP session was created in SAP until all system resources were used up.

Transaction SM04:

200 ACSMITH 192.168.10.30 14.46.33 1 Plugin HTTP

200 ACSMITH 192.168.10.30 14.46.33 1 Plugin HTTP

200 ACSMITH 192.168.10.30 14.46.33 1 Plugin HTTP

200 ACSMITH 192.168.10.30 14.46.33 1 Plugin HTTP

200 ACSMITH 192.168.10.30 14.46.33 1 Plugin HTTP

200 ACSMITH 192.168.10.30 14.46.33 1 Plugin HTTP

200 ACSMITH 192.168.10.30 14.46.33 1 Plugin HTTP

200 ACSMITH 192.168.10.30 14.46.33 1 Plugin HTTP

200 ACSMITH 192.168.10.30 14.46.33 1 Plugin HTTP

...

This issue was resolved by setting the privacy settings to accept all cookies.

Is there is a way to limit the number of plugin HTTP sessions that a single user can have in order to protect the back-end system.

Thank you,

Aubrey Smith

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

The way to limit the number of user at the same time is with the
parameter rdisp/tm_max_no. But, this is the limit for all type of
context in the backend (RFC,GUI,HTTP).

To limit the % of context for HTTP connection you must use the parameter
icm/HTTP/context_quota. This is the % of rdisp/tm_max_no for HTTP
connections.
There is no way to limit the number of users from Web Dispatcher
side.

If you want to limit the number of HTTP connections to 50 distinct users
and the parameter rdisp/tm_max_no is, for example, set to 100. The
parameter icm/HTTP/context_quota must be 50, that means 50% of 100
connections.

0 Kudos

The parameter is icm/HTTP/esid_max_ctx.

tiago_scherer
Participant
0 Kudos

Hello Aubrey Smith,

As far as I know there is no parameter to limit the number os sessions per user. What you could do is to set the timout parameter. If the user context of an external plug-in (such as HTTP) was held, and no action has taken place for rdisp/plugin_auto_logout seconds, the context is automatically deleted. If the parameter has the value 0, the automatic delete does not take place.

Regards,

Tiago

SergioFerrari
Active Contributor
0 Kudos

Yes Tiago, I confirm you're right.

Former Member
0 Kudos

Hi Sergio,

If you set: rdisp/plugin_auto_logout you also have to take care of rdisp/gui_auto_logout.

This is default set to 0 (never log out). If the plugin session is then killed, that leaves the gui session open. Resulting the user to be still logged on.

I had same kind of problems in a handheld scanner scenario for WM.

Regards,

Jos