TIBCO-AMX-ADMIN-002001 |
Trying to reconnect to the EMS server. |
TIBCO-AMX-ADMIN-002097 |
Could not reconnect to the JMS server. |
TIBCO-AMX-ADMIN-002098 |
Failed to get host queue status. |
TIBCO-AMX-ADMIN-002099 |
Task entity type and task entity identifiers are required inputs. |
TIBCO-AMX-ADMIN-002100 |
Could not reconnect to the JMS server. |
TIBCO-AMX-ADMIN-002101 |
Failed to get host queue status. |
TIBCO-AMX-ADMIN-002102 |
Task entity type and task entity identifiers are required inputs. |
TIBCO-AMX-ADMIN-002103 |
Trying to reconnect with JMS server. |
TIBCO-AMX-ADMIN-002104 |
Marking for processing {0} pending tasks. |
TIBCO-AMX-ADMIN-002105 |
AdminServersGroup is NULL or Admin Server is not a leader. AdminServersGroup: {0}. |
TIBCO-AMX-ADMIN-002106 |
Failed to queue task_id:''{0}''. |
TIBCO-AMX-ADMIN-002107 |
Could not collect tasks already queued: {0}. |
TIBCO-AMX-ADMIN-002108 |
TaskService.onStatusNotification called with null status or null notification processor. |
TIBCO-AMX-ADMIN-002109 |
Error: Task with id:{0} has cyclic dependencies. |
TIBCO-AMX-ADMIN-002110 |
Failed to get a task result. |
TIBCO-AMX-ADMIN-002111 |
Error while locking task for update. |
TIBCO-AMX-ADMIN-002112 |
UtilityTask cannot have empty dependencies. |
TIBCO-AMX-ADMIN-002113 |
Invalid mode specified for UtilityTask. |
TIBCO-AMX-ADMIN-002114 |
Evaluating task_id:''{0}'' since one of it's dependency task_id:''{1}'' failed. |
TIBCO-AMX-ADMIN-002115 |
Deleting NoOpUtilityTask task_id:''{0}'' as it has no more dependencies. |
TIBCO-AMX-ADMIN-002116 |
Ignoring execution of task “{0}” (taskId:''{1}''). |
TIBCO-AMX-ADMIN-002117 |
TaskServiceUtil.getTasksByDescriptor() ignored task_id:''{0}''. |
TIBCO-AMX-ADMIN-002118 |
Could not find registered Task executor for task input:''{0}''. |
TIBCO-AMX-ADMIN-002119 |
TaskInput for task {0} should be a IndeterminateQueueTaskInput as it does not specify a queue, but it is not. |
TIBCO-AMX-ADMIN-002120 |
Registered task for task {0} should be a IndeterminateQueueTask as it does not specify a queue, but it is not. |
TIBCO-AMX-ADMIN-002121 |
Exception occurred in calling {0}.handleTaskCancellation. |
TIBCO-AMX-ADMIN-002122 |
Calling taskService extension {0} failed. |
TIBCO-AMX-ADMIN-002123 |
Exception occurred in TaskServiceImpl.possiblyUpdateUserActionStatus() for user_action_id:''{0}'' |
TIBCO-AMX-ADMIN-002124 |
Could not find registered Task executor for task input:''{0}''. |
TIBCO-AMX-ADMIN-002125 |
Could not queue messages into the JMS server. |
TIBCO-AMX-ADMIN-002126 |
Message not queued as EMS server is not available; see previous log messages. It is queued later when EMS is available. |
TIBCO-AMX-ADMIN-002127 |
Could not queue messages into the JMS server: The queue URI was null. |
TIBCO-AMX-ADMIN-002128 |
Calling taskService extension {0} failed. |
TIBCO-AMX-ADMIN-002129 |
Unable to store exception in the TaskResult as a BLOB. |
TIBCO-AMX-ADMIN-002130 |
Calling taskService extension {0} failed. |
TIBCO-AMX-ADMIN-002131 |
The real error cannot be retrieved. It is packed inside an exception class “{0}” that is of unknown type. View the server log file to find the real error. |
TIBCO-AMX-ADMIN-002132 |
The failed task (task_id:''{0}'') is now marked (committed) in the database. |
TIBCO-AMX-ADMIN-002133 |
User action tracked by {0} completed successfully. |
TIBCO-AMX-ADMIN-002134 |
User action tracked by {0} completed in error. |
TIBCO-AMX-ADMIN-002135 |
Starting to execute task identified by task ID “{0}” and user action {1}: {2}. |
TIBCO-AMX-ADMIN-002136 |
Successfully executed task identified by task ID “{0}” and user action {1}: {2} |
TIBCO-AMX-ADMIN-002137 |
Failed to execute task identified by task ID “{0}” and user action {1}: {2}. |
TIBCO-AMX-ADMIN-002138 |
Processed {0} status notification for task identified by task ID “{1}” and user action {2}, status is “{3}”, returning result “{4}”. |
TIBCO-AMX-ADMIN-002139 |
Cleanup of historical user actions occurs because the size of the TASKRESULT table grows beyond the preset threshold ({0}). It reduces the table by 15%. Starting to remove {1} user actions with {2} task results. |
TIBCO-AMX-ADMIN-002140 |
{0} user actions with {1} task results were removed successfully. |
TIBCO-AMX-ADMIN-002141 |
Could not execute tasks since node “{0}” is not running. |
TIBCO-AMX-ADMIN-002142 |
Could not execute tasks since host “{0}” is not running. |