on 04-12-2005 5:41 PM
Using Enqueue statments we create locks on the database record when a user is viewing/changing them. If a user leaves for lunch and SAP releases the lock that is in SM12 is there a way to cancel the web session they were working with?
Thanks,
Anthony
You can alter the timeouts to match the lock length or do so programmatically by checking if the lock is there and if so OK otherwise manually close the session.
OK this is just late night random thoughts but in theory they should work
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think you actually have a lock lenght in SAP, your lock lifetime is tied to the session state. My question is - Is this a spilt system landscape - BSP application on one system (such as a standalone WebAS) and your Lock set in another system (such as a backend R/3 system).
Now when your session is destroyed in on the BSP side (for a stateful BSP), any remote session created by RFC (and the corresponding locks) are also cleaned up.
So my rule of thumb has always been to set the BSP session timeout shorter (even if by a small amount) than your backend system timeout (which is also probably a good idea from a system resource standpoint as well).
Thanks for the replies. To answer your questions first we do not have a standalone WebAS. I'm using the Single_Session_Frame.htm service to remove the locks if the web browser is closed. And that works perfectly.
What we asaw in our test system was the the SAP R/3 system would drop the logic lock if it sat too long without activity, and the BSP session would still be running. SO now I have two users who could access and change the same record.
Where do I set the BSP session timeout? Is that a server or admin setting?
Thanks so much,
Anthony
> Where do I set the BSP session timeout? Is that a
> server or admin setting?
There is a small section in this document on timeout values: <a href="/people/mark.finnern/blog/2003/09/24/bsp-in-depth-confusion-between-stateless-stateful-and-authentication">BSP In-Depth: Confusion between Stateless, Stateful and Authentication</a>
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
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.