ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CA WA DE (dSeries): Applications in quiesce State

book

Article ID: 145761

calendar_today

Updated On:

Products

CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation DE DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries) CA Workload Automation DE - Scheduler (dSeries)

Issue/Introduction

The events are not triggering and the server is quiesce state.

Cause

The quiesce command will hold all events and applications.  This is a manual command and has to be issued manually in monitor perspective or CLI.  Once the command is issued, the events will not trigger and applications will not run.  The tracelog and audit logs capture the command and user who issued the command.

20200220 09:XX:XX.000 [facade:request] [INFO] RMI TCP Connection(9876)-10.10.10.10: [2020-02-20_09:XX:XX.000] OperationalFacade.quiesce() response: userToken=[UserToken[userId=USER123,tokenId=000000000000001234]], StandardResponse[statusMessage=Quiesce requested., statuscompletioncode=SUCCESS, statusmessageid=0000

Environment

Release : 12.x

Component : CA WORKLOAD AUTOMATION DE (DSERIES)

Resolution

Enter the following command in CLI to unquiesce the applications and server.  This command will unquiesce all the events and applications

unquiesce appl("*.*")event("*.*")reason("reason")

To unquiesce specific events, enter event with the prefix (user).

unquiesce event("schedmaster.verify")


The quiesce and unquiesce are also available in Monitor Perspective of Desktop Client.




Attachments