Update Namespace Activity Stuck in BUSY State Due to SocketTimeoutException
Article ID: 443218
Updated On:
Products
Issue/Introduction
The Update Namespace activity becomes stuck in the environment, causing the namespace object to remain in a BUSY state. Consequently, subsequent delete namespace calls never execute.
During the AttachContentLibrariesPhase, a child activity (AssociateContentLibrariesToNamespaceActivity) is kicked off and registered, but the parent UpdateNamespaceActivity waits endlessly for it to complete.
Sanitized log excerpt showing the registration and indefinite wait state:
file-log-##########.log:YYYY-MM-DD HH:MM:SS | DEBUG | Backend-activity-pool-166106 | c.v.v.a.t.e.AbstractActivityEventRelay | Registering activity, activity-id=urn:uuid:e2f370db-3eca-4746-b8ff-7db232736007 | requestTime=1779946882686, request=PUT https://<REDACTED_HOSTNAMES>/cloudapi/vcf/namespaces/urn:vcloud:namespace:2106a546-64dc-4792-b348-04241b91242b, ACTIVITY_HANDLE=activity=(com.vmware.vcf.backend.vc.UpdateNamespaceActivity,urn:uuid:52355066-ec45-4565-8873-a4398dc09a3d), requestInfo=requestId=6a17d5813cd4573b13ff2178ffb2feb5-d6f5bdc1-65d8-4a8a-a48d-88f6574dd2af,request=PUT https://<REDACTED_HOSTNAMES>/cloudapi/vcf/namespaces/urn:vcloud:namespace:2106a546-64dc-4792-b348-042...,requestTime=1779946882686,remoteAddress=<REDACTED_IPS>:38252,userAgent=ccs-infra-eas-app-79466b96cb-prdgv,accept=application/json;version 40.1,Host=<REDACTED_HOSTNAMES>, REQUEST_ID=6a17d5813cd4573b13ff2178ffb2feb5-d6f5bdc1-65d8-4a8a-a48d-88f6574dd2af, remoteAddress=<REDACTED_IPS>:38252, jti=<REDACTED_SECRETS>, accept=application/json;version=40.1, OPERATION_TAG=vcd=00921e08-0557-4ea7-910c-d6385f705423,task=52355066-ec45-4565-8873-a4398dc09a3d
file-log-##########.log:YYYY-MM-DD HH:MM:SS | DEBUG | Backend-activity-pool-166106 | c.v.v.b.v.UpdateNamespaceActivity | [Activity Execution] Waiting on ActivitySupervisionRequest: SupervisedCompletion [activity=com.vmware.vcf.backend.vc.UpdateNamespaceActivity@2349f4b6, activityExecutionState=com.vmware.vcloud.activity.impl.FrameworkActivityExecutionStateImpl@d56fec2, activityEventEmitter=ActivityEventEmitterTemplate [activityEventListenerSet=[com.vmware.vcf.backend.vc.UpdateNamespaceActivity$AttachContentLibrariesPhase@49eef1eb]], beginTimeMillis=1779946885076, canceled=false, complete=false, futures(size)=1, eventTracker(size)=0, nextPhase=class com.vmware.vcf.backend.vc.UpdateNamespaceActivity$FinalPhase, onComplete=com.vmware.vcloud.activity.executors.LocalActivityExecutor$3@de21940, timeoutNotificationSent=false, timeoutMillis=180000, shortCircuit=false] next phase: class com.vmware.vcf.backend.vc.UpdateNamespaceActivity$FinalPhase - Handle: urn:uuid:52355066-ec45-4565-8873-a4398dc09a3d, Current Phase: UpdateNamespaceActivity$AttachContentLibrariesPhase
Environment
VCF Automation 9.1.0
Cause
A SocketTimeoutException occurs during the UpdateNamespaceActivity. Because AttachContentLibrariesPhase extends BasePhase (which lacks timeout handling) instead of AbstractTimeoutPhase, the child activity is persisted in the "activity" table but not in the "task_activity_queue" table. When the cell service recovers, no activity is queued for it to execute, causing the parent activity to wait endlessly for a completion signal that never arrives.
Resolution
This issue will be fixed in future release.
Feedback
