era.ors.2.2.0.source-code.ors_history_messages.properties Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of ors Show documentation

The newest version!

# Author: [email protected]
# Since: 1.0.0
# Version: $Id: ors_history_messages.properties 16154 2012-07-14 16:34:05Z colin $
#
# $License$

# This MUST be encoded in ISO-8859-1. To supply characters that are
# not supported by this encoding, use unicode escapes (\uxxxx).
#
# You may also create a separate file with a native encoding, and then
# use the 'native2ascii' tool of the Java Development Kit to convert
# that file into a this message file in ISO-8859-1. The same tool can
# do the reverse conversion using the '-reverse' command-line option.

log_root_id_not_found.msg=Unable to find an execution report record with order ID ''{1}'' when processing an execution report with order ID ''{0}'' and original order ID ''{1}''. This means that we missed execution report(s) for the original order(s) in this chain of orders. The system will be using ''{0}'' as the root order ID for this chain of orders.
error_reconstitute_fix_msg.msg=Unexpected error reconstituting report from the FIX Message ''{0}''. Contact product support.
rhs_cannot_create_queue.msg=Cannot create JMS queue for asynchronous report saving. Contact product support.
rhs_no_more_ids.msg=No more IDs are available. Contact product support.
rhs_enqueued_reply.msg=Enqueued reply ''{0}''
rhs_dequeued_reply.msg=Dequeued reply ''{0}''
rhs_persisted_reply.msg=Persisted reply ''{0}''
rhs_persist_error.msg=Unable to persist the report to the database and assign it an ID. This will result in system not having complete data on reports. This is a critical error. It is recommended that you stop the system, look at the underlying error for more details, fix it and then start using the system again. You may also want to manually add the report which could not be saved, before you restart. The report which could not be saved is ''{0}''