Quarantine

The Quarantine page displays internal system messages that were intercepted because they were not processed correctly or because the server was not able to process them at all. Placing these messages in Quarantine helps ensure that they are checked before taking action.

Overview

Internal messages control processing based on objects and their settings. If such messages are not processed correctly, it is so important to check their content.

Invalid messages cancel a server process. The message is intercepted and displayed in the Quarantine page of the Administration perspective. Quarantined messages do not affect server processes, so the quarantine protects your system.

When a message is intercepted and quarantined, a notification message is sent to all users with the relevant privileges in all clients of the system. Click Open on the quarantine notification message to access the Requests dialog.

Notes:

• You can only see this area of the Administration perspective and the respective notification in Quarantine in the AWI if your User object or UserGroup has the Create diagnostic information privilege, and the right to modify server processes. These permissions are typically managed by administrators. For more information, see Granting Automation Engine Privileges.
• Quarantined messages are helpful for further analysis. Consult CA Automic Support before releasing a message.

The left panel of the dialog provides the list of tasks that triggered the requests. The right pane displays information on the triggering task, and allows you to either Acknowledge the message, or open the Quarantine list.

To access the quarantine, open the Administration perspective and click Quarantine.

The Quarantine List

The columns in the list display the following information:

• Message number
• Alarm
  An alarm icon indicates that the message has not been acknowledged
• Status symbol
  Status of the message:
  • Unprocessed
    May be released after you contact CA Automic Support
  • Locked
    Has been logged for analysis purposes, but cannot be released
  • Processed
    Successfully processed, and can be deleted
• Occurrence time
  Time when the message was quarantined
• Reason for failure
  Information on the cause of the failure
• Replays
  Number of release attempts
• XML Stream
  Message sections (if retrievable) for analysis

Use the Refresh button in the toolbar to refresh the content of the table. The Export button lets you export the content of the table as a CSV file. Both buttons are available by default.

Deactivating Internal Message Checking

The Automation Engine checks internal messages by default. On UNIX, this can have a negative impact on performance.

To deactivate this function, use the parameter exception= in the INI file of the Automation Engine. For more information, see Automation Engine.

Reaction to Invalid Messages

The following steps are initiated if an invalid message is detected:

1. The message is put into quarantine.
2. All database modifications made by this message are canceled.
3. Further message information is written to the log file of the Automation Engine.
4. A trace file with the following name is created:
   UC4Dump_name of the Server process_RunID_timestamp.txt
   Example:
   c:\AUTOMIC\server\temp\UC4Dump_UC2T#WP002_40373135_20060406144901543.txt
5. If possible, a dump is created.
6. The ServiceManager restarts the aborted server process.
7. If the administrator has defined the EXECUTE_ON_EXCEPTION key in the UC_SYSTEM_SETTINGS variable, the specified object starts. For more information, see UC_SYSTEM_SETTINGS - Systemwide Settings.