Skip to Content
Author's profile photo Artem Ivashkin

GRC. Recent experience with BSP hanging

Dear colleagues,

I would like to share my recent experience with BSP hanging while I was trying to create ARQ. The only two services were hanging and only in one client. Please read my investigations and you will understand why.

Now I’m working on a project that requires to integrate GRC with LDAP group assignment. All customizing activities I perform into 200 client. In order to stop messing in LDAP logs, I stopped the connector and set status DOWN.

While I was trying to find something in the logs, in parallel, I decided to run my test scenario one more time. However, I wanted to active the connector right before I push “Approve” on the last stage of the request to minimize the log length.

And so I found? My function “Copy request” stops working. Then I try to use “Template Based Request” in order to create request from scratch. The same picture – BSP page hangs.

In the process monitor (SM50) I found this

The problem seemed global, and I called the same links from the other client of the same system (230). No problem, the pages opened in a second.

After time out I analysed ST22 information.

Shock!!! The first information I saw was:

And below

So, I would like to ask anyone who reads my post

How do you thing why the system does this selection?!

For me it seems not good, because for some reason LDAP connector might be switched off. And what? All activities with other connectors also stops?

If a grc architect reads my post, please, adjust the check logic or kindly explain why do we need it?


Artem Ivashkin

P.S. After you active LDAP connector again your service will work (the hanged pages will not alive, restart required).

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.