Copyright © TIBCO Software Inc. All Rights Reserved

> Error and Status Messages
> Category
> Admin command failed
> Description
> An admin tool or program using the admin API attempted an operation that failed for the given reason.
> Resolution
> The admin tool or admin API provides the failure reason. The user of the tool or API should examine the error and correct the syntax, parameter or configuration that is causing the failure.
> Errors
> %s: create %s failed: conflicting zone: existing consumer has a different zone
> %s: create %s failed: detected duplicate durable subscription [%s] for topic [%s].
> %s: create %s failed: illegal to use wildcard %s [%s].
> %s: create %s failed: invalid %s [%s].
> %s: create %s failed: invalid session id=%d.
> %s: create %s failed: invalid syntax of %s [%s].
> %s: create %s failed: invalid temporary %s [%s].
> %s: create %s failed: not allowed to create dynamic %s [%s].
> Invalid consumer in recover one msg request.
> Invalid sequence number in recover one msg request.

> Category
> A durable consumer was found in the store file for a route that does not exist
> Description
> On server startup a durable consumer was found in the store file for a route that is not listed in the routes.conf file. This happens if the routes.conf file is manually edited.
> Resolution
> Make routing changes via administration tools.
> Errors
> Discarding durable '%s' for route '%s' because the route does not exist.

> Category
> Backup server '%s' disconnected
> Description
> Lost connection with the backup fault-tolerant server.
> Resolution
> Determine if the backup server is running. If it is running, check for a network partition.
> Errors
> Backup server '%s' disconnected.

> Category
> Bad or missing value for command line parameter
> Description
> An invalid value was supplied for a command line parameter.
> Resolution
> Change the value of the named parameter to an acceptable value; for information about tibemsd command line parameters, see EMS documentation.
> Errors
> '%s' requires an integer argument.
> '%s' requires a positive integer argument.
> '%s' requires a string argument.

> Category
> Basic initialization failed
> Description
> tibemsd was unable to start.
> Resolution
> Correct the configuration or startup parameters and restart.
> Errors
> Unable to add admin user into admin group: error=(%d) %s
> Fault tolerant activation has to be greater than 2x heartbeat
> Server heartbeat client should be non-zero and no more than a third of the client timeout server connection
> Server heartbeat server should be non-zero and no more than a third of the server timeout server connection
> Client heartbeat server should be non-zero and no more than a third of the server timeout client connection
> Fault Tolerant configuration error, can't create loop.
> Fault tolerant connection failed, fault tolerant mode not supported on '%s'.
> Fault tolerant heartbeat has to be greater than 0
> Initialization failed due to errors in configuration.
> Initialization failed due to errors in SSL.
> Initialization failed due to errors with transports.
> Initialization failed. Exiting.
> Initialization has failed. Exiting.
> Initialization of thread pool failed (%s). Exiting.
> Startup aborted.
> Server failed to read configuration.
> Initialization failed: storage for '%s' not found.
> Failure initializing storage thread: %s.
> Initialization failed due to errors with multicast.
> Configuration error: dbstore_driver_name for store [%s] cannot be empty
> Configuration error: dbstore_driver_url for store [%s] cannot be empty
> Configuration error: dbstore_driver_dialect for store [%s] cannot be empty
> Configuration error: dbstore_driver_username for store [%s] must be specified
> Configuration error: dbstore_driver_password for store [%s] must be specified
> Error Loading JVM: %s
> Unknown Error Loading JVM
> Trying JVM location: %s
> Error Loading JVM: %s
> Unknown Error Loading JVM
> $sys.meta store's type must be 'file' or 'dbstore'.

> Category
> Commit failed due to prior failure or after fault-tolerant switch
> Description
> A warning message indicating that the commit of a client application's transaction failed either because there were earlier errors when processing this transaction or because the transaction was started on the primary server prior to a fault-tolerant failover.
> Resolution
> The client application should retry the transaction.
> Errors
> Commit failed due to prior failure or after fault-tolerant switch.

> Category
> Compaction failed
> Description
> Compaction of the store file failed.
> Resolution
> The most likely cause of this error is running out of memory. Shut down tibemsd and see remedies for Out of memory.
> Errors
> Compaction failed on file '%s': %d (%s). Please shutdown and restart tibemsd.
> Compaction failed on file '%s': %d (%s).
> Initialization of auto-compact feature failed for queue '%s' (store '%s') due to an out of memory condition. Feature is disabled.
> Auto-compaction of queue '%s' (store '%s') failed: %d (%s).

> Category
> Configured durable differs from stored one
> Description
> The durables configuration file specifies a durable with a given name and client identifier with attributes that are different from the identically named durable found in the meta.db file.
> Resolution
> Correct the durables configuration file to match the durable defined in the meta.db file or administratively delete the durable and re-define it.
> Errors
> Configured durable '%s' differs from durable in storage, storage version used.

> Category
> Create of global routed topic failed: not allowed to create dynamic topic
> Description
> A server received an interest notification from another server that does not match the allowed topics in its configuration.
> Resolution
> This only is printed when the trace includes ROUTE_DEBUG. If the server's topic definitions are as expected, this statement can be ignored or remove the ROUTE_DEBUG trace specification to prevent printing.
> Errors
> Create of global routed topic failed: not allowed to create dynamic topic [%s].

> Category
> Create of routed queue failed: not allowed to create dynamic queue
> Description
> A warning indicating that a tibemsd with a route to this daemon has a queue configured to be global but this daemon does not permit the creation of that queue dynamically.
> Resolution
> Add the specified queue or a pattern that includes it to this daemon if you want the queue to be accessible from this daemon, otherwise the warning can be ignored.
> Errors
> Create of routed queue failed: not allowed to create dynamic queue [%s].

> Category
> Database record damaged
> Description
> An error occurred reading one of the tibemsd store files.
> Resolution
> Send details of the error and the situation in which it occurred to TIBCO Support.
> Errors
> Server failed to recover state.

> Category
> Authentication error
> Description
> The EMS server failed to authenticate the user or password.
> Resolution
> Ensure the user is defined to EMS by one of the methods allowed by the user_auth parameter in the main configuration file. The user is either specified by the application or in the SSL certificate. If the user is defined, reset the password and try again.
> Errors
> Unable to initialize connection, SSL username error.
> LDAP authentication failed for user '%s', status = %d
> LDAP authentication failed for user '%s', no password provided

> Category
> Duplicate message detected
> Description
> Warning generated when tibemsd receives a message with a message id that matches another message's message id.
> Resolution
> Only seen when message id tracking is enabled.
> Errors
> Detected duplicate %s message, messageID='%s'

> Category
> Error in configuration file
> Description
> The server encountered an invalid configuration statement in the specified configuration file on the specified line.
> Resolution
> Examine the appropriate configuration file and correct the syntax error.
> Errors
> Configuration warning: file=%s, line=%d: route '%s' does not have a user configured for authorization.
> SSL Configuration error: file=%s, line=%d: invalid certificate file name, unknown extension or invalid encoding specification
> Configuration error: file=%s, line=%d: illegal to specify %s for routed queue
> Configuration error: file=%s, line=%d: bad destination specification: %s
> Configuration warning: file=%s, line=%d: illegal to specify prefetch=none for global or routed queue. Prefetch reset to default.
> Configuration warning: file=%s, line=%d: illegal to specify prefetch=none for topic. Prefetch reset to default.
> Configuration error: file=%s, line=%d: ignored alias '%s' for %s '%s' because such alias already exists
> Configuration error: The specified file '%s' is empty or does not exist
> Configuration error: file=%s, line=%d: both tibrv_export and tibrvcm_export are specified, ignoring tibrv_export
> Configuration error: file=%s, line=%d: ignoring transport '%s' in %s list, transport not found
> Configuration error: file=%s, line=%d: multiple bridge entries for the same destination '%s' are not allowed.
> Configuration error: file=%s, line=%d: Ignoring durable, name cannot start with $sys.route, use route property instead.
> Configuration error: file=%s, line=%d: Rendezvous transport not specified for Rendezvous CM transport '%s'
> Configuration error: file=%s, line=%d: ignoring invalid max connections in the line, reset to unlimited
> Configuration error: file=%s, line=%d: ignoring invalid max_client_msg_size in the line, reset to unlimited
> Configuration error: file=%s, line=%d: value of %s out of range, reset to default
> Configuration error: file=%s, line=%d: unable to create %s '%s': invalid destination name, invalid parameters or out of memory
> Configuration error: file=%s, line=%d: value of db_pool_size too big or less than allowed minimum, reset to default value of %d bytes
> Configuration error: file=%s, line=%d: Ignoring durable, route does not allow clientid, selector or nolocal.
> Configuration error: file=%s, line=%d: Route '%s' does not exist for configured durable.
> Configuration error: file=%s, line=%d: unable to process selector in route parameters, error=%s
> Configuration error: file=%s, line=%d: both tibrv_import and tibrvcm_import are specified, ignoring tibrv_import
> Configuration error: file=%s, line=%d: ignored route '%s' because route represents route to this server.
> Configuration error: file=%s, line=%d: ignoring invalid topic selector specifications in route parameters
> Configuration error: file=%s, line=%d: value of max_msg_memory less than allowed, reset to %dMB
> Configuration error: file=%s, line=%d: ignored alias '%s' for factory because such alias already exists
> Configuration error: file=%s, line=%d: specified value below allowable minimum. Resetting value store_minimum to 8M.
> Configuration error: file=%s, line=%d: specified value below allowable minimum. Resetting value store_minimum_sync to 8M.
> Configuration error: file=%s, line=%d: invalid certificate file name, unknown extension or invalid encoding specification
> Configuration error: file=%s, line=%d: ignored route '%s' because route has invalid zone information.
> Configuration error: file=%s, line=%d: ignored route '%s' because route with such name or URL already exists.
> Configuration error: file=%s, line=%d: value of msg_pool_size invalid or too big or less than allowed minimum of %d, reset to default value of %d
> SSL Configuration error: file=%s, line=%d: invalid private key file name, unknown extension or invalid encoding specification
> Configuration conflict: file=%s, line=%d: value of msg_pool_block_size already set at line=%d. Ignoring msg_pool_size.
> Configuration error: file=%s, line=%d: bridge has no targets, unable to process
> Configuration error: file=%s, line=%d: Illegal to specify routed queue as a bridge source
> Configuration error: file=%s, line=%d: client_trace error: %s
> Configuration error: file=%s, line=%d: %s
> Configuration error: file=%s, line=%d: duplicate specification of transport type
> Configuration error: file=%s, line=%d: duplicate value
> Configuration error: file=%s, line=%d: Ignoring durable, duplicate of earlier entry.
> Configuration error: file=%s, line=%d: Ignoring durable, name is invalid.
> Configuration error: file=%s, line=%d: Ignoring durable, name is missing or invalid.
> Configuration error: file=%s, line=%d: Ignoring durable, topic is invalid.
> Configuration error: file=%s, line=%d: Ignoring durable, topic is missing or invalid.
> Configuration error: file=%s, line=%d: error in the bridge description, unable to proceed.
> Configuration error: file=%s, line=%d: error in permissions
> Configuration error: file=%s, line=%d: error in the transport description, unable to proceed.
> Configuration error: file=%s, line=%d: errors in line, some options may have been ignored
> Error: unable to add bridge specified in file=%s, line=%d. Error=%s
> Configuration error: file=%s, line=%d: Unable to create destination defined by the bridge source
> Unable to create Rendezvous Certified transport '%s' because it references undefined Rendezvous transport '%s'
> Configuration error: file=%s, line=%d: failed to create ACL entry, reason=%s
> Unable to export message to SmartSockets. error=%s.
> Use fsync error: file=%s, line=%d: invalid property value
> Use fsync (min disk) error: file=%s, line=%d: invalid property value
> exit_on_nonretryable_disk_error: file=%s, line=%d: invalid boolean property value
> consumed_msg_hold_time: file=%s, line=%d: invalid property value
> active_route_connect_time: file=%s, line=%d: invalid property value
> Fault tolerant reread error: file=%s, line=%d: invalid property value
> Fault standby lock check error: file=%s, line=%d: invalid property value
> Configuration error: file=%s, line=%d: ignored unknown permission '%s'
> Configuration error: file=%s, line=%d: ignoring duplicate %s '%s' specified earlier
> Configuration error: file=%s, line=%d: ignoring duplicate transport name '%s' in %s list
> Configuration error: file=%s, line=%d: ignoring duplicate user
> Configuration error: file=%s, line=%d: ignoring errors in permission line
> Configuration error: file=%s, line=%d: ignoring invalid connect attempt count
> Configuration error: file=%s, line=%d: ignoring invalid connect attempt delay
> Configuration error: file=%s, line=%d: ignoring invalid connect attempt timeout
> Configuration error: file=%s, line=%d: ignoring invalid disk statistic period
> Configuration error: file=%s, line=%d: ignoring invalid entry syntax
> Configuration error: file=%s, line=%d: ignoring invalid factory load balancing metric
> Configuration error: file=%s, line=%d: ignoring invalid ft activation in the line
> Configuration error: file=%s, line=%d: ignoring invalid ft heartbeat in the line
> Configuration error: file=%s, line=%d: ignoring invalid ft reconnect timeout in the line
> Configuration error: file=%s, line=%d: ignoring invalid line
> Configuration error: file=%s, line=%d: ignoring invalid line in factory parameters
> Configuration error: file=%s, line=%d: ignoring invalid line in route parameters
> Configuration error: file=%s, line=%d: ignoring invalid line: invalid syntax in the line
> Configuration error: file=%s, line=%d: ignoring invalid reconnect attempt count
> Configuration error: file=%s, line=%d: ignoring invalid reconnect attempt delay
> Configuration error: file=%s, line=%d: ignoring invalid reconnect attempt timeout
> Configuration error: file=%s, line=%d: ignoring invalid value of %s
> Configuration error: file=%s, line=%d: ignoring invalid value in the line
> Configuration error: file=%s, line=%d: ignoring unknown property '%s'
> Configuration error: file=%s, line=%d: ignoring unrecognized property '%s'
> Configuration error: file=%s, line=%d: ignoring user out of group context
> Configuration error: file=%s, line=%d: illegal to use predefined name %s
> Configuration error: file=%s, line=%d: Invalid clientid value
> Configuration error: file=%s, line=%d: invalid value of db_pool_size, reset to default of %d bytes
> Configuration error: file=%s, line=%d: invalid line syntax or line out of order
> Configuration error: file=%s, line=%d: invalid value of max memory, reset to unlimited
> Configuration error: file=%s, line=%d: invalid value of max_msg_memory, reset to unlimited
> Configuration error: file=%s, line=%d: invalid property value
> Configuration error: file=%s, line=%d: invalid property value, reset to default.
> Configuration error: file=%s, line=%d: invalid password
> Configuration error: file=%s, line=%d: invalid value of reserve_memory, reset to zero
> Configuration error: file=%s, line=%d: invalid value of route_recover_interval, reset to default %d
> Configuration error: file=%s, line=%d: invalid value of route_recover_count, line ignored
> Configuration error: file=%s, line=%d: Invalid selector value
> Configuration error: file=%s, line=%d: invalid syntax of %s, unable to continue.
> Configuration error: file=%s, line=%d: invalid transport parameter '%s'
> Configuration error: file=%s, line=%d: invalid transport type '%s'
> Configuration error: file=%s, line=%d: invalid trace_client_host value
> Configuration error: file=%s, line=%d: invalid trace_millisecond value
> Configuration error: file=%s, line=%d: invalid value of %s, reset to unlimited
> Configuration error: file=%s, line=%d: invalid value, reset to no minimum.
> Configuration error: file=%s, line=%d: invalid value '%s'
> Configuration error: file=%s, line=%d: invalid value of '%s'
> Configuration error: file=%s, line=%d: invalid value of %s
> Configuration error: file=%s, line=%d: invalid value of %s, reset to 256MB
> Configuration error: file=%s, line=%d: invalid value of %s, reset to default
> Configuration error: file=%s, line=%d: line too long, ignoring it
> Configuration error: file=%s, line=%d: maximum number of listen interfaces reached.
> Configuration error: file=%s, line=%d: multiple principals specified, line ignored
> Configuration error: file=%s, line=%d: multiple targets specified, line ignored
> Configuration error: file=%s, line=%d: out of memory, unable to create Rendezvous transport
> Configuration error: file=%s, line=%d: no permissions found in acl entry
> Configuration error: file=%s, line=%d: no target found in acl entry
> Configuration error: file=%s, line=%d: %s '%s' not found
> Configuration error: No topic exists for configured durable '%s%s%s'.
> failed to create durable '%s', exception: %s.
> Configuration error: file=%s, line=%d: no valid user or group found in acl entry
> Configuration conflict: file=%s, line=%d: Overriding value of msg_pool_size already set at line=%d.
> Configuration warning: file=%s, line=%d: parameter '%s' is deprecated
> Configuration error: file=%s, line=%d: value of reserve_memory too small, reset to 16MB
> Configuration error: file=%s, line=%d: ignoring invalid line in route parameters: invalid zone type, too long
> Configuration error: file=%s, line=%d: ignoring invalid line in route parameters: zone name exceeding %d bytes
> Routing Configuration error: file=%s, line=%d: invalid property value
> Configuration warning: file=%s, line=%d: ignoring rvcmlistener, duplicate
> Configuration error: file=%s, line=%d: ignoring rvcmlistener, first token is invalid
> Configuration error: file=%s, line=%d: ignoring rvcmlistener, invalid destination
> Configuration error: file=%s, line=%d: ignoring rvcmlistener, second token is invalid
> Configuration error: file=%s, line=%d: ignoring rvcmlistener, third token is invalid
> Configuration error: file=%s, line=%d: ignoring rvcmlistener, wildcards are not permitted
> SmartSockets configuration directory name is too long. error=%s.
> SmartSockets file '%s' not found.
> SSL Configuration error: file=%s, line=%d: duplicate value
> SSL Configuration error: file=%s, line=%d: invalid value of DH key size.
> SSL Configuration error: file=%s, line=%d: invalid property value
> SSL Configuration error: file=%s, line=%d: invalid renegotiate size value
> SSL Configuration error: file=%s, line=%d: invalid renegotiate size value, minimum is %dKb
> SSL Configuration error: file=%s, line=%d: invalid renegotiate value, minimum is %d (in seconds)
> Configuration error: file=%s, line=%d: syntax error in the line, ignoring
> Configuration error: file=%s, line=%d: syntax errors in line, line ignored
> Topic '%s' not valid in configured durable '%s'.
> Configuration error: file=%s, line=%d: Unrecognized attribute
> Configuration error: file=%s, line=%d: user '%s' not found, ignoring
> Configuration error: file=%s, line=%d: value is invalid or less than minimum %d, reset to 0
> Configuration error: file=%s, line=%d: value less than allowed minimum, reset to 0
> Configuration error: file=%s, line=%d: value of %s less than allowed minimum of %dKB, reset to unlimited
> Configuration error: file=%s, line=%d: Invalid value or value does not fall between %d and %d
> Configuration error: Invalid line: file=%s, line=%d
> Configuration error: Missing store header: file=%s, line=%d
> Configuration error: Mixed mode configuration: file=%s, line=%d
> Configuration error: Invalid store parameter: file=%s, line=%d
> Configuration error: Store definition failed
> Configuration error: Unrecognized store type requested.
> Configuration error: Filename for store '%s' cannot be empty.
> Error occurred writing store definition into file.
> Configuration error: file=%s, line=%d: ignoring channel '%s' on topic '%s', channel does not exist
> Configuration error: file=%s, line=%d: ignoring channel '%s' on topic '%s', overlaps with channel '%s' on topic '%s'
> Configuration error: file=%s, line=%d: ignoring channel '%s', duplicate name
> Configuration error: file=%s, line=%d: ignoring channel '%s', address of '%s:%d' already defined
> Configuration error: file=%s, line=%d: channel '%s', %s
> Configuration error: file=%s, line=%d: channel '%s', no address specified.
> Configuration error: file=%s, line=%d: channel '%s', invalid address syntax: port not specified.
> Configuration error: file=%s, line=%d: channel '%s', invalid address: group must be in the range 224.0.0.0 to 239.255.255.255
> Configuration error: file=%s, line=%d: channel '%s', interface must address a valid multicast-capable network interface.
> Configuration error: file=%s, line=%d: channel '%s', invalid address: port must be in the range 1 to 65535
> Configuration error: file=%s, line=%d: channel '%s', ttl must be in the range 1 to 255
> Configuration error: file=%s, line=%d: channel '%s', priority must be in the range -5 to 5
> Configuration error: file=%s, line=%d: channel '%s', maxrate must be less than 512MB
> Configuration error: file=%s, line=%d: channel '%s', maxtime must be greater than 0
> Configuration error: file=%s, line=%d: cannot store messages in: %s
> Configuration error: file=%s, line=%d: cannot find store: %s
> Required store param 'type' not specified for store '%s'
> Invalid params at line %d in file '%s' for store '%s' when store type is 'file' %s
> Invalid params at line %d in file '%s' for store '%s' when store type is 'dbstore' %s
> Invalid params at line %d in file '%s' for store '%s' when store type is 'mstore' %s
> Store '%s' already defined
> Configuration error: Store with similar dbstore_driver_url exists, file=%s, line=%d
> Configuration error: duplicate file name %s for stores %s and %s
> Configuration warning: file=%s, line=%d: the discardAmount is too small for the selected RV Queue Limit Policy. It is recommended to have at least 10%% of the maxEvents
> Configuration error: file=%s, line=%d: the discardAmount is too big compared to the maxEvents value. Defaulting to TIBRVQUEUE_DISCARD_NONE policy
> Configuration error: file=%s, line=%d: maxEvents and discardAmount values must be strictly positive for an RV Queue Limit Policy other than TIBRVQUEUE_DISCARD_NONE. Defaulting to TIBRVQUEUE_DISCARD_NONE policy
> Configuration error: file=%s, line=%d: RV Queue Limit Policy '%s' unknown or not supported. Defaulting to TIBRVQUEUE_DISCARD_NONE policy
> Configuration error: file=%s, line=%d: Error parsing the RV Queue Limit Policy value '%s'. Defaulting to TIBRVQUEUE_DISCARD_NONE policy
> Configuration warning: file=%s, line=%d: The bridge's source destination '%s' is dynamic but has no parent. The bridge should either be removed or a static parent destination added

> Category
> Error writing commit request, errors already occurred in this transaction
> Description
> A client application's attempt to commit a transaction failed because the server encountered an error during an operation associated with the transaction.
> Resolution
> Examine previous error statements to determine the cause of the operation failure and correct that before attempting the transaction again.
> Errors
> Error writing commit request, errors already occurred in this transaction.

> Category
> Error writing configuration file
> Description
> tibemsd was unable to update one of its configuration files following a configuration change.
> Resolution
> Check that the user that started the tibemsd has permission to change the configuration files and that there is sufficient disk space on the device.
> Errors
> Error occurred saving acl information
> Error occurred saving bridges information
> Error occurred saving durables information
> Error occurred saving factories information
> Error occurred saving file '%s'
> Error occurred saving group information
> Error occurred saving %s information
> Error occurred saving main configuration file '%s'
> Error occurred saving routes information
> Error occurred saving tibrvcm information
> Error occurred while updating main configuration file '%s'. Configuration has not been saved.
> Error occurred writing bridges into file.
> Error occurred writing destination '%s' into file
> Error occurred writing factory into file.
> Error occurred writing group '%s' into file
> Error occurred writing into the file '%s'.
> Error occurred writing route into file.
> I/O error occurred saving bridge information
> I/O error occurred saving group information
> I/O error occurred saving route information
> I/O error occurred writing into file '%s'

> Category
> Error writing to store file
> Description
> tibemsd was unable to write data to one of its store files.
> Resolution
> Ensure that the directory containing the store files is mounted and accessible to the tibemsd, and that there is free space available on the device
> Errors
> Failed writing block data to '%s': %s
> Failed writing message to '%s': I/O error or out of disk space.
> Failed writing purge state for queue '%s': I/O error or out of disk space.
> Failed writing purge state for topic consumer: I/O error or out of disk space.
> Exception trying to create confirm record, %s.
> Exception trying to create message from store: %s
> Exception trying to create transaction record.
> Exception trying to create valid messages record, %s.
> Exception trying to export message to RV.
> Failed writing message to '%s': %s.
> Exception writing transaction commit record: %s.
> Exception writing transaction rollback record: %s.
> Exception writing transaction prepare record: %s.
> Failure deleting old version of transaction record: %s.
> Failed deleting '%s' record from %s: %s

> Category
> Failed to open TCP port
> Description
> tibemsd was unable to open the tcp port.
> Resolution
> Shutdown process that is using the port or change the value of the 'listen' parameter in the server's tibemsd.conf file to a port that is not in use.
> Errors
> Binding connection to TCP port %d failed:%d (%s).

> Category
> File access error
> Description
> tibemsd was unable to properly access the specified file.
> Resolution
> Check that the path name is correct and the directory exists, the user that started tibemsd has permission to read the specified directory and path, the file exists if it isn't one that the tibemsd can create, the file is not being used by another tibemsd or some other process.
> Errors
> Configuration file '%s' not found.
> Failed to create file '%s'
> failed to open file '%s'.
> failed to open log file '%s'.
> Failed to read message from store.
> Failed to rename file %s into %s: %s
> Unable to open metadata file '%s', error '%s'.
> Unable to open metadata file '%s', file may be locked.
> Unable to open store file '%s', error '%s'.
> Unable to open store file '%s', file may be locked.
> Unable to preallocate storage file '%s'.
> I/O error occurred reading from the file '%s'.
> Exiting on non-retryable disk error: %d
> Exception trying to read message from store.
> Error during file close of '%s' - %d.

> Category
> Internal error that should be status-driven
> Description
> The server detected an internal inconsistency.
> Resolution
> Send the error statement and a description of the environment to TIBCO Support.
> Errors
> **Error** unable to process message, error = %s
> Admin user not found during initialization
> Error bridging transacted data message, '%s'.
> Error processing xa commit request, %s. connID=% PRINTF_LLFMT d %s
> Error processing xa end - transaction marked ROLLBACKONLY, %s. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> Error processing xa prepare request, %s. connID=% PRINTF_LLFMT d %s
> Error processing xa rollback request, %s. connID=% PRINTF_LLFMT d %s
> Error decoding sequence data in xa rollback request. connID=% PRINTF_LLFMT d %s
> Error decoding sequence data in route ack response.
> Unable to create internal session
> Problem setting flow stall recover message on route queue:%s: %s
> Failed to handle connection initialization: %s.
> Problem trying to recover routed consumer for queue %s: setting recover message. Error: %s
> Failed to send the flow stall recover request: %s.
> Unable to handle transacted data message, '%s'.
> Unable to handoff connection init message: %s.
> Unable to initialize fault tolerant connection, remote server returned '%s'
> Unable to process producer message, failed to add sender name, error=%s.
> Unable to process sequence for message.
> Unable to send recover ack on flow stall: %s
> Handling of route flow stall recovery request from %s failed: unable to get message property %s: %s
> Handling of route flow stall recovery request failed: Unable to get message properties:%s
> Failed to send acknowledge to the stall recover request of server %s, will try later. Error: %s
> failed to send recover ack on stalled flow: invalid consumer
> unable to create recovered connection, status: %s
> Exception creating purge record.
> Exception creating zone.
> Exception creating zone: adding zone to state.
> Exception in startup, exiting.
> Exception preparing message for client send.
> Exception sending flow recover acknowledge
> Exception sending routing information to %s - %s
> Exception sending session init response
> Exception sending queue acknowledge response to %s: %s
> Exception trying to initialize connection.
> Exception trying to initialize connection, can't send response: %s
> Exception trying to initialize route.
> Exception trying to initialize route '%s' configured durables: %s
> Exception trying to process message, '%s'.
> Exception trying to process message from store.
> Failure queuing incoming message for processing: %s.
> Failure queuing message for removal from system: %s.
> Failure queuing message to add to dead queue: %s.
> Failure discarding topic overflow: %s.
> Failure processing system request.
> Failure processing transaction message.
> Failure bridging incoming message: %s.
> Failure verifying uniqueness of routed message: %s.
> Failure scheduling message hold release: %s.
> Exception adding message write context: %s.
> %s: Failure processing multicast request: %s
> %s: Failure sending multicast request response: %s
> %s: Failure processing multicast status: %s
> %s: Failure sending multicast status response: %s
> %s: Failure sending multicast configuration: %s
> Failure sending multicast message on channel '%s': %s
> Failure enqueuing multicast message on channel '%s': %s
> Failure starting multicast engine: %s
> Failure starting multicast channel '%s': %s
> Failure posting multicast channel '%s' wake event: %s
> Failed preparing message for writing: %s
> Failed discarding local transaction: %s
> Abandoning transaction record due to IO failure.
> Error sending acknowledgment to route '%s': %s
> Error processing acknowledgments from route '%s': %s

> Category
> Invalid connection
> Description
> Warning indicating that tibemsd was attempting to reestablish delivery of messages across a route to another tibemsd but was unable to find the connection for that route.
> Resolution
> Either reduce the tibemsd's memory requirement by consuming messages or removing messages from its queues, or increase the amount of memory available to the tibemsd by shutting down other processes on the machine or increasing the machine's memory.
> Errors
> Recovery flow stall for destination %s failed: invalid route connection

> Category
> Invalid destination
> Description
> An application is attempting to use a destination name that is not valid.
> Resolution
> Alter application code to use an acceptable destination name.
> Errors
> %s: create %s failed: Not permitted to use reserved queue [%s].
> %s: %s failed: illegal to use wildcard %s [%s].
> %s: %s failed: %s [%s] not configured.
> At least one bridge is referencing %s [%s] as a target. This destination does not exist and there is no parent that would allow its dynamic creation. The destination has been forcefully created. To avoid this, the bridge(s) referencing this target should be destroyed.
> Use of '$' destination prefix is not supported [%s %s].

> Category
> Invalid listen specification
> Description
> The server could not parse the listen parameter in the tibemsd.conf file
> Resolution
> Correct the listen parameter to match the form [protocol]://[url] as specified in the manual.
> Errors
> Invalid listen specification: '%s'.
> Invalid request to create temporary destination.

> Category
> Invalid session
> Description
> tibemsd received a request that referred to a session that doesn't currently exist.
> Resolution
> Send details of the error and the situation in which it occurred to TIBCO Support.
> Errors
> Cannot find session for ack
> Cannot find session for ack range
> %s: destroy %s failed: invalid session id=%d.
> Unable to destroy session, invalid session.
> Invalid session in commit request.
> Invalid session trying to update(%d) tx record.
> Invalid session in commit transaction record.
> Invalid session in recover request.
> Invalid session in rollback request.
> Invalid session in xa end request. connID=% PRINTF_LLFMT d
> Invalid session in xa start request. connID=% PRINTF_LLFMT d

> Category
> LDAP error - should always display LDAP error
> Description
> An attempt to authenticate a client's userid and password using the external LDAP server failed.
> Resolution
> Examine the error code printed by the messaging server and consult the manual for the external LDAP server.
> Errors
> Filter '%s' contains an illegal type substitution character, only %%s is allowed
> Filter '%s' contains too many occurrences of %%s, max allowed is: %d
> Filter '%s' too long, max length is %d characters
> Invalid search scope: %s
> LDAP Configuration error: file=%s, line=%d: invalid property value
> LDAP is not present
> LDAP search resulted %d hits.
> ldap_url_parse failed, returned: %d
> Lookup of group '%s' produced incorrect or no results
> Missing LDAP URL
> Missing %s parameter
> Zero entries returned from getting attributes for group '%s':
> Failed adding user '%s' into LDAP user cache

> Category
> LICENSE WARNING
> Description
> The server detected a violation of its license.
> Resolution
> This error only occurs with the evaluation version of the server or in an embedded form. To correct this error either replace your evaluation version with a production version or contact the vendor who supplied the embedded version.
> Errors
> License violation: %s.

> Category
> Missing configuration
> Description
> An essential attribute has not been configured.
> Resolution
> Change the tibemsd.conf file so that a value for the attribute is provided.
> Errors
> Configuration error with metadata database.
> Configuration error with storage databases.

> Category
> Missing transaction
> Description
> A client application attempted to change the state of a transaction that the tibemsd does not have in its list of current transactions.
> Resolution
> Check tibemsd trace logs to see if the transaction had been committed or rolled back by an administrator, if not then check the client code to see if it or its transaction manager are calling the transaction operations in the correct order.
> Errors
> Cannot find transaction referred to transaction record update(%d) request. connID=% PRINTF_LLFMT d %s
> Cannot find transaction referred to in xa commit request. connID=% PRINTF_LLFMT d %s
> Cannot find transaction referred to in xa prepare request. connID=% PRINTF_LLFMT d %s
> Cannot find transaction referred to in xa rollback request. connID=% PRINTF_LLFMT d %s
> Received prepare request for transaction already prepared. connID=% PRINTF_LLFMT d %s
> Cannot find transaction referred to in xa start (resume) request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> Cannot find transaction referred to in xa start (join) request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> Cannot find transaction referred to in xa end request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s

> Category
> Out of memory
> Description
> The server failed to allocate memory as it was attempting to perform an operation.
> Resolution
> Check how much memory the server process is using according to the operating system. Compare this with how much memory and swap space the host actually has. If there are sufficient memory and swap space, check the operating system limits on the server process to determine if this is the cause. If the limits are set to their maximum and this error occurs, reduce the load on this server by moving some topics and queues to another server.
> Errors
> %s trying to recreate persistent message.
> Error during routed queue configuration, can not create routed queue consumer
> Could not initialize monitor
> Error: out of memory processing admin request
> Error during route configuration, can not create routed queue consumer, err=%s
> Configuration error - duplicate group: file=%s, line=%d: ignoring line
> Unable to create admin group: out of memory during initialization
> Error: unable to create alias for %s '%s': no memory
> Error: unable to create alias: out of memory
> Unable to create import event for %s '%s' on transport '%s'
> Unable to create internal connection, error=(%d) %s
> Unable to create internal connection: out of memory during initialization
> Error: unable to create %s '%s': no memory
> Error: unable to create route while parsing file=%s, line=%d.
> Unable to create SmartSockets subscriber on transport '%s', %s '%s': out of memory
> Unable to create temporary destination, out of memory
> Failed to create reserve memory. Exiting.
> Failed writing message to '%s': No memory for operation.
> Unable to process message imported on transport '%s'.
> Fault Tolerant configuration, no memory!
> Fault Tolerant error, no memory.
> LDAP initialization failed.
> No memory.
> No memory authenticating user '%s'
> No memory authenticating via LDAP
> Out of memory while building admin response message
> Out of memory while building JNDI response message
> Out of memory creating global import event on transport '%s'
> Out of memory creating import event for %s '%s' on transport '%s'
> Out of memory creating SS transport %s
> No memory creating stalled flows in destination
> Out of memory during initialization
> Could not set replyto destination exporting SS message.
> Could not set destination exporting SS message.
> Could not get destination exporting SS message.
> Failed to initialize SS message fields exporting SS message.
> Out of memory exporting SS message.
> Out of memory: unable to process SS message type on export
> No memory for creating connection.
> No memory generating dynamic route durable.
> Out of memory importing SS message. error=%s.
> No memory in IO thread to create pool.
> Out of memory while parsing bridges file
> Out of memory while parsing factories file
> Out of memory while parsing routes file
> No memory performing routing operation.
> Out of memory processing %s on %s '%s'
> Out of memory processing administrative request
> Out of memory processing message tracing
> No memory processing purge record.
> No memory while processing route interest
> Out of memory processing transports
> Out of memory processing transports configuration
> Out of memory reading configuration.
> Out of memory restoring routed consumer
> Out of memory sending monitor message.
> No memory sending topic routing information.
> %s trying to add message to %s queue.
> No memory trying to add message to system.
> No memory trying to cleanup route.
> No memory to create ack record.
> No memory to create client connection
> No memory to create configured durable '%s%s%s'.
> No memory to create configured durables
> No memory to create confirm record.
> No memory to create connection.
> No memory to create consumer.
> No memory trying to create destination.
> No memory to create destination for consumer or browser.
> No memory trying to create global topic destination.
> No memory to create message from store.
> No memory to extract routing info from incoming message.
> No memory trying to create message producer.
> No memory to create producer.
> No memory trying to create queue browser.
> No memory trying to create response message.
> No memory to create routed consumer
> No memory to create routed queue consumers
> No memory trying to create routed queue destination.
> No memory trying to create routed tmp queue destination.
> No memory to create session.
> No memory trying to create tmp destination for consumer.
> No memory trying to create transaction.
> No memory to create valid messages record.
> No memory restoring valid sequence number info.
> No memory to create zone.
> No memory trying to export message to RV.
> No memory trying to export message to SS.
> No memory trying to import message from RV%s.
> No memory trying to import message from RVCM.
> No memory trying to import message from SS. error=%s.
> No memory trying to initialize connection.
> No memory trying to initialize route connection.
> No memory trying to parse configured durable.
> No memory trying to process data message.
> No memory trying to process queue message.
> No memory to process route interest
> No memory to process SSL renegotiation request.
> No memory trying to process system request.
> No memory trying to process topic consumer.
> No memory trying to process topic message.
> No memory trying to process xa end. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> No memory trying to read message from store.
> Route down while trying to recover routed consumer.
> No memory trying to recover routed consumer.
> No memory trying to recover one msg for routed consumer.
> No memory trying to recover route stall.
> No memory trying to recover route stall, will try again.
> No memory to restore messages.
> No memory to restore prepared transactions.
> No memory trying to retrieve for queue browser.
> No memory trying to send recover/rollback response.
> out of memory trying to send topic interest to routes
> No memory to set clientID for connection.
> No memory trying to setup queue route configuration
> No memory trying to setup route configuration
> No memory trying to setup topic route configuration
> Route recovery of destination %s on route from %s will fail: No memory
> Route recovery of destination %s on route from %s will fail: No memory to create timer
> Route recovery of destination %s on route from %s will fail: %s
> Failed to initialize OpenSSL environment: out of memory
> Out of memory queuing imported message for processing.
> Out of memory gathering consumers for incoming message.
> Out of memory scheduling message delete.
> Out of memory preparing to write message.
> Out of memory assembling list of message to store.
> Out of memory processing route consumer.
> Out of memory preparing message for writing.
> Out of memory creating connection thread list.
> Out of memory creating RV gateway thread list.
> Out of memory creating SmartSockets gateway thread list. error=%s.
> Out of memory delaying bridged flow control response.
> Out of memory preparing to delay flow control response.
> Out of memory delaying one flow control response.
> Out of memory delaying set of flow control responses.
> Out of memory trying to clear message hold.
> Out of memory trying to delete held message.
> Unable to update the valid messages record. Error code: %d - %s.
> No memory scheduling message delete completion, Error code: %d.
> No memory to build msg properties.
> No memory to create prop.
> No memory to set prop.
> No memory getting the list of delivered messages. The JMSXDeliveryCount property of some messages may no longer be accurate.
> No memory getting the list of delivered messages from session % PRINTF_LLFMT d. The JMSXDeliveryCount property of messages that were sent to this session may no longer be accurate.
> No memory getting the list of delivered messages during rollback of transaction with xid: %s. The JMSXDeliveryCount property of messages that were rolled-back may no longer be accurate.
> Out of memory discarding message.
> Out of memory advancing queue pending.
> Out of memory adding message to pending list.
> Out of memory returning message to pending list.
> Out of memory trying to re-queue after xa rollback.
> Out of memory finalizing restored queue: %s.
> Out of memory restoring queue flush state.
> Out of memory detaching message during queue purge.
> Out of memory removing message from queue.
> Out of memory retrieving message by correlation id.
> Out of memory scheduling cleanup of transaction ack: %s.
> Out of memory setting message all acked: %s.
> Out of memory cleaning up transaction: %s.
> Out of memory updating sent state on ack.
> Out of memory updating in-doubt state on ack.
> Out of memory removing message from system.
> Out of memory associating ack with data.
> Out of memory associating ack with transaction.
> Out of memory resetting mstore discard scan: %s.
> Out of memory recording modified topic.
> Out of memory re-queuing sent messages.

> Category
> Protocol error, incorrect XID in XA request
> Description
> The tibemsd received an XA End instruction from the third party Transaction Manager which referred to a different transaction from the one currently in use by the session.
> Resolution
> Report this to the your Transaction Manager vendor.
> Errors
> Incorrect xid in xa end (0x%x) request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s

> Category
> Protocol error, transaction in incorrect state
> Description
> A client application's attempt to start an XA transaction failed because the transaction already exists and is not in the correct state.
> Resolution
> This error is most likely caused by an external transaction manager that allowed two separate client applications to use the same XA transaction identifier (XID). Consult the manual for the transaction manager or report this to the transaction manager vendor.
> Errors
> Cannot process xa start for a session when another transaction is already active on that session. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> Cannot process xa start with TMNOFLAGS when the transaction is already active. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s

> Category
> Protocol message format error
> Description
> tibemsd received a message with either missing or incomplete data.
> Resolution
> Send details of the error and the situation in which it occurred to TIBCO Support.
> Errors
> Unable to confirm session, invalid request.
> Unable to create consumer, invalid destination.
> Unable to init session, invalid request.
> Unable to process msg for export. error=%s.
> Unable to recover consumer, invalid request.
> Unable to recover consumer, invalid session.
> Unable to recover one msg for consumer, invalid request.
> Unable to recover one msg for consumer, invalid sequence number.
> Unable to recover one msg for consumer, invalid session.
> Unable to serve the flow stall recover request from server %s, invalid request.
> Unable to start consumer, invalid consumer
> Unable to server the flow stall recover request from server %s, invalid consumer.
> Unable to unsubscribe consumer, invalid client request.
> %s: %s failed: illegal to use %s [%s] in standby mode.
> Invalid flag in xa end request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> Invalid flag in xa start request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> Invalid request to delete temporary destination: %s. connID=% PRINTF_LLFMT d
> Invalid request to delete temporary destination: not owner connection.
> Invalid xid in commit request.
> Invalid xid in commit transaction record.
> Invalid xid trying to update(%d) transaction record.
> Invalid xid in rollback request.
> Invalid xid in rollback transaction record.
> Invalid xid in xa commit request. connID=% PRINTF_LLFMT d
> Invalid xid in xa end request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d
> Invalid xid in xa prepare request. connID=% PRINTF_LLFMT d
> Invalid xid in xa rollback request. connID=% PRINTF_LLFMT d
> Invalid xid in xa start request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d
> Malformed routed message
> Problem decoding sequence data in confirm: %s.
> Problem decoding sequence data in rollback.
> Problem decoding sequence data in xa end. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> %s:%s queue browser failed: queue name is missing in request message
> Received admin request with replyTo not set
> Received JNDI request with replyTo not set.
> Received unexpected message type %d
> No destination in incoming data message.

> Category
> Protocol sequence error
> Description
> A non-embedded java client is attempting to connect to a tibemsd that is part of an embedded JMS environment.
> Resolution
> Reconfigure the client to connect to a fully licensed tibemsd.
> Errors
> Invalid client connect detected.
> No closure.

> Category
> Rejected attempt to connect via SSL to TCP port
> Description
> A client application attempted to connect to the server's TCP port using the SSL protocol.
> Resolution
> Change the client application's URL from ssl to tcp or change the server's listen parameter from tcp to ssl. To activate a change of the server listen parameter requires a restart of the server.
> Errors
> Rejected attempt to connect via SSL to TCP port

> Category
> Rejected attempt to connect via TCP to SSL port
> Description
> A client application attempted to connect to the server's SSL port using the TCP protocol.
> Resolution
> Change the client application's URL from tcp to ssl or change the server's listen parameter from ssl to tcp. To activate a change of the server listen parameter requires a restart of the server.
> Errors
> Rejected attempt to connect via TCP to SSL port

> Category
> rejected connect from route: invalid cycle in route
> Description
> The multi-hop route support of the server does not support configuring a cycle. However, it detected a configuration that would create a cycle.
> Resolution
> Remove one of the routes that creates the cycle.
> Errors
> [%s@%s]: rejected connect from route: invalid cycle in route: %s
> Illegal, route to '%s' creates a cycle. Terminate the connection
> Illegal, route to '%s' creates a cycle.

> Category
> Rendezvous transport error
> Description
> tibemsd encountered a Rendezvous error.
> Resolution
> See Rendezvous documentation for details of what the error means and how to remedy it.
> Errors
> Unable to create dispatcher for import event for %s '%s' on transport '%s', error is %s
> Unable to create inbox for import event for %s '%s' on transport '%s'
> Unable to create Rendezvous Certified transport '%s': %s
> Unable to create Rendezvous Certified transport '%s' because unable to create Rendezvous transport '%s'
> Unable to create Rendezvous transport '%s': %s
> Unable to create TIBCO Rendezvous Certified Listener for %s '%s' on transport '%s': %s
> Failed to confirm RVCM message: %d (%s)
> Failed to confirm RVCM message sequence % PRINTF_LLFMT u from cm sender '%s'. Error: %d (%s)
> Unable to store trackId % PRINTF_LLFMT d for RVCM message sequence % PRINTF_LLFMTu from cm sender '%s'. Error: %d (%s)
> Unable to retrieve trackId % PRINTF_LLFMT d. Error: %d (%s)
> A problem occurred while importing RVCM message sequence % PRINTF_LLFMT u from cm sender '%s'. Expecting a redelivery
> Unable to queue the request type: %d. Transport '%s', destination '%s', CM Sender '%s', CM Sequence % PRINTF_LLFMT u . Error: %d (%s)
> Unable to queue the request type: %d. Transport '%s', destination '%s'. Error: %d (%s)
> Failed to disallow Rendezvous Certified Message listener '%s': %s
> Unable to export topic message, error=%s.
> Unable to pre-register certified listener '%s' on transport '%s': %s
> Rendezvous send failed on transport '%s', error='%s'
> Unable to restart the CM Listener for %s '%s' (RVCM Transport '%s'). Error code: %d '%s'
> Unable to create the timer for the restart of the CM Listener for %s '%s' (RVCM Transport '%s'). Error code: %d '%s'
> Unable to stop the CM Listener for %s '%s' (RVCM Transport '%s'). Error code: %d '%s'

> Category
> Running on reserve memory
> Description
> Warnings indicating that the tibemsd has run out of memory and is now using its reserve memory
> Resolution
> Either reduce the tibemsd's memory requirement by consuming messages or removing messages from its queues, or increase the amount of memory available to the tibemsd by shutting down other processes on the machine or increasing the machine's memory.
> Errors
> Running on reserve memory, ignoring new message.
> Running on reserve memory, no more send requests accepted. Pending msg count = % PRINTF_LLFMT d
> Pending msg count = % PRINTF_LLFMT d

> Category
> SmartSockets transport error
> Description
> tibemsd encountered a SmartSockets error.
> Resolution
> See SmartSockets documentation for details of what the error means and how to remedy it.
> Errors
> Unable to create SmartSockets subscriber on transport '%s': failed to convert %s '%s', error=%s
> Unable to import SmartSockets message on transport %s: failed to convert subject '%s', error=%s
> Unable to import SmartSockets message on transport %s: failed to tokenize subject '%s'
> Unable to import SmartSockets message on transport %s: failed to convert reply subject '%s', error=%s
> Unable to import SmartSockets message on transport %s: no destination found '%s'
> Unable to export EMS message into SmartSockets on transport '%s'. Failed to convert subject '%s', error=%s.
> Unable to export EMS message into SmartSockets on transport '%s'. Failed to convert reply subject '%s', error=%s.
> Error translating EMS message body into SS message. Status=%s
> Error translating EMS message headers into SS message. Status=%s
> Error translating EMS message properties into SS message. Status=%s
> Unable to confirm SS message. %s
> Unable to connect to SmartSockets RTserver via transport: '%s': %d - %s
> Unable to register GMD failure callback: '%s': %d - %s
> Unable to create open callback on transport: '%s': %d - %s
> Unable to create default callback on transport: '%s': %d - %s
> Unable to create SS callback for %s '%s' on transport '%s' SS error: %s
> Unable to create SS message type on export
> Unable to create SmartSockets subscriber for %s '%s' on transport '%s', error: %s
> Unable to create SmartSockets transport '%s': %d - %s
> Failed to confirm SS message. error=%s.
> Failed to create SmartSockets transport %s
> Unable to handoff confirm SS message: %s.
> Unable to import SS message. Error=%d, %s.
> Unable to import SS message data fields. Error=%d, %s.
> Unable to import SS message headers. Error=%d, %s.
> Unable to import SS message, failed to create message destination.
> Unable to import SS message, failed to create reply destination.
> Unable to import SS message, error retrieving delivery mode.
> Unable to import SS message, error setting imported property. error=%s.
> Unable to import SS message, error setting message extentions property. error=%s.
> Unable to import SS message, failed to create message wire. error=%s.
> Unable to import SS message, error retrieving number of fields.
> Unable to initialize SmartSockets transport '%s': error=%d: %s
> Unable to set SmartSockets Dispatcher for transport: '%s': %d - %s
> Unable to set SS message type on export
> Unable to set Username/Password for SmartSockets transport '%s': %d - %s
> Unable to import SmartSockets message on transport %s: failed to retrieve SS subject.
> SS Subject CB destroy Failed: for '%s' on transport '%s' SS error: %s
> SS Subject CB lookup Failed: for '%s' on transport '%s' SS error: %s
> SmartSockets TipcMsgSetDeliveryMode failed, '%s'
> SmartSockets TipcMsgSetLbMode failed, '%s'
> SmartSockets TipcSrvConnFlush failed, '%s'
> SmartSockets TipcSrvConnMsgSend failed, '%s'
> SS Unsubscribe failed: for '%s' on transport '%s' SS error: %s
> GMD delivery failed on transport '%s', SS message seq=%d, reason='%s' for process '%s'
> Unable to process undelivered SS GMD message, can not register EMS message, error='%s', tport='%s', GMD seq=%d
> Unable to process undelivered SS GMD message, can not add to undelivered EMS queue, error='%s', tport='%s', GMD seq=%d
> Unable to process undelivered SS GMD message, failed to build EMS message, error='%s', tport='%s', GMD seq=%d
> Unable to convert undelivered SS GMD message into EMS message, error='%s', tport='%s', GMD seq=%d

> Category
> SSL initialization failed
> Description
> The server failed attempting to initialize the OpenSSL library.
> Resolution
> Examine the OpenSSL error and the EMS User's Guide chapter describing the use of SSL.
> Errors
> Failed to process ft ssl password
> Failed to process ssl password
> Ignoring SSL listen port %s
> Failed to initialize SSL: can not load certificates and/or private key and/or CRL file(s) and/or ciphers.
> Failed to initialize OpenSSL environment: error=%d, message=%s.
> Failed to initialize SSL. Error=%s
> Failed to initialize SSL: unable to obtain password
> Failed to initialize SSL: server certificate not specified.
> Failed to initialize SSL: server private key not specified.

> Category
> System call error, should be errno-driven
> Description
> A low-level system function has failed.
> Resolution
> Report the error to your system administrator and ask them to remedy the problem.
> Errors
> Accept() failed: too many open files. Please check per-process and system-wide limits on the number of open files.
> Accept() failed: %d (%s)
> Select() failed: %d (%s)
> Epoll_wait() failed: %d (%s)
> Epoll_ctl() %s on fd %d failed: %d (%s)
> ioctl() on /dev/poll failed: %d (%s)
> write() %s update /dev/poll on fd %d failed: %d (%s)
> Cannot retrieve user name of the current process.
> Client connection not created, %s.
> Could not obtain hostname
> Could not resolve hostname '%s'. Possibly default hostname is not configured properly while multiple network interfaces are present.
> Unable to listen for connections: %d (%s).
> Unable to open socket for listening: %d (%s).
> Closing SSL connection from %s due to timeout.

> Category
> Unnecessary or duplicate message
> Description
> tibemsd received a message with either missing or incomplete data.
> Resolution
> Send details of the error and the situation in which it occurred to TIBCO Support.
> Errors
> Error processing xa start request, %s. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d
> Error trying to enter standby for '%s', %s.

> Category
> Unrecognized option
> Description
> The server's command line contains an unrecognized option.
> Resolution
> Run the server with the -help option and compare it with the command line containing the unrecognized option.
> Errors
> Unrecognized option: '%s'.

> Category
> Restoring consumer failed
> Description
> Seen when tibemsd starts up and detects that the zone for a route as specified in routes.conf has been changed.
> Resolution
> Either delete the route or change its zone back and restart the tibemsd.
> Errors
> Restoring consumer failed: Conflicting zone for route to [%s]: The route was initially zone %s type %s, but now %s type %s. Zone change not allowed while there are durable subscribers. Please delete the route first and create new one.

> Category
> Banners and debug traces
> Description
> Banner and debug traces
> Resolution
> Not applicable
> Errors
> %s: %s has been changed
> %s: %s has been changed to %s
> %s: %s has been changed to %d
> %s: %s has been changed to % PRINTF_LLFMT d
> Invalid session for route configuration.
> Invalid routed queue information message.
> Expired % PRINTF_LLFMT d message%s.
> Discarded % PRINTF_LLFMT d message%s.
> [%s@%s]: rejected connect from route: invalid password
> %s: purged durable '%s'
> %s: %s %s '%s' permissions on %s '%s': %s
> %s: create %s failed: durable creation access denied for %s [%s].
> Async Recs: max=%d avg=%.2f min=%d
> Process Id: %d
> Server activating on failure of '%s'.
> ldap_search_ext_s(%x, %s, %s, %s)
> Flow Stall Recovery Timer: to recover stall of %s on route from %s, recovery count = %d
> Error, filter '%s' contains an illegal type substitution character, only %%s is allowed
> Rendezvous Certified Advisory: %s
> LDAP response resulting from checking if an entry is a member of a dynamic group:'
> ignoring route '%s' at '%s', route user does not exist.
> Created %s transport '%s'
> Send recover request for routed queue flow stall for queue %s
> Removing routed topic consumer '%s'
> License has been activated.
> Hostname: %s
> Evaluation Software Notice: remaining uptime is %d hours %d minutes.
> [%s@%s]: rejected connect from route: implicit route already exists
> LDAP response resulting from getting attributes for group '%s':
> ldap_parse_reference: %s
> Storage Location: '%s'.
> Search reference: %s
> Route Recover Interval is %u seconds.
> Route Recover Minimum Message Count is %u.
> Route connect error: route has no zone setting
> SS: Deleting existing GMD file.
> LDAP error: %s
> Clean all flow stalls for route to server %s: %s
> %s: shutdown server
> Reading configuration from '%s'.
> Configuration warning: file=%s, line=%d: illegal to specify both '%s' and '%s', ignoring '%s'
> Recovered flow stalled consumer for destination: %s:%s
> %s: revoked all %s permissions on %s '%s'
> Error sending routing information to '%s'.
> Send recover request
> Skipping recover request, message count % PRINTF_LLFMT d greater than recover count
> Lazy Dels: max=%d avg=%.2f min=%d
> Release Holds: max=%d avg=%.2f min=%d
> %s: created rvcmlistener transport '%s' name '%s' dest '%s'
> ERROR: file=%s, line=%d: %s is too long.
> Route '%s' connecting to url '%s'.
> Route '%s' connected to url '%s' with zone '%s:%s'.
> Detected tie during route creation '%s'. Resolution, keep existing route (connID=% PRINTF_LLFMT d).
> Detected tie during route creation '%s'. Resolution, destroy existing route (connID=% PRINTF_LLFMT d).
> Found connID=%PRINTF_LLFMTd for existing route '%s', but no connection.
> [%s@%s]: rejected connect from route: %s
> Configuration warning: file=%s, line=%d: Use of Rendezvous Bridge via tibrv_... parameters has been deprecated. This feature is subject to removal in the next release of this product. Please convert your configuration to utilize transports defined in transports.conf configuration file.
> Rendezvous %s %s enabled (RV %s).
> Error in ldap_search_ext_s: %s
> Server is re-entering standby mode.
> Statistics database memory now below limit
> SS: Destroying SmartSockets transport %s
> Created file '%s'
> Restored routed topic consumer for '%s'
> Adding routed topic consumer for '%s'
> Subscriber %s for topic '%s' exceeded topic limit.
> Refrained from removing configured durable '%s'
> Sync Recs: max=%d avg=%.2f min=%d
> SS: Unsubscribe from '%s' tport = %s
> Recovered %d pending connection%s.
> SS: Imported message on tport='%s', subject='%s', reply='%s'.
> Clean flow stall for consumers of destination %s:%s
> ldap_search_s(%x, %s, %s, %s, [NULL])
> %s:%s queue browser failed: illegal to use wildcard queue [%s]
> There should be only one consumer reaching %s, but %d found
> %s:%s queue browser failed: cannot browse [%s] because it is a routed queue.
> Detected IP interface: %s (%s)
> Clear (Non-IO) flow stalled on dest %s:%s from route of %s
> Error sending routing information to %s, send failed
> %s: %s updated: '%s'
> %s: consumed_msg_hold_time updated: '%d'
> Authorization is disabled.
> SSL connect: using certificate username '%s'.
> SSL reset to TCP for connID=% PRINTF_LLFMT d, user='%s'
> Configuration warning: file=%s, line=%d: invalid trace option '%s' is ignored
> Server is now active.
> (NON-IO) Flow stalled on dest %s from route of %s
> Dump of user cache:
> Administrator group not found, created with default member.
> Received exception on route '%s':'%s'
> ldap_search_s(%x, %s, %s, %s, [%s,%s,%s,%s,%s,NULL])
> EXPIRE: msgs=%d
> Clean flow stall for routed consumer of queue %s
> EXPIRE: total=% PRINTF_LLFMT d expire=0
> EXITING
> Configuration error: file=%s, line=%d: ignoring invalid selector specifications in route parameters
> %s: created group '%s'
> set %s:% PRINTF_LLFMT d in flow stall recover request
> Error: unable to bind to LDAP server as: '%s', %s
> DISK IO stats for %s:
> Authorization exception creating routed topic consumer for '%s'
> Fault tolerant reconnect timeout is set to a negative or 0 value of %d seconds,
> Licensed server is waiting for license activation.
> LDAP message resulting from checking existence:
> Memory limit of %d MB exceeded.
> %s %s to %s: connID=% PRINTF_LLFMT d consID=% PRINTF_LLFMT d msgID='%s' %s='%s'%s%s%s%s%s%s
> User '%s' is authenticated via LDAP
> User '%s' is authenticated via JAAS
> Route '%s' accepted from host '%s' with zone '%s:%s'.
> %s:%s queue browser failed: queue does not exist: [%s]
> %s acknowledged by %s: connID=% PRINTF_LLFMT d consID=% PRINTF_LLFMT d msgID='%s' %s='%s'
> %s premature exit: %s : connID=% PRINTF_LLFMT d prodID=% PRINTF_LLFMT d msgID='%s' %s='%s'
> %s: removed user '%s' from group '%s'
> Reading SS configuration from '%s'.
> Ignoring inbound routed topic '%s', illegal topic.
> %s: Compacting %s with no time limit.
> STARTING POP WAITING
> Flow stall recover ack received Post IO
> RVCM name not specified for transport '%s', using RVCM name '%s'
> Purged % PRINTF_LLFMT d queue message%s.
> Purged % PRINTF_LLFMT d topic consumer message%s.
> No memory to process incoming data from connection id=% PRINTF_LLFMT d. Connection terminated.
> %s: Disconnected, connection id=% PRINTF_LLFMT d, reason: %s%s
> %s: connection id=% PRINTF_LLFMT d purged after FT timeout
> Error, missing %s parameter
> Bytes: max=%d avg=%.2f min=%d
> Server is active.
> %s: %s bridge: source=[%s:%s] target=[%s:%s]
> Error, filter '%s' contains too many occurrences of %%s, max allowed is: %d
> %s: created JNDI name '%s' for %s '%s'
> Server is in standby mode.
> %s: create %s failed: durable access denied for %s [%s].
> %s: Destroyed producer (connid=% PRINTF_LLFMT d, sessid=% PRINTF_LLFMT d, prodid=% PRINTF_LLFMT d) %s
> ldap_simple_bind_s(, *******)
> [%s] %s
> Active server '%s' not found.
> Backup server '%s' has connected.
> Error in ldap_set_option: %s
> %s:%s queue browser failed: access denied for queue [%s]
> Ignoring inbound routed topic '%s', no corresponding topic.
> %s: created user '%s'
> Unable to initialize route: expected route name '%s', received '%s'.
> Evaluation Software Notice: remaining uptime is %d minutes.
> %s: created topic '%s'%s%s
> Connected to LDAP server %s
> Processed %d msgs
> Error, LDAP is disabled
> Configuration warning: file=%s, line=%d: illegal to use '.' in server name, replaced with '_',
> %s: %s %s '%s' administrative permissions: %s
> Warning: statistics database memory exceeded limit
> [%s@%s]: rejected connect from route: this shouldn't happen: route exists with no zone setting
> Rejected connect from route '%s' at %s, routing disabled.
> Missing heartbeats from primary server '%s'.
> Flow stall recovery request received, send to IO
> Unable to initialize route '%s': route server returned: '%s'
> RUNNING SWAPPER %d %d needed = %u!
> Restoring consumer warning: zone of id %d does not exist in zone mapping entries
> Ignoring inbound routed queue '%s', no corresponding queue.
> %s:%s queue browser failed: illegal to use reserved queue [%s]
> %s: committed transaction %s
> Trying to send flow stall recovery request for destination: %s
> %s: destroyed connection % PRINTF_LLFMT d
> ldap_search_s(%x, %s, %s, %s, [%s,%s,%s,NULL])
> Allocating storage to minimum %s for store '%s', please wait.
> %s:%s queue browser failed: invalid name of queue [%s]
> %s: updated group '%s'
> SS: Created subscriber to '%s' LB override=%d. tport='%s'
> %s: destroyed message '%s'
> Configuration warning: file=%s, line=%d: Use of Rendezvous import/export settings via tibrv_... parameters has been deprecated. This feature is subject to removal in the next release of this product. Please convert your configuration to utilize 'import' and 'export' properties and using transports defined in transports.conf configuration file.
> Route '%s' disconnected, connection id=% PRINTF_LLFMT d
> Logging into file '%s'
> %s: create %s failed: access denied for %s [%s].
> Unable to obtain message type number for imported SS message
> Route Warning: host of this name does not exist: %s
> %s: created queue '%s'%s%s
> now timer fired
> Clock sync timer created with interval %d seconds
> Clock sync timer fired
> Clock sync timer error: %s
> Breaking from remove thread for wantsLock!
> %s: created JNDI name '%s' = '%s'
> Metadata storage: '%s'.
> Flow stall recover ack received for destination %s
> Server rereading configuration.
> Route '%s' sent resume request
> Refrained from deleting configured durable '%s' even though application's attributes differ from configuration
> EXPIRE: msgs=% PRINTF_LLFMT d exp=% PRINTF_LLFMT d expd=% PRINTF_LLFMT d int=% PRINTF_LLFMT d tm=% PRINTF_LLFMT d
> Server of version %d.%d does not support flow stall recovery, do nothing.
> %s: rotated log file.
> Asynchronous storage: '%s'.
> Created Routed Dynamic Queue '%s' from '%s'
> Results of searching for dynamic groups:
> Transaction for non-existent consumer: % PRINTF_LLFMT d connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> Error in ldap_unbind: %s
> Rendezvous %s %s enabled.
> [%s@%s]: route connect failed: invalid password
> %s: updated topic '%s': %s
> ldap_search_s(%x, %s, %s, %s, [%s, NULL])
> Configuration warning: file=%s, line=%d: invalid option '%s' is ignored
> Server is in standby mode for '%s'.
> Error, references not supported
> Acknowledging the flow stall recover request for destination %s:%s and resume the flow
> Failed to rename file, original file %s saved as file %s. Please rename the file
> Route connect error: can not connect to route '%s' at '%s', error=%s.
> Recovered %d message%s.
> %s: deleted group '%s'
> Start opening sync db
> Start opening async db
> Removed Routed Dynamic Queue '%s'
> %s: %s bridge: source=[%s:%s] target=[%s:%s] selector='%s'
> Error, zero entries returned from getting attributes for group '%s':
> Warning: configuration file 'tibjmsd.conf' should be renamed to 'tibemsd.conf'.
> Warning: [queue: %s]: dynamic routed queues are not supported.
> Transaction for non-existent message: % PRINTF_LLFMT d connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
> Route recovery of destination %s on route from %s failed, will try again: %s
> [%s@%s]: route connect failed: route server not authorized.
> Implicit route to [%s] already exists
> %s: %s route '%s', URL=[%s]
> Results of searching for static groups:
> %s: Queue limit exceeded for queue '%s'.
> %s: Topic limit exceeded for topic '%s'.
> Implicit route to '%s' already exists.
> %s: deleted rvcmlistener transport '%s' name '%s' dest '%s'
> Evaluation Software Notice: remaining uptime is %d hours.
> Secure Socket Layer is enabled, using %s
> Using cryptographic module %s
> Reserve memory reestablished, all client requests accepted. Pending msg count = % PRINTF_LLFMT d
> Msg recs processed = %d
> ldap_search_s(%x, %s, %s, %s, [%s,%s,NULL])
> (IO) Flow stalled on dest %s:%s from route of %s
> Invalid specifications for route '%s' topic '%s'
> %s: Created producer (connid=% PRINTF_LLFMT d, sessid=% PRINTF_LLFMT d, prodid=% PRINTF_LLFMT d) %s
> SS: Consumer subscribe to '%s' LB override=%d. tport='%s'
> Routing is enabled.
> Recovering state, please wait.
> Files opened.
> Starting msgPass.
> Finished msgPass.
> Administrator user not found, created with default password.
> Route '%s' sent suspend request
> %d batches, %.2f batches/sec
> %s: purged queue '%s'
> Error in ldap_search_s: %s
> %s: created durable '%s' Selector: %s
> Accepted license with limits: conns=%d hosts=%d hours=%d
> USING %d memory
> Continuing as active server.
> VALIDATING STORE %s
> [%s@%s]: rejected connect from route: route already connected
> %s: purged topic '%s'
> ldap_search_ext: %s
> Flow control %s on %s '%s'
> Accepting connections on %s.
> Configuration warning: ignoring tibrvcm_import property set on %s '%s' because it collides with tibrvcm_import property on %s '%s'
> Warning: configuration file '%s' not found and has been created. All configuration settings have been reset to defaults.
> EXPIRE ERROR: oldCount=% PRINTF_LLFMT d found=% PRINTF_LLFMT d walked=% PRINTF_LLFMT d
> Shutdown complete.
> Restarting now.
> %s: Created %s%sconsumer%s%s%s%s (connid=% PRINTF_LLFMT d, sessid=% PRINTF_LLFMT d, consid=% PRINTF_LLFMT d) on %s '%s'%s%s%s%s
> Search completed successfully. Entries found: %d
> Created routed dynamic queue '%s' for '%s'
> %s: deleted durable '%s'
> Part of the DN that matches an existing entry: %s
> Purged %d connection%s.
> Ignoring inbound routed topic '%s', local topic is not global.
> %s: deleted user '%s'
> %s: create %s failed: access denied for monitoring %s [%s].
> Administrator group found with no members, added default member.
> %s: updated user '%s'
> SmartSockets transports are enabled.
> Running in Temporary Destination Compliance mode.
> ldap_search_s(%x, %s, %d, %s, [%s,NULL])
> %s: %screated dynamic %s '%s'
> Using %d threads for LDAP processing.
> Routing is disabled.
> %s: %s factory '%s'
> INIT-EXPIRE: exp=%d mexp=% PRINTF_LLFMT d oldt=% PRINTF_LLFMT d interval=%d
> Error in ldap_initialize(%s)
> Created dynamic %s '%s'
> %s: Compacting %s with time limit %PRINTF_LLFMTd seconds
> Error sending route query to '%s'.
> %s: updated queue '%s': %s
> Server name: '%s'.
> Route configuration error: global queue '%s' from route '%s' collides, global queues must be unique.
> Route configuration error: routed queue '%s' from route '%s' is not global in '%s'.
> Server shutting down.
> Server preparing to restart.
> Route configuration warning: global queue '%s' from route '%s' not configured on local server
> Flow stall recovery request received, recover consumer of id % PRINTF_LLFMT d
> Flow Control is enabled.
> %s: deleted JNDI name '%s'
> Clear (IO) flow stalled on dest %s:%s from route of %s
> Removing route '%s', URL='%s': this route is duplicate, creates a loop or has configuration errors
> EXPIRE: giving up amid lock
> Done opening async db
> Error, invalid search scope: %s
> Error in ldap_url_parse, returned: %d
> %s: create %s failed: durable recreation access denied for %s [%s].
> Ignoring inbound routed queue '%s', illegal queue.
> key: '%s' value: '%s'
> Connection to primary server '%s' has been lost.
> Route connect error: failed connect to server '%s' at '%s'
> %s: rolled back transaction %s
> LDAP response resulting from checking existence:
> ldap_parse_result: %s
> Hostname IP address: %s
> Flow stall recovery request received, after IO
> %s: Connected, connection id=% PRINTF_LLFMT d, type: %s%s
> %s: Reconnected, connection id=% PRINTF_LLFMT d, type: %s%s
> Unable to initialize one hop route: One-hop routing is not supported for server version %d.%d
> Error, must provide static and/or dynamic group name attribute
> Unable to initialize route, expected route name not received.
> Stat: rate=%d cleanup=%d memory=%d
> %s: Destroyed %sconsumer%s%s%s%s (connid=% PRINTF_LLFMT d, sessid=% PRINTF_LLFMT d, consid=% PRINTF_LLFMT d) on %s '%s'
> %s: Unsubscribed durable consumer '%s' due to administrator deleting durable (consid=% PRINTF_LLFMT d) on topic '%s'
> %s: Unsubscribed durable consumer '%s' due to user calling unsubscribe (connid=% PRINTF_LLFMT d, consid=% PRINTF_LLFMT d) on topic '%s'
> %s %s from %s: connID=% PRINTF_LLFMT d prodID=% PRINTF_LLFMT d msgID='%s' %s mode=%s size=%d %s='%s'%s%s
> ldap_search_s(%x, %s, %s, %s, [%s,%s,%s,%s,NULL])
> ldap_search_s: %s
> Error, filter '%s' too long, max length is %d characters
> %s: deleted %s '%s'
> Disallowing Rendezvous Certified Message listener '%s'
> SS: Exporting EMS message: tport='%s', dest='%s', reply='%s' SSDelivery=%d, LB=%d
> Refrained from removing configured route durable '%s'
> Authorization is enabled.
> Rendezvous Advisory: %s
> Refrained from removing durable for route '%s' due to configured durable
> Configuration error: file=%s, line=%d: invalid value of option '%s'. Unable to start.
> %s: %sconnect failed: %s%s
> unable to create connection with existing ID % PRINTF_LLFMT d
> Synchronous storage: '%s'.
> Clean all flow stalls for destination %s
> Done opening sync db
> %s: added user '%s' to group '%s'
> ldap_search_s(%x, %s, %s, %s, [%s,%s,%s,%s,%s,%s,NULL])
> Configuration warning: file=%s, line=%d: can not specify 'NONE' with other options
> %s: %s failed: access denied for %s [%s].
> Process started from '%s'.
> Clean flow stall for routed consumer of queue %s: no other remote consumers, remove the stall
> [%s@%s]: connect failed: reached maximum number of %s %d
> Refrained from removing durable for route '%s' due to configured durable
> LDAP Cache: User '%s' is a member of group(s):
> LDAP Cache: Deleting cached record of user: '%s'
> Client ID is too long.
> Durable name is too long.
> Durable name must be specified (connID=% PRINTF_LLFMT d)
> Consumed Msg Hold Time is %d seconds.
> A duplicate durable instance (conn=%s durable=%s dest=%s) was detected, discarding old one
> A duplicate connection with same client id (clientid=%s) detected, destroying old conn (conn-id=% PRINTF_LLFMT d)
> Warning, deleting and recreating durable '%s' due to change in client attributes: %s%s%s
> Unable to build monitor message. Error code: %d - %s
> Multicast is enabled.
> %s: Multicast consumers require NO_ACKNOWLEDGE sessions: %s
> %s: Multicast consumers require non-transacted sessions: %s
> %s: Multicast consumer status: %s (consid=% PRINTF_LLFMT d)
> %s: Multicast consumer status: %s (consid=% PRINTF_LLFMT d channel='%s')
> [%s]: tx=% PRINTF_LLFMT d bytes, rtx=% PRINTF_LLFMT d bytes, buf=% PRINTF_LLFMT d bytes
> [%s@%s %s]: rcv=% PRINTF_LLFMT d bytes, lost=% PRINTF_LLFMT d, naks=% PRINTF_LLFMT d, failed=% PRINTF_LLFMT d
> %s
> %s: JMX stats for store '%s' updated: %s
> Route configuration: Adding topic '%s' for server %s
> Route configuration: Sending %d topics to server %s at %s - %s
> Route configuration: Sending topics to server %s at %s - %s
> Route configuration: Sending queue '%s' to server %s at %s - %s
> Route configuration: Sending queues to server %s at %s - %s
> Route configuration: Processing topics from server %s at %s.
> Route configuration: Processing queue '%s' from server %s at %s.
> Route '%s' acknowledgment timer destroyed.
> Route '%s' acknowledgment timer unknown event type.
> Route '%s' acknowledgment timer send failed: %s
> Route '%s' acknowledgment timer connection % PRINTF_LLFMT d not found.
> Route configuration: Processing queues from server %s at %s.
> Discarded incoming client message exceeding size limit: connID=% PRINTF_LLFMT d, %s='%s', size=%d.
> Configuration update failure: %s
> Rolling back to configuration on disk.
> Rollback failed: %s
> Rollback succeeded.
> %s property [%s].
> %s configuration item:
> %s status: %s
> Illegal property get in _emsdConfigurationObjectProperty_GetStringValue.
> Attempting to generate a search key for an unsearchable object (%s).
> More than one result found searching route selectors route=%s topic=%s.
> More than one result found searching alias %s=%s jndiName=%s.
> Secondary override required for single file fault tolerance using \qlocalhost\q.
> Secondary override required for single file fault tolerance on one host.
> Secondary override requires a fault tolerant active url.
> Secondary override requires a fault tolerant secondary active url.
> Configured as fault tolerant secondary.
> Configured as fault tolerant primary.
> Unable to find group %s.
> Detected Mixed mode configuration: Ignoring property %s file=%s, line=%d
> Missing field %s from server object %s near line %d.
> Invalid field detected in server object (%s), field (%s), at line %d.
> %s will not complete until the server is restarted.
> Detected unsupported password hash for user \q%s\q. The user's password may need to be reset.
> Ignoring request to remove an administrative user.
> Ignoring request to remove the administrative group.
> %s will not occur until fault tolerant failover or restart.
> Ignoring unknown property %s.
> Configuration error: file=%s, line=%d: ignoring rvcmlistener
> Illegal configuration namespace set, %s=%s Expecting %s.
> Failed to write file %s: (%s)
> Error loading configuration: %s
> Applying configuration changes.
> Configuration update status: %s
> Rollback unable to load file %s.
> Initialized queue browser on '%s'%s%s%s
> Creating store '%s' file '%s' ...
> Converting %s format from %s to %s
> First scan on '%s' is finished
> Destination cursor id % PRINTF_LLFMT d %s slot %d
> Client browsing mstore-based queue %s needs to be upgraded for optimum performance.
> Warning: file=%s, line=%d: multicast_udp_encapsulation is no longer a supported parameter.

> Category
> Runtime Error in Fault-Tolerant Setup
> Description
> In a fault-tolerant setup, error occurs at runtime.
> Resolution
> Check the status of the both server (primary, standby). In case of both active, the file store data may be corrupted already and we recommend shutting down both servers and investigate the situation.
> Errors
> Fault-tolerance error: Dual-Active server detected at: '%s'
> The primary EMS server does not hold the lock on meta store
> The standby EMS server could not find the specified meta store.
> The primary EMS server name is %s while the standby EMS server name is %s. The names must be the same
> A backup EMS server (%s) is already connected to the primary EMS server
> Fault Tolerant error (%s), can't create connection to '%s'.

> Category
> Errors in Database Stores Setup
> Description
> In a database stores setup, errors occuring at runtime
> Resolution
> Check your database server vendor and database administrator for failures occuring during writes,deletes,reads of different records, for failures occuring during database store open check with the database administrator for permissions and the existence of the database. For failures occuring during a FT setup where all the stores are database stores, please check with the database server vendor or database administrator. In the case where both are active, we recommend shutting down both the servers and investigating the problem.
> Errors
> Unable to open store [%s]: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to store message record in store [%s]: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to write ack record in store [%s]: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to write txn record in store [%s]: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to update txn record in store [%s]: [ ESTATUS = %d, ERRSTR = %s ]
> No memory to create no hold list for valid msgs record
> No memory to create hold list for valid msgs record
> No memory to create held list for valid msgs record
> Failed to write valid msg record in store [%s]: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to update msg record with record id [% PRINTF_LLFMT d] in store [%s]: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to delete %s record id = % PRINTF_LLFMT d : [ ESTATUS = %d, ERRSTR = %s ]
> Failed to read message with store id = % PRINTF_LLFMT d: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to initialize dbstore [%s]: [ ERRSTR = %s ]
> Failed to open store [%s], error = %s
> Unable to restore %s records from store [%s]: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to delete meta record: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to beginTransaction: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to read message with store id = % PRINTF_LLFMT d: [ ESTATUS = %d, ERRSTR = %s ]
> Store [%s] locked by server %s
> Store [%s] cannot be locked by server %s
> Failed to store txn record: [ txn id = % PRINTF_LLFMT d, ESTATUS = %d ]
> Failed to update txn record: [ txn record id = % PRINTF_LLFMT d, ESTATUS = %d ]
> Exception while processing msg from database store [%s], error = %d
> Failed to write meta record: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to update meta record: [ ESTATUS = %d, ERRSTR = %s ]
> Failed to write connection record: error = %d
> Failed to write session record: error = %d
> Failed to write consumer record: error = %d
> Failed to write producer record: error = %d
> Failed to write zone record: error = %d
> Failed to update connection record: error = %d
> Failed to update consumer record: error = %d
> Failed to write purge record: [ ESTATUS = %d, ERRSTR = %s ]
> Commit Transaction Failed [ ESTATUS = %d, ERRSTR = %s ]
> No Memory to create lock manager: Store [%s] cannot be locked by server %s
> Could not find system record for store [%s]

> Category
> Multicast Daemon Status Codes and Errors
> Description
> Errors occuring in the Multicast Daemon.
> Resolution
> Check the configuration of the Multicast Daemon and Server, as well as the health of the network.
> Errors
> Interface IP address: %s
> [%s] Connection created, connid=% PRINTF_LLFMT d
> Error: Unable to set channel property \q%s\q=% PRINTF_LLFMT d
> [%s] Created consumer consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTd topic=\q%s\q
> Multicast Daemon Id=%s
> Statistics enabled on a %d second interval.
> Statistics disabled.
> Rotating log from %s to %s
> Memory allocation error, possible data loss.
> Unrecoverable PGM error rc=%d, reason=%s
> Could not parse configuration file \q%s\q
> Interface IP address: %s
> Tracing enabled.
> Tracing disabled.
> refused new connection with existing ID % PRINTF_LLFMT d
> [%s] Connection destroyed, connid=%PRINTF_LLFMTd
> Error sending to consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTd from channel \q%s\q: %s
> %s, status=%s
> Attached channel \q%s\q to consumer consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTd
> Error attaching channel \q%s\q to consumer consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTd
> Detaching channel \q%s\q from consumer consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTd
> Destroying consumer consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTd
> Channel configuration from server does not match existing channel \q%s\q
> Ignoring additional PGM receiver created on group \q%s\q, dport=%d, sport=%d, channel=%s
> Created channel: \q%s\q
> Error: %s is not a valid multicast-capable IP address. Use the -ifc command line parameter to specify a valid interface.

> Category
> General Multicast Status Codes and Errors
> Description
> General multicast errors that can occur in the Server and Multicast Daemon.
> Resolution
> Check the configuration of the Multicast Daemon and Server, as well as the health of the network.
> Errors
> PGM ERROR: %s - %s (%d)
> PGM ERROR: channel=\q%s\q - %s (%d)
> Error setting PGM parameter %s=%u: %s (%d)
> Error setting PGM parameter %s=\q%s\q: %s (%d)
> Error getting PGM parameter \q%s\q: %s (%d)
> Error getting PGM statistic \q%s\q: %s (%d)
> Received an invalid EMS Message.
> Received a message spanning mulitple fragments.
> PGM Session was reset for channel \q%s\q, PGM seqno=%PRINTF_LLFMTd, code=%c
> Stopped receiving on channel \q%s\q
> Started receiving on channel \q%s\q
> Error receiving on channel \q%s\q
> Stopped sending on channel \q%s\q
> Started sending on channel \q%s\q
> Error creating sender on channel \q%s\q: %s

> Category
> Multicast channel allotted bandwith exceeded.
> Description
> Indicates that a multicast channel's allotted bandwidth has been exceeded.
> Resolution
> Either slow down the publisher(s), enable flow control, or increase the multicast channel's allotted bandwidth by increasing the channel's maxrate property or increasing the server's multicast_reserved_rate property.
> Errors
> Multicast channel \q%s\q has exceeded its allotted bandwidth

> Category
> Store file format mismatch
> Description
> The store files specified were created from a different version of EMS that is not supported by this version.
> Resolution
> Revert to use the version of EMS that created the store file or locate the store file conversion tool and use it to convert the store file to this version.
> Errors
> Unsupported store format: %s (%d)

> Category
> Recovery errors
> Description
> An error occurred during the recovery process.
> Resolution
> If you are not able to fix the problem and need to restart the system, make a backup of the store files and restart the server with the '-forceStart' command line parameter. The server will then attempt to start regardless of errors (expect out-of-memory errors). In this mode, application messages and/or internal records causing problems (due to file corruption or other) will be deleted. Therefore, dataloss is likely to occur, so this command line parameter should be used with extreme caution and only after understanding the consequences. A copy of the store files can be sent to TIBCO Support for post-mortem analysis.
> Errors
> The recovery process stopped while processing a '%s' record (id=% PRINTF_LLFMT d), error: %d - %s. Check the section 'Problems on Startup' from chapter 'Running the EMS Server' in the User's Guide before attempting to restart the server
> The recovery process stopped while processing a '%s' record (id=% PRINTF_LLFMT d) due to an out-of-memory condition. Ensure that the system can allocate sufficient memory to the EMS Server process before restarting it
> Unable to get the session's context handle for %s record: %d - %s
> Unable to get the list iterator for %s record
> Unable to get next element from list for %s record
> Unable to create %s object, no memory
> Error occured while processing %s record id=% PRINTF_LLFMT d (%s) - Unable to reconstruct message: %d - %s
> Unable to recreate zone '%s': %d - %s
> Unable to add zone '%s' to the system: %d - %s
> Zone '%s' is defined as type '%s' in configuration but also is defined as type '%s' in meta.db
> Unable to recreate connection id=% PRINTF_LLFMT d: %d - %s
> Discarding session id=% PRINTF_LLFMT d because the connection id=% PRINTF_LLFMT d was not recovered. Recovery continues
> Unable to recreate session id=% PRINTF_LLFMT d with connection id=% PRINTF_LLFMT d: %d - %s
> Unable to recreate consumer id=% PRINTF_LLFMT d with connection id=% PRINTF_LLFMT d and session id=% PRINTF_LLFMT d: invalid destination: %s
> No memory to create destination for consumer id=% PRINTF_LLFMT d
> Discarding consumer id=% PRINTF_LLFMT d on destination '%s' because connection id=% PRINTF_LLFMT d was not restored. Recovery continues
> Discarding consumer id=% PRINTF_LLFMT d on destination '%s' and connection id=% PRINTF_LLFMT d because session id=% PRINTF_LLFMT d was not restored. Recovery continues
> No memory to recreate consumer id=% PRINTF_LLFMT d
> Failed to build import selectors for consumer id=% PRINTF_LLFMT d: %d - %s
> Failed to read import selectors for routed consumer id=% PRINTF_LLFMT d: %d - %s
> Discarding durable id=% PRINTF_LLFMT d (connection id=% PRINTF_LLFMT d) on destination '%s' because the durable name is not specified. Recovery continues
> Unable to recreate producer id=% PRINTF_LLFMT d with connection id=% PRINTF_LLFMT d and session id=% PRINTF_LLFMT d: invalid destination: %s
> No memory to create destination for producer id=% PRINTF_LLFMT d
> Discarding producer id=% PRINTF_LLFMT d on destination '%s' because connection id=% PRINTF_LLFMT d was not restored. Recovery continues
> Discarding producer id=% PRINTF_LLFMT d on destination '%s' with connection id=% PRINTF_LLFMT d because session id=% PRINTF_LLFMT d was not restored. Recovery continues
> Unable to recreate purge record: invalid destination: %s
> Unable to recreate purge record for destination %s: %d - %s
> Error creating message for transaction record: %d - %s
> Error creating message's store structure for transaction record: %d - %s
> Unable to recover transaction record: transaction id missing: %d - %s
> Unable to recover transaction id=% PRINTF_LLFMT d: %d - %s
> Unable to recover ack record (txid=% PRINTF_LLFMT d, consid=% PRINTF_LLFMT d, seqid=% PRINTF_LLFMT d, location=%s): %d - %s
> Unable to recover ack record, cannot create message: %d - %s
> Unable to recover sequence numbers from valid record: %s
> Unable to recover message, can not create lock: %d - %s
> Unable to restore held message from store, (location=%s) no memory
> Unable to restore message sequence=% PRINTF_LLFMT d: (location=%s) %d - %s
> No memory to create destination for message
> Inconsistency restoring routed message sequence=% PRINTF_LLFMT d
> No memory to restore routed message sequence=% PRINTF_LLFMT d
> Persisted message possibly corrupted: %s
> Error creating message's store structure: %d - %s

> Category
> Mstore errrors
> Description
> An error occurred using an Mstore database file.
> Errors
> Unable to open store %s: %s: %d (%s).
> Wrong schema version. Found %d, expected %d.
> Schema creation failed: '%s' error: %d %s
> Unable to reset a statement (%s): %s.
> Unable to step a statement (%s): %s: %d.
> Store %s: %s: bind fail: %d.
> Store %s: Fail retrieving consumer interest: %d.
> Store %s: Fail retrieving msg interest info: %s.
> Store %s: Fail writing transaction record: %s.
> Store %s: Fail reading data: %s.
> Store %s: Fail reading topic message: %s.
> Store %s: Fail marking topic message non-pending: %s.
> Store %s: Fail reading next topic message: %s.
> Store %s: Fail reading queue message: %s.
> Store %s: Fail getting next queue message: %s.
> Store %s: Fail marking queue message non-pending: %s.
> Store %s: Fail writing transaction info: %s.
> Store %s: Fail deleting transaction acks: %s.
> Store %s: Fail recording transaction msg: %s.
> Store %s: Fail recording transaction acks: %s.
> Store %s: Fail deleting ack: %s.
> Store %s: Fail completing transaction: %s.
> Store %s: Too many entries in memory message interest.
> Store %s: Invalid message interest for destination % PRINTF_LLFMT d.
> Store %s: Invalid destination read.
> Store %s: Failure restoring transaction: %s.
> Store %s: Failure restoring transaction msg: %s.
> Store %s: Failure restoring transaction ack: %s.
> Store %s: Failure resetting topic: %s.
> Store %s: Correct functioning cannot be guaranteed due to mstore failure. Exiting.
> Failed writing to mstore: I/O error or out of disk space.

> Category
> Dynamic Module Loading Errors
> Description
> An error occurred when loading or using a shared library module.
> Resolution
> Module loading is affected by the presence of shared libraries in the module path. Use the +load tracing flag to get more information about how the server is loading modules. See the section on Starting the EMS Server for more details.
> Errors
> Problem loading %s: %s
> Unknown problem loading %s.
> Loaded %s
> Problem binding %s: %s
> Unknown problem binding %s.
> Unable to locate %s
> Fatal error: Returned from exec(), errno = %d
> OpenSSL library version mismatch

> Category
> FIPS 140-2 Mode Errors
> Description
> An error occurred while starting or running the server in FIPS 140-2 compliant mode.
> Resolution
> Check the configuration of SSL related parameters to make sure that no incompatible ciphers or operations are requested.
> Errors
> Cannot specify ldap_tls_cipher_suite in FIPS 140-2 mode.
> Cannot specify ldap_tls_rand_file in FIPS 140-2 mode.
> Cannot specify SSL cipher list in FIPS 140-2 mode.
> Cannot specify random data source file in FIPS 140-2 mode.
> Cannot specify ssl_dh_size in FIPS 140-2 mode.
> Cannot specify ssl_server_ciphers in FIPS 140-2 mode.
> Cannot specify ssl_rand_file in FIPS 140-2 mode.

> Category
> Exceeded system resources.
> Description
> The system resources are inadequate for timely processing of server activities.
> Resolution
> Increase the specified resource or reduce the workload on this server.
> Errors
> Slow clock tick %d, delayed messaging and timeouts may occur.

> Category
> Transaction action while previous action is incomplete.
> Description
> State-modifying action is requested on a transaction for which another such action is being processed.
> Resolution
> Send details of the error and the situation in which it occurred to TIBCO Support.
> Errors
> Cannot request second state change for transaction while the first request is in progress (%d, %d) %s.
> Unexpected request to roll xa txn forward with previous operation (%d) incomplete: %s.
> Unexpected request to roll xa txn back with previous operation (%d) incomplete: %s.
> Unexpected request to prepare xa txn with previous operation (%d) incomplete: %s.
> Unexpected request to commit xa txn with previous operation (%d) incomplete: %s.
> Unexpected request to commit session with previous operation (%d) incomplete.

> Category
> Transaction timeout.
> Description
> Transaction not completed before timeout. Offending transaction is discarded.
> Resolution
> Most likely, transaction manager error prevented it from advancing this transaction in a timely manner. Verify correct operation of the transaction manner.
> Errors
> Rollback due to timeout on unprepared transaction. connID=% PRINTF_LLFMT d %s

Copyright © TIBCO Software Inc. All Rights Reserved