![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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.
An admin tool or program using the admin API attempted an operation that failed for the given reason.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.
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.
Change the value of the named parameter to an acceptable value; for information about tibemsd command line parameters, see EMS documentation.
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).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.%s %s to %s: connID=% PRINTF_LLFMT d consID=% PRINTF_LLFMT d msgID='%s' %s='%s'%s%s%s%s%s%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'No memory to process incoming data from connection id=% PRINTF_LLFMT d. Connection terminated.%s: Destroyed producer (connid=% PRINTF_LLFMT d, sessid=% PRINTF_LLFMT d, prodid=% PRINTF_LLFMT d) %sConfiguration 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.Refrained from deleting configured durable '%s' even though application's attributes differ from configurationEXPIRE: msgs=% PRINTF_LLFMT d exp=% PRINTF_LLFMT d expd=% PRINTF_LLFMT d int=% PRINTF_LLFMT d tm=% PRINTF_LLFMT dTransaction for non-existent consumer: % PRINTF_LLFMT d connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %sTransaction for non-existent message: % PRINTF_LLFMT d connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s%s: Created producer (connid=% PRINTF_LLFMT d, sessid=% PRINTF_LLFMT d, prodid=% PRINTF_LLFMT d) %sConfiguration 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%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%sRoute configuration error: global queue '%s' from route '%s' collides, global queues must be unique.Removing route '%s', URL='%s': this route is duplicate, creates a loop or has configuration errors%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%sA duplicate durable instance (conn=%s durable=%s dest=%s) was detected, discarding old oneA duplicate connection with same client id (clientid=%s) detected, destroying old conn (conn-id=% PRINTF_LLFMT d)[%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 dDiscarded incoming client message exceeding size limit: connID=% PRINTF_LLFMT d, %s='%s', size=%d.Fault tolerant configurations should have a primary listens marked as ft_active - FT will be disabled.Fault tolerant configurations should have a secondary listens marked as ft_active - FT will be disabled.Warning: file=%s, line=%d: multicast_udp_encapsulation is no longer a supported parameter.Disconnecting connection connID=% PRINTF_LLFMT d, because %s (consid=% PRINTF_LLFMT d) has reached the limit of non-acknowledged messages
Server heartbeat client should be non-zero and no more than a third of the client timeout server connectionServer heartbeat server should be non-zero and no more than a third of the server timeout server connectionClient heartbeat server should be non-zero and no more than a third of the server timeout client connectionConfiguration error: file=%s, line=%d: The processor ID '%d' is greater than '%d', which is the maximum processor ID for this machine
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.
The most likely cause of this error is running out of memory. Shut down tibemsd and see remedies for Out of memory.Initialization of file_destination_defrag feature failed for queue '%s' (store '%s') due to an out of memory condition. Feature is disabled.
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.Correct the durables configuration file to match the durable defined in the meta.db file or administratively delete the durable and re-define it.
A server received an interest notification from another server that does not match the allowed topics in its configuration.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.
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.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.
Warning generated when tibemsd receives a message with a message id that matches another message's message id.
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.
The server encountered an invalid configuration statement in the specified configuration file on the specified line.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 specificationConfiguration 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 existsConfiguration error: file=%s, line=%d: both tibrv_export and tibrvcm_export are specified, ignoring tibrv_exportConfiguration 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 unlimitedConfiguration error: file=%s, line=%d: ignoring invalid max_client_msg_size in the line, reset to unlimitedConfiguration error: file=%s, line=%d: unable to create %s '%s': invalid destination name, invalid parameters or out of memoryConfiguration error: file=%s, line=%d: value of db_pool_size too big or less than allowed minimum, reset to default value of %d bytesConfiguration error: file=%s, line=%d: Ignoring durable, route does not allow clientid, selector or nolocal.Configuration error: file=%s, line=%d: unable to process selector in route parameters, error=%sConfiguration error: file=%s, line=%d: both tibrv_import and tibrvcm_import are specified, ignoring tibrv_importConfiguration 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 parametersConfiguration error: file=%s, line=%d: value of max_msg_memory less than allowed, reset to %dMBConfiguration error: file=%s, line=%d: ignored alias '%s' for factory because such alias already existsConfiguration error: file=%s, line=%d: invalid certificate file name, unknown extension or invalid encoding specificationConfiguration 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 %dSSL Configuration error: file=%s, line=%d: invalid private key file name, unknown extension or invalid encoding specificationConfiguration conflict: file=%s, line=%d: value of msg_pool_block_size already set at line=%d. Ignoring msg_pool_size.Unable to create Rendezvous Certified transport '%s' because it references undefined Rendezvous transport '%s'Configuration error: file=%s, line=%d: invalid value of db_pool_size, reset to default of %d bytesConfiguration error: file=%s, line=%d: invalid value of route_recover_interval, reset to default %dConfiguration error: file=%s, line=%d: out of memory, unable to create Rendezvous transportConfiguration conflict: file=%s, line=%d: Overriding value of msg_pool_size already set at line=%d.Configuration error: file=%s, line=%d: ignoring invalid line in route parameters: invalid zone type, too longConfiguration error: file=%s, line=%d: ignoring invalid line in route parameters: zone name exceeding %d bytesConfiguration error: file=%s, line=%d: value of %s less than allowed minimum of %dKB, reset to unlimitedConfiguration error: file=%s, line=%d: ignoring channel '%s' on topic '%s', channel does not existConfiguration error: file=%s, line=%d: ignoring channel '%s' on topic '%s', overlaps with channel '%s' on topic '%s'Configuration error: file=%s, line=%d: channel '%s', invalid address: group must be in the range 224.0.0.0 to 239.255.255.255Configuration 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 65535Configuration 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 maxEventsConfiguration error: file=%s, line=%d: the discardAmount is too big compared to the maxEvents value. Defaulting to TIBRVQUEUE_DISCARD_NONE policyConfiguration 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 policyConfiguration error: file=%s, line=%d: RV Queue Limit Policy '%s' unknown or not supported. Defaulting to TIBRVQUEUE_DISCARD_NONE policyConfiguration error: file=%s, line=%d: Error parsing the RV Queue Limit Policy value '%s'. Defaulting to TIBRVQUEUE_DISCARD_NONE policyConfiguration 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
A client application's attempt to commit a transaction failed because the server encountered an error during an operation associated with the transaction.Examine previous error statements to determine the cause of the operation failure and correct that before attempting the transaction again.
tibemsd was unable to update one of its configuration files following a configuration change.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.
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
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.Failed to update msg record with record id [% PRINTF_LLFMT d] in store [%s]: [ ESTATUS = %d, ERRSTR = %s ]
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.
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.
Check the configuration of SSL related parameters to make sure that no incompatible ciphers or operations are requested.
Error processing xa end - transaction marked ROLLBACKONLY, %s. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %sProblem trying to recover routed consumer for queue %s: setting recover message. Error: %sHandling of route flow stall recovery request from %s failed: unable to get message property %s: %s
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.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.
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.
An attempt to authenticate a client's userid and password using the external LDAP server failed.Examine the error code printed by the messaging server and consult the manual for the external LDAP server.
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.
A client application attempted to change the state of a transaction that the tibemsd does not have in its list of current transactions.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.Cannot find transaction referred to transaction record update(%d) request. connID=% PRINTF_LLFMT d %sCannot find transaction referred to in xa commit request. connID=% PRINTF_LLFMT d %sCannot find transaction referred to in xa prepare request. connID=% PRINTF_LLFMT d %sCannot find transaction referred to in xa rollback request. connID=% PRINTF_LLFMT d %sReceived prepare request for transaction already prepared. connID=% PRINTF_LLFMT d %sCannot find transaction referred to in xa start (resume) request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %sCannot find transaction referred to in xa start (join) request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %sCannot find transaction referred to in xa end request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
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.
Error sending to consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTd from channel \q%s\q: %sAttached channel \q%s\q to consumer consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTdError attaching channel \q%s\q to consumer consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTdDetaching channel \q%s\q from consumer consid=%PRINTF_LLFMTd connid=%PRINTF_LLFMTdIgnoring additional PGM receiver created on group \q%s\q, dport=%d, sport=%d, channel=%sError: %s is not a valid multicast-capable IP address. Use the -ifc command line parameter to specify a valid interface.
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.No memory trying to process xa end. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %sNo 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.
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.Incorrect xid in xa end (0x%x) request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
A client application's attempt to start an XA transaction failed because the transaction already exists and is not in the correct state.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.Cannot process xa start for a session when another transaction is already active on that session. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %sCannot process xa start with TMNOFLAGS when the transaction is already active. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
Invalid flag in xa end request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %sInvalid flag in xa start request. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %sProblem decoding sequence data in xa end. connID=% PRINTF_LLFMT d sessID=% PRINTF_LLFMT d %s
A non-embedded java client is attempting to connect to a tibemsd that is part of an embedded JMS environment.
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.The recovery process stopped while processing a '%s' record (id=% PRINTF_LLFMT d), error: %d - %s. Check the section 'Error Recovery Policy' from chapter 'Running the EMS Server' in the User's Guide before attempting to restart the serverThe 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 itError occured while processing %s record id=% PRINTF_LLFMT d (%s) - Unable to reconstruct message: %d - %sDiscarding session id=% PRINTF_LLFMT d because the connection id=% PRINTF_LLFMT d was not recovered. Recovery continuesUnable to recreate session id=% PRINTF_LLFMT d with connection id=% PRINTF_LLFMT d: %d - %sUnable to recreate consumer id=% PRINTF_LLFMT d with connection id=% PRINTF_LLFMT d and session id=% PRINTF_LLFMT d: invalid destination: %sDiscarding consumer id=% PRINTF_LLFMT d on destination '%s' because connection id=% PRINTF_LLFMT d was not restored. Recovery continuesDiscarding consumer id=% PRINTF_LLFMT d on destination '%s' and connection id=% PRINTF_LLFMT d because session id=% PRINTF_LLFMT d was not restored. Recovery continuesDiscarding durable id=% PRINTF_LLFMT d (connection id=% PRINTF_LLFMT d) on destination '%s' because the durable name is not specified. Recovery continuesUnable to recreate producer id=% PRINTF_LLFMT d with connection id=% PRINTF_LLFMT d and session id=% PRINTF_LLFMT d: invalid destination: %sDiscarding producer id=% PRINTF_LLFMT d on destination '%s' because connection id=% PRINTF_LLFMT d was not restored. Recovery continuesDiscarding producer id=% PRINTF_LLFMT d on destination '%s' with connection id=% PRINTF_LLFMT d because session id=% PRINTF_LLFMT d was not restored. Recovery continuesUnable to recover ack record (txid=% PRINTF_LLFMT d, consid=% PRINTF_LLFMT d, seqid=% PRINTF_LLFMT d, location=%s): %d - %s
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.
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.
The multi-hop route support of the server does not support configuring a cycle. However, it detected a configuration that would create a cycle.
Unable to create Rendezvous Certified transport '%s' because unable to create Rendezvous transport '%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)A problem occurred while importing RVCM message sequence % PRINTF_LLFMT u from cm sender '%s'. Expecting a redeliveryUnable to queue the request type: %d. Transport '%s', destination '%s', CM Sender '%s', CM Sequence % PRINTF_LLFMT u . Error: %d (%s)Unable to create the timer for the restart of the CM Listener for %s '%s' (RVCM Transport '%s'). Error code: %d '%s'
Seen when tibemsd starts up and detects that the zone for a route as specified in routes.conf has been changed.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.
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.Running on reserve memory, no more send requests accepted. Pending msg count = % PRINTF_LLFMT d
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.The primary EMS server name is %s while the standby EMS server name is %s. The names must be the same
Unable to import SmartSockets message on transport %s: failed to convert reply subject '%s', error=%sUnable 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.Unable to process undelivered SS GMD message, can not register EMS message, error='%s', tport='%s', GMD seq=%dUnable to process undelivered SS GMD message, can not add to undelivered EMS queue, error='%s', tport='%s', GMD seq=%dUnable to process undelivered SS GMD message, failed to build EMS message, error='%s', tport='%s', GMD seq=%dUnable to convert undelivered SS GMD message into EMS message, error='%s', tport='%s', GMD seq=%d
Failed to initialize SSL: can not load certificates and/or private key and/or CRL file(s) and/or ciphers.
The store files specified were created from a different version of EMS that is not supported by this version.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.
Accept() failed: too many open files. Please check per-process and system-wide limits on the number of open files.Could not resolve hostname '%s'. Possibly default hostname is not configured properly while multiple network interfaces are present.
State-modifying action is requested on a transaction for which another such action is being processed.Cannot request second state change for transaction while the first request is in progress (%d, %d) %s.
Most likely, transaction manager error prevented it from advancing this transaction in a timely manner. Verify correct operation of the transaction manner.
Run the server with the -help option and compare it with the command line containing the unrecognized option.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |