94 TRS-10000 to TRS-30030

TRS-10000: TRSConnectionMgr: DataSource is null.
Cause: DataSource is not set.
Action: Set DataSource first using MBeans.

Level: 1

Type: ERROR

Impact: Configuration

TRS-10001: Dispatcher failed to get jobs. {0}
Cause: SQLException
Action: Check database.

Level: 1

Type: ERROR

Impact: Data

TRS-10002: {0} failed to check job status. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10003: TxnReplayer URL:{0} is malformed. Replay item cannot be processed. {1}
Cause: Malformed TxnReplayer URL
Action: Change TxnReplayer URL specified in MBean or web.xml

Level: 1

Type: ERROR

Impact: Configuration

TRS-10004: Cannot open TxnReplayer URL:{0}. Replay item cannot be processed. {1}
Cause: TxnReplayer might not be running
Action: Check network. Make sure TxnReplayer is running

Level: 1

Type: ERROR

Impact: Network

TRS-10005: Dispatcher encountered an error during update of the REPLAY_USERS table. {0}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10006: JOB FAILED: clientId = {0}, JobId ={1}.
Cause: Job might be hanging or crashed.
Action: Consult administrator.

Level: 1

Type: ERROR

Impact: Data

TRS-10007: {0} failed to get database connection.
Cause: Database related
Action: Check database, or check DataSource.

Level: 1

Type: ERROR

Impact: Data

TRS-10008: Dispatcher failed to prepare SQL Statement. {0}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10009: Error creating DispatcherRuntimeInfo MBean. {0}
Cause: Open MBean metadata information cannot be constructed.
Action: Check MBean validity constraints.

Level: 1

Type: ERROR

Impact: Data

TRS-10010: Data source name: {0} cannot be resolved. Dispatcher thread will not start
Cause: Cannot resolve DataSource name
Action: Check DataSource name

Level: 1

Type: ERROR

Impact: Configuration

TRS-10011: {0} - error registering. {1}
Cause: MBean might already exist, or other reasons
Action: Ignore if MBean already exists. Otherwise consult administrator.

Level: 1

Type: ERROR

Impact: Data

TRS-10012: {0} - error querying number of jobs. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10013: {0} - error closing resultset. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10014: {0} - error closing statement. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10015: {0} - error querying replay items. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10016: {0} - error querying replay users. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10017: {0} - error querying replay types. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10018: DispatcherRuntimeInfo - error creating composite item. {0}
Cause: Open MBean related OpenDataException
Action: Consult administrator

Level: 1

Type: ERROR

Impact: Data

TRS-10019: DispatcherRuntimeInfo - error creating composite job. {0}
Cause: Open MBean related OpenDataException
Action: Consult administrator

Level: 1

Type: ERROR

Impact: Data

TRS-10020: {0} - error inserting replay type. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10021: {0} - error updating replay type. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10022: {0} - error removing replay items. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10023: {0} - error removing replay jobs. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10024: {0} - error removing replay users. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10025: {0} - error in database connection operations: commit, rollback or setAutoCommit. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10026: {0} - error loading settings. {1}
Cause: Error related to preference node
Action: Consult administrator

Level: 1

Type: ERROR

Impact: Data

TRS-10027: {0} - Cannot resolve DataSource Name {1}.
Cause: Cannot resolve DataSource
Action: Check DataSource name

Level: 1

Type: ERROR

Impact: Configuration

TRS-10028: {0} - DataSource name is null
Cause: DataSource name is null
Action: Check DataSource name in MBean or web.xml

Level: 1

Type: ERROR

Impact: Configuration

TRS-10029: {0} - error inserting replay items. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10030: {0} - Cannot find keystore password from Credential Store.
Cause: Cannot find keystore password
Action: Consult administrator

Level: 1

Type: ERROR

Impact: Security

TRS-10031: TRSConnectionMgr: fail to get database connection. {0}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10032: Cannot access Credential Store.
Cause: Credential store is not existing
Action: Consult administrator

Level: 1

Type: ERROR

Impact: Security

TRS-10033: Fail to get private key.
Cause: cannot get private key
Action: Check keystore, keystore password, certificate alias.

Level: 1

Type: ERROR

Impact: Security

TRS-10034: Client {0}, Replay item #{1}: Cannot update item status to {2}. {3}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10035: Client {0}, Replay item #{1}: Dependency not met. Parent item #{2} status is {3}.
Cause: Parent item status is not DONE
Action: Check parent item status

Level: 1

Type: ERROR

Impact: Data

TRS-10036: Client {0}, Replay item #{1}: Invalid Dependency #{2}.
Cause: DEPENDENCY value is not valid
Action: Check DEPENDENCY column for this item in table

Level: 1

Type: ERROR

Impact: Data

TRS-10037: Client {0}, Replay item #{1}: Fail to parse parameter. {2}
Cause: Cannot parse xml parameter
Action: Check PARAMS column for this item in table

Level: 1

Type: ERROR

Impact: Data

TRS-10038: Client {0}, Replay item #{1}: Error in retrieving password. {2}
Cause: Cannot get user's password
Action: Check security configuration

Level: 1

Type: ERROR

Impact: Security

TRS-10039: Client {0}, Replay item #{1}: Cannot find replay type class. {2}
Cause: Replay type class is missing
Action: Check to make sure the class library is available

Level: 1

Type: ERROR

Impact: Data

TRS-10040: Client {0}, Replay item #{1}: Cannot instantiate replay type class. {2}
Cause: Replay type class cannot be instantiated
Action: Class might be an interface or abstract

Level: 1

Type: ERROR

Impact: Data

TRS-10041: Client {0}, Replay item #{1}: Cannot find method with the right signature. {2}
Cause: No method available with the specified signature
Action: Check parameter provided in REPLAY_ITEM table

Level: 1

Type: ERROR

Impact: Data

TRS-10042: Client {0}, Replay item #{1}: Invocation access failure. {2}
Cause: Replay type method cannot be invoked
Action: The method does not have access to the definition of the specified class, field, method or constructor

Level: 1

Type: ERROR

Impact: Data

TRS-10043: Client {0}, Replay item #{1}, Calling Method = {2}, Class = {3}, Parameters = {4}: Invocation target failure. {5}
Cause: Replay type class cannot be invoked
Action: The invoked method throws an exception

Level: 1

Type: ERROR

Impact: Data

TRS-10044: Client {0}, Replay item #{1}: Unexpected exception. {2}
Cause: not known
Action: Check the error stack

Level: 1

Type: ERROR

Impact: Data

TRS-10045: Client {0}, Replay item #{1}: Unexpected error. {2}
Cause: not known
Action: Check the error stack

Level: 1

Type: ERROR

Impact: Data

TRS-10046: Query pending replay items for client {0} failed. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10047: Job #{0} for client {1} caught unexpected exception - {2}
Cause: The job is possibly determined dead by dispatcher or it has encountered other errors.
Action: Check the error stack

Level: 1

Type: ERROR

Impact: Data

TRS-10048: Cannot update job status to {0} for job id {1}.
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10049: Public key encryption is not set up properly. The feature is disabled.
Cause: Encryption configuration is not set up properly.
Action: Check public key encryption setup.

Level: 1

Type: ERROR

Impact: Security

TRS-10050: Default schema has not been set for user {0}, job {1}.
Cause: no default schema
Action: Set default schema in MBean

Level: 1

Type: ERROR

Impact: Configuration

TRS-10051: Caught RejectedExecutionException for user {0}, job {1}.
Cause: The job cannot be accepted for execution.
Action: Check thread pool

Level: 1

Type: ERROR

Impact: Configuration

TRS-10052: Thread pool is shut down for user {0}, job {1}.
Cause: Thread pool is shut down.
Action: Restart application.

Level: 1

Type: ERROR

Impact: Threads

TRS-10053: Missing ResourceBundle: {0}.
Cause: ResourceBundle is missing
Action: Check if resourcebundle is available

Level: 1

Type: ERROR

Impact: Data

TRS-10054: Client {0}, Replay item #{1}: Error processing the item.
Cause: Exception happened during processing this item
Action: Check log for errors logged before

Level: 1

Type: ERROR

Impact: Data

TRS-10055: Query outstanding replay items for client {0} failed. {1}
Cause: SQLException
Action: Check database

Level: 1

Type: ERROR

Impact: Data

TRS-10056: Worker servlet detects job {0} for client {1} has unexpected status. The job is not executed.
Cause: The job is determined dead by dispatcher, so it is not executed.
Action: Adjust failure recovery timeout if this error happens very frequently.

Level: 1

Type: ERROR

Impact: Data

TRS-10057: {0}: Failed to enable auto archive of replay jobs and replay items. {1}
Cause: IllegalArgumentException
Action: Check auto archive attributes

Level: 1

Type: ERROR

Impact: Data

TRS-10058: {0}: Failed to disable auto archive of replay jobs and replay items. {1}
Cause: IllegalArgumentException
Action: Make sure auto archive was previously enabled

Level: 1

Type: ERROR

Impact: Data

TRS-10059: Failed to create archive file {0}. {1}
Cause: Exception happened during creation of archive file
Action: Check database and make sure disk is not full

Level: 1

Type: ERROR

Impact: Data

TRS-10060: Failed to get value of attribute {0}.
Cause: Failed to get MBean attribute value
Action: Make sure attribute name is correct

Level: 1

Type: ERROR

Impact: Data

TRS-10061: Failed to set attribute {0} to {1}.
Cause: Failed to set MBean attribute value
Action: Make sure attribute name and value are correct

Level: 1

Type: ERROR

Impact: Data

TRS-10062: Database operation failed after retrying. Number of retries is {0}.
Cause: Database failure
Action: Check database.

Level: 1

Type: ERROR

Impact: Data

TRS-10063: Exception caught. Exiting Dispatcher thread.
Cause: Application is stopped or database failure.
Action: If it is database failure, check database.

Level: 1

Type: ERROR

Impact: Other

TRS-10064: Job Timeout triggered for client {0} for job {1} with status {2}. Updated time {3}, Timeout Value {4}
Cause: The job has been in the present state for more than the timeout value.
Action: Adjust failure recovery timeout if this error happens very frequently.

Level: 1

Type: ERROR

Impact: Data

TRS-10065: Failed to recover job {0} for client {1}
Cause: Database error may have occurred while updating job status to error.
Action: Check database connections.

Level: 1

Type: ERROR

Impact: Data

TRS-10066: Failed to query for the last processed item for client {0} and job {1}
Cause: Database error may have occurred while querying for replay items.
Action: Check database connections.

Level: 1

Type: ERROR

Impact: Data

TRS-10067: No items have been updated for client {0}
Cause: The item has been in the present state for more than the timeout value.
Action: Adjust item processing timeout if this error happens very frequently.

Level: 1

Type: ERROR

Impact: Data

TRS-10068: Failed to recover replay item for client {0} job {1}
Cause: Database error may have occurred while updating replay item status.
Action: Check database connections.

Level: 1

Type: ERROR

Impact: Data

TRS-10069: Received HTTP error code {0} for request {1}
Cause: Some error has occurred in the TxnReplayer component.
Action: Check log for errors logged before.

Level: 1

Type: ERROR

Impact: Data

TRS-10070: Cannot persist settings change for key: {0}, value: {1}
Cause: Some error has occurred in Java preference node persistent storage.
Action: Check default Java preference node storage location for your system.

Level: 1

Type: ERROR

Impact: Data

TRS-10071: Client {0}, Replay item #{1}: Custom Java class {2} cannot be found
Cause: Custom Java class is missing
Action: Check to make sure the custom Java class library is available

Level: 1

Type: ERROR

Impact: Data

TRS-10072: Client {0}, Replay item #{1}: Invalid parameter value {2} for the {3} of type {4} has been detected
Cause: Parameter value is not valid
Action: Check PARAMS column for this item in table

Level: 1

Type: ERROR

Impact: Data

TRS-10073: Client {0}, Replay item #{1}: Invalid parameter value for the {2} of type {3} has been detected. {4}
Cause: Parameter value is not valid
Action: Check PARAMS column for this item in table

Level: 1

Type: ERROR

Impact: Data

TRS-10074: Client {0}, Replay item #{1}: The value {2} of type char is empty
Cause: Parameter value is not valid
Action: Check PARAMS column for this item in table

Level: 1

Type: ERROR

Impact: Data

TRS-10075: Client {0}, Replay item #{1}: Invalid parameter value {2} {3} of type boolean has been detected
Cause: Parameter value is not valid
Action: Check PARAMS column for this item in table

Level: 1

Type: ERROR

Impact: Data

TRS-10076: Client {0}, Replay item #{1}: NULL is not a valid parameter value for the {2} of type {3}
Cause: Parameter value is not valid
Action: Check PARAMS column for this item in table

Level: 1

Type: ERROR

Impact: Data

TRS-10077: Cannot get Response from {0}. Replay item cannot be processed. {1}
Cause: TxnReplayer might not be running
Action: Check network. Make sure TxnReplayer is running

Level: 1

Type: ERROR

Impact: Network

TRS-10078: Client {0}, Replay item #{1}: the replay type has an invalid PASSWORD_TYPE value {2}.
Cause: Invalid PASSWORD_TYPE in REPLAY_TYPE table
Action: Provide valid value for the PASSWORD_TYPE column of the corresponding replay type in the REPLAY_TYPE table

Level: 1

Type: ERROR

Impact: Data

TRS-10079: Client {0}, Replay Item {1}: PARAMS column in REPLAY_ITEM table cannot be null or empty.
Cause: The PARAMS column in REPLAY_ITEM table is null or empty
Action: The PARAMS should have a value

Level: 1

Type: ERROR

Impact: Data

TRS-10080: TRS cannot publish the business event.
Cause: Client {0}, Item {1}: The event publication failed
Action: Check the following: (1) check the configuration (for example datasource) for event publication; (2) check the event payload; (3) check the DOM parser specified

Level: 1

Type: ERROR

Impact: Data

TRS-10081: Cannot parse property {0} for Replay type {1}. The property will be ignored.
Cause: The TYPE_PROPERTIES value for the replay type is in wrong format.
Action: Verify the value is a single string with a sequence of name value pairs, for example, "name1=value1;name2=value2;name3=value3;..."

Level: 1

Type: ERROR

Impact: Data

TRS-10082: Client {0}, Replay item #{1}: Application Module Configuration should not be empty for the replay type.
Cause: The ADF_CONFIG_NAME value for the replay type is empty.
Action: Provide valid value for ADF_CONFIG_NAME column in REPLAY_TYPE table for the replay type.

Level: 1

Type: ERROR

Impact: Data

TRS-10083: Client {0}, Replay item #{1}: Servlet URL should not be empty for the replay type.
Cause: The ReplayServletURL value for the replay type is empty.
Action: Provide valid ReplayServletURL value in TYPE_PROPERTIES column in REPLAY_TYPE table for the replay type.

Level: 1

Type: ERROR

Impact: Data

TRS-10084: Client {0}, Replay item #{1}: Cannot authenticate the user.
Cause: The username and password provided in replay item cannot be authenticated.
Action: Check the username and password for the replay item.

Level: 1

Type: ERROR

Impact: Data

TRS-10085: Client {0}, Replay item #{1}: Received error response from ReplayServlet with HTTP status code {2}. Detailed message: {3}
Cause: The server encountered error when processing the request.
Action: Check the log for details.

Level: 1

Type: ERROR

Impact: Data

TRS-10086: Client {0}, Replay item #{1}: Cannot post to ReplayServlet due to transport error.
Cause: Cannot post to the ReplayServlet due to transport/network problems.
Action: Check the network or increase the timeout.

Level: 1

Type: ERROR

Impact: Data

TRS-10087: Client {0}, Replay item #{1}: Cannot post to ReplayServlet due to protocol violation.
Cause: There may be a mismatch between client and server in interpreting the HTTP specification.
Action: Report the bug.

Level: 1

Type: ERROR

Impact: Data

TRS-10088: Authentication failed because it cannot post to ReplayServlet due to transport error.
Cause: Cannot post to the ReplayServlet due to transport/network problems.
Action: Check the network or increase the timeout.

Level: 1

Type: ERROR

Impact: Data

TRS-10089: Authentication failed because it cannot post to ReplayServlet due to protocol violation.
Cause: There may be a mismatch between client and server in interpreting the HTTP specification.
Action: Report the bug.

Level: 1

Type: ERROR

Impact: Data

TRS-10090: Failed to validate credential for user {0} for replay type {1}.
Cause: Incorrect username or password.
Action: Check whether username or password is correctly set up for the replay type.

Level: 1

Type: ERROR

Impact: Data

TRS-19000: Entity Object {0} with key {1} not found.
Cause: The entity object row is not found in the database.
Action: Please check if the transaction needs to be changed and resubmitted.

Level: 1

Type: ERROR

Impact: Data

TRS-19001: Cannot find attribute {0} in Entity Object {1}.
Cause: The definition of attribute is not found in the entity object.
Action: Please make sure that the mobile entity object and server entity object have consistent attribute definitions.

Level: 1

Type: ERROR

Impact: Data

TRS-19002: Entity Object {0} with key {1} has an update conflict on attribute {2}. Current server-side value is ({3}), client-side old value is ({4}) and new value is ({5}).
Cause: The server value is different from the client's old value. Some other transaction(s) might have updated the server value since client's last synchronization.
Action: Please check if the transaction needs to be changed and resubmitted.

Level: 1

Type: ERROR

Impact: Data

TRS-20000: TRSConnectionMgr: invalid Database Retries is defined in MBeans. It is treated as no database retry.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Configuration

TRS-20001: Client {0}, Replay item #{1}: Plain user password is provided in REPLAY_ITEM table, which is not secure.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Security

TRS-20002: Client {0}, Replay item #{1}: The value {2} {3} of type char is longer than 1 character. Ignoring the rest of the characters.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Data

TRS-20003: {0} Preferences has invalid values. Reset using web.xml values.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Configuration

TRS-20004: {0} - error unregistering. {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Configuration

TRS-20005: {0} - cannot resolve backup DataSource name {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Configuration

TRS-20006: {0} failed to close statement. {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Data

TRS-20007: TRSConnectionMgr: failed to return connection to the pool. {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Data

TRS-20008: The system property {0} has value ({1}), which is different from the expected value ({2}).
Cause: The Java VM does not have the system property needed to support full features of TRS.
Action: Set the property or check documentation on its impact.

Level: 1

Type: WARNING

Impact: Configuration

TRS-20009: {0}: Failed to save archive attributes to preference node. {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Data

TRS-20010: {0}: Failed to remove archive attributes from preference node. {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Data

TRS-20011: TRSConnectionMgr is retrying to get connection. Number of times that TRSConnectionMgr retried:{0}
Cause: Database failure.
Action: Check database.

Level: 1

Type: WARNING

Impact: Configuration

TRS-20012: TRSDBExecutor is retrying the database operation. Number of times that TRSDBExecutor retried:{0}
Cause: Database failure.
Action: Check database.

Level: 1

Type: WARNING

Impact: Configuration

TRS-20013: A Replay Item for client {0} has been updated to status "ADMIN_REVIEW".
Cause: TxnReplayer failed while processing replay items.
Action: Adjust failure recovery timeout if this error happens very frequently.

Level: 1

Type: WARNING

Impact: Data

TRS-20014: {0} jobs to be submitted, but the expected number is {1} jobs.
Cause: Job query failed to pick up all new jobs.
Action: Increase dispatcher cycle time if this warning happens very frequently.

Level: 1

Type: WARNING

Impact: Data

TRS-20015: Client {0}, Replay item #{1}: USER_PASSWORD column is ignored for "CSF" password type.
Cause: User password is retrieved from credential store for replay types with "CSF" password type.
Action: Remove the value in USER_PASSWORD column in REPLAY_ITEM table for replay items with "CSF" password type.

Level: 1

Type: WARNING

Impact: Data

TRS-20016: {0} - Cannot access the MBean Server through JNDI: {1}. {2}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Configuration

TRS-20017: Test certificate is used for public key encryption.
Cause: Test certificate was configured as the default certificate for development purpose only.
Action: Use a secure certificate in a production environment.

Level: 1

Type: WARNING

Impact: Configuration

TRS-20018: {0}: Cannot close SQL result set. {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-20019: {0}: Cannot close SQL statement. {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-20020: {0}: Cannot close File Writer. {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30000: TRSConnectionMgr: using backup DataSource
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30001: Changing TxnReplayer URL from {0} to {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30002: Changing Dispatcher loop delay from {0} to {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30003: DispatcherListener: Starting Dispatcher thread.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Threads

TRS-30004: DispatcherListener: Stopping Dispatcher thread.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Threads

TRS-30005: The keystore provider is {0}. The keystore URL is {1}. The keystore type is {2}. The certificate alias is {3}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Security

TRS-30006: Client {0}, Replay item #{1}: Begin processing the item.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30007: Client {0}, Replay item #{1}: Successfully processed the item.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30008: Client {0}, Replay item #{1}: Checking replay item dependency.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30009: Client {0}, Replay item #{1}: Calling Method={2}, Class={3}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30010: Client {0}, Replay item #{1}: Invoking method {2} of Class {3} succeeded.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30011: Client {0}, Replay item #{1}: Use custom XSD {2}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30012: Client {0}, Replay item #{1}: Use custom XSL {2}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30013: Public key encryption is disabled.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Security

TRS-30014: {0}: Inserted item {1} successfully.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30015: {0}: Enabling auto archive of replay jobs and replay items
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30016: Auto archive is enabled. Archive Time is {0}. Archive Interval is {1}. Archive Age is {2}. Archive Path is {3}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30017: {0}: Successfully removed {1} replay items
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30018: {0}: Successfully removed {1} replay jobs
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30019: Removing replay jobs older than {0} and with job status DONE or ERROR
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30020: Removing replay items older than {0} and with any status but PENDING, PROCESSING or ADMIN_REVIEW
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30021: Successfully created archive file {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30022: Recovering job {0} for client {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30023: Recovering replay items for client {0} and job {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30024: Persist setting changes for key: {0}, value: {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30025: {0}: Successfully removed {1} lone replay items
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30026: {0}: Successfully removed {1} parent/child replay items
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30027: {0}: Successfully removed {1} replay items in total
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30028: Successfully disabled auto archive of replay jobs and replay items
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30029: Publish business event
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30030: Successful credential validation for user {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Data