BSP Application Timing Out

[Former Member]

Hello all, I have a BSP application that runs successfully when processed all at once. But if you take more than a couple minutes between clicks, it times out. I found many ICM parameters for this but I am not sure how they all work together. The "icm/keep_alive_timeout" is set to a system default of 60 seconds. I'm not sure if this is causing the issue or not. Does anyone have any advice or know of a blog or something that talks about time outs and BSP processing?

I tried to code for this by writing all pertinent information to cookies but I can't read the cookies after the r/3 session is terminated. I have the expire date set to one day in the future so it should be there. I see it in table SSCOOKIE but I cannot read it. My session id remains the same so I am not sure of the problem.

Any help is appreciated, Troy

[eddy_declercq · Accepted solution]

Hi,

You can decide how long the session can last if you double click on the app node within SICF. Under the service options, you can define a session timeout.

the profile parameter rdisp/plugin_auto_logout will otherwise clear things after 30 minutes.

Eddy

PS.

Put yourself on the SDN world map (http://sdn.idizaai.be/sdn_world/sdn_world.html) and earn 25 points.

Spread the wor(l)d!

[Former Member · Accepted solution]

I will have to take a look becuase I am timing out in a couple minutes. Why would that be?

[eddy_declercq · Accepted solution]

Hi,

What value has this profile parameter configured? You can check this with eg RZ10.

Eddy

PS.

Put yourself on the SDN world map (http://sdn.idizaai.be/sdn_world/sdn_world.html) and earn 25 points.

Spread the wor(l)d!

[Former Member · Accepted solution]

Thank you, for some reason the SAP default in DEV and PRD is 30 minutes but in TST, the SAP default is 30 seconds??????

Thanks again, we are bouncing the instance at noon.