Long WAITING requests

[Former Member]

Hi experts,

We are using NWDI 7.1 SP4. Until now we have never had any problem with activities activation (request type ACTIVATE) on CBS. But now we have more than 40 requests that are open and the first request (request id 3942) has request type ACTIVATE and request state WAITING. At least 7 other requests have this same request state (WAITING) and 2 requests have request state PROCESSING. The other 31 requests have request state QUEUED. The requests are on this state for 10 days and I can´t figure out which request is locking the others. How can I identify it? How can I make this requests be processed by CBS?

Best Regards,

Gabriela

[Former Member · Accepted solution]

hi Gabriela

Did you check for your SLD configuration? NWDI_CMSADM user id's password expired in SLD?

Thanks & regards

ala

[Former Member]

Hi sm_balas, I verified the user NWDI_CMSADM and it is not blocked and neither expired.

Hi Pramod, I´ve checked:

1) The Buildspace Input Mode is OPEN, Request Processing Mode is ON, Output Queue Mode is NOTQUEUED and Output Pool Mode is ON.

2) Already open, skiped

3) Service sap.com/tc.CBS.Service has status Started

4) At http://) of the target runtime system and the corresponding access data.

The synchronization functionality is not supported, because the used connection is unsecured. Please call the servlet with the 'https' protocol and use the correspondig 'https' port"

Currently we are not using Runtime Systems with auto deployment.

Passed 30 minutes after triggered deployment, the requests was not processed on the list, they remained unchanged.

This weird behavior is related only with that specific buildspace, the other 3 buildspaces used on that same NWDI has its requests processed with no delay.

Any other suggestions?

[pramod_gopisetty1]

Hi,

Without defining runtime systems where are you trying to deploy???

Define them and see if it works.

And let us know the update after runtime systems are defined.

Cheers,

Pramod

[Former Member]

Hi Pramod,

We are not using the Runtime Systems resource since each developer tests on it´s on CE server. The problem is related to activation of activities. Do you believe that the empty configuration of Runtime Systems can make the requests be frozen? Since this track was created, it never has a Runtime System configured, and it worked for 1 year at least.

Best Regardds,

Gabriela Tinti Vasselai

[pramod_gopisetty1]

Hi,

Help me understand, this is the process we follow:

1. On Checkout we create activity, makes the changes in that activity

2. We Check-in the activity

3. We Activate the activity, the activation request we can see in CBS

4. After Relasing the activity you have the changes in Dev system and

5. the activity is in import queue of Consolidation system

This is the flow of an activity, now tell me where are you getting error?

Cheers-

Pramod

[Former Member]

Hi Pramod,

Thanks for your response.

Item 3 (We Activate the activity, the activation request we can see in CBS) is ok, we can see the request on CBS, but this request has status pending forever, it´s never processed. I think it might have some deadlock or some request blocking the others from being processed. Why did it happen and how to make all those requests be processed?

We restarted the server 2 days ago and now all the requests have status "QUEUED" but none of them is being processed.

Best Regards,

Gabriela

[pramod_gopisetty1]

Hi,

Go to TCS Deployer and see if you can see the activities for the buildspace in question.

Try triggering the deployment manually.

Also check the link below and see if this helps

https://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29Q0010

https://wiki.sdn.sap.com/wiki/display/TechTSG/(NWDI)Home

Hope this helps.

Cheers-

Pramod

[Former Member]

Hi Gabriela,

Try restarting CBS Service in VA and see if the requests are getting processed.

Regards,

Pavithra

[pramod_gopisetty1]

Hi,

Check these things:

1. See if the Buildspace is Open or Closed in CBS

2. If the state of buildspace is close, select the track and in edit mode change the input mode from closed to open.

3. In Visual Admin make sure you have the CBS service running.

4. log on to the TCS Deployer and trigger the deployment process manually, to do so follow the steps below

a. go to URL : http://<hostname>:<port number>/TCS/Deployer

b. Check the Deployment status of the activity and see if you can find any issues stopping you to activate

c. or Trigger the Deployment for the Buildspace in question irrespective of the status of the activity.

d. Wait for 10-15 mins and see if the deployment is successful

Check the Note 1248926 - JVM Settings for 7.1 and see you have proper settings in place.

Hope this helps.

Cheers-

Pramod