cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

RSPLSE - I find few selections in Locking conflict tab.

Former Member
0 Likes
1,028

When I run the BADI calculations for the model, I observe some dumps in  ST22 with exception  CX_UJO_W RITE_BACK  and terminated program CL_UJO_WRITE_BACK=============CP Error Analysis: The reason for the exception is:  Error obtaining concurrency lock (enqueue_server_busy) when I observe the RSPLSE , in the Tab 'Locking Conflict' I find  some selections in lock request.  Please  find attachment. How to release the Locks in the RSPLSE ?  there are no entries in SM12. Regards Srinivas

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Likes

Hi Srinivas,

Unfortunately your screenshot doesn't include the top part of that screen: does it have 2 user IDs filled or just one?

Regards,

Gersh

Former Member
0 Likes

Hi Gersh,

Screenshot attached. Only one user is available.

Regards

Srinivas

gregor_dieckmann
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Srinivas,

as you said already you got an 'enqueue server busy' exception i.e. the enqueue server was handling another enqueue or dequeue request already. That you had this situation can also be seen in the empty field 'User with Lock'. Have you read note 928044? You should do this and use some of the BPC related customizing settings mentioned there (and in the BPC documentation) and you should also use 'Lock Attempts' and 'Wait Time in Seconds' settings.

Regards,

Gregor

gregor_dieckmann
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

RSPLSE just records and displays the last lock conflict. This does not mean that there are still locks. By the way, this is easy to check also with RSPLSE on the third tab.

Not nice that BPC creates a dump when the lock server just sends an exception that can be catched and treated nicely. Check the BPC related parts of note 928044 (sizing note).

Regards,

Gregor

former_member186338
Active Contributor
0 Likes

Sorry, but there is no generic answer. You have to debug and analyze your badi code to understand the reason for the locking conflict.