Table of Contents
Just a second...

Log messages

The Diffusion™ server outputs log messages. Each log message contains an ID, a message, and a description.

PUSH-000006

Extra JMS header found, ignoring: '{}'.

Description

JMS messages can have user-defined headers as key/value pairs. Diffusion messages are effectively "value" only. To map user headers from Diffusion to JMS there must be an even number of headers. These headers are artificially grouped as key/value pairs in the JMS message.

PUSH-000007

Failed to find topic binding for '{}'.

Description

An attempt has been made to send a reply from the JMS adapter back to the JMS server using the DiffusionReplyTo header, but the adapter was unable to determine the corresponding JMSReplyTo destination.

PUSH-000024

Mime extension '{}' was already mapped to '{}' : overwriting map with '{}'.

Description

A configured Mime extension was already mapped to another value but has now been remapped to a new value. This indicates duplicate mime extension values in the mimes configuration.

PUSH-000026

Requested receive buffer size for HTTP Proxy connection not allocated, requested: {}, allocated {}.

Description

Diffusion tried to set the size of the TCP receive buffer for a socket connection to an HTTP proxy, but the actual number of bytes allocated was different.

PUSH-000027

Requested send buffer size for HTTP Proxy connection not allocated, requested: {}, allocated {}.

Description

Diffusion tried to set the size of the TCP send buffer for a socket connection to an HTTP proxy, but the actual number of bytes allocated was different.

PUSH-000038

Exception caught from TopicDeletionListener '{}' topicDeleted method.

Description

An exception has been thrown from a call to a TopicDeletionListener.topicDeleted method. The exception has been logged but has no other effect.

PUSH-000045

Attempt to queue message '{}' for client {} when ACK timeout has already expired.

Description

An acknowledgement would be queued in response to a message requiring an acknowledgement. However the ACK timeout has already expired. Consider increasing the ACK timeout.

PUSH-000076

Unable to start Connector '{}', permission denied.

Description

The operating system denied permission for a resource used by this connector. Often this relates to reserved ports (less than 1024) on Unix-based operating systems.

PUSH-000080

Non-SSL connection attempted to connector '{}' which only supports SSL-type connections.

Description

An attempt has been made to make a non-secure connection to a connector that is configured to only accept secure connections.

PUSH-000083

Connector '{}' received a client connection but does not support clients.

Description

The given connector is not configured to receive and handle client connections. For example, the connector might be dedicated to event publisher connections.

PUSH-000085

{}: Requested input buffer size could not be allocated, requested: '{}' allocated: '{}'.

Description

The receive buffer of the socket was assigned a different amount of memory than requested. This is configured by the input buffer size. The configured input buffer size is a hint to the operating system. Refer to your OS documentation for any socket buffer limits. This can have performance implications.

PUSH-000086

{}: Requested output buffer size could not be allocated, requested: {} allocated: {}.

Description

The send buffer of the socket was assigned a different amount of memory than requested. This is configured by the output buffer size. The configured output buffer size is a hint to the operating system. Refer to your OS documentation for any socket buffer limits. This can have performance implications.

PUSH-000087

Connector '{}' received an unidentified connection request [{}] from {}.

Description

An unidentified connection attempt has been made via a connector. The hexadecimal representation of the initial bytes of the connection request are logged in order to aid in identifying the origin.

PUSH-000146

Service Request error for client {} on service '{}', request id '{}', error '{}'.

Description

A request from a client to a service topic has failed and it was not possible to report the failure back to the client, possibly because it is closed.

PUSH-000147

Failure in TopicDataListener '{}' topicDataChanged method.

Description

An exception has been thrown by an implementation of the TopicDataListener.topicDataChanged method. The exception is simply logged and has no other effect.

PUSH-000155

No connectors have been configured. Creating default connector listening on port {}.

Description

No connectors have been configured therefore a default connector listening on port 8080 has been created with all default values.

PUSH-000175

SHA1 algorithm not found, unable to respond to WebSocket request.

Description

The WebSocket protocol requires the SHA1 algorithm, but it was not found. This can only happen with an incomplete or incompatible Java installation.

PUSH-000187

Second attempt to write output, try increasing timeout or output buffers '{}'.

Description

Diffusion has tried to obtain a selector for writing and failed and is trying again. If this problem persists, try increasing the write timeout or the output buffer size.

PUSH-000197

Unable to create directory '{}' for the public certificates.

Description

The HTTP service which can be used for updating the license needs to be able to store the license in a directory, but that directory does not exist and cannot be created.

PUSH-000210

License check failed : Unable to parse CIDR Address: '{}'.

Description

The product is licensed to run on machines with IP addresses matching a CIDR expression, but the expression could not be parsed. Contact Push Technology for an updated license file.

PUSH-000228

Multiplexer event is significantly delayed as the queue current size is beyond threshold '{}', capacity = '{}'.

Description

Because the queue is full, a multiplexer cannot queue an event after a significant amount of time, but it is continuing to try to do so.

PUSH-000231

Long multiplexer cycle [cycle {}: processed {} events in {} ms; processed {} clients in {} ms].

Description

A multiplexer processing cycle exceeded the configured notification threshold. On the server, this can be due to subscription processing for many clients. Consider allocating more CPU cores and increasing the number of multiplexers correspondingly.

PUSH-000253

Exception caught in {} method of authorization handler {}.

Description

An exception has been thrown by the specified method of the user-written authorization handler - the exception has been logged and the requested action rejected.

PUSH-000258

Publisher '{}' did not handle server rejected credentials for '{}'.

Description

The default (unimplemented) serverRejectedCredentials method of a publisher has been called because credentials it has sent to a server have been rejected.

PUSH-000262

Error writing file for deployment: {}.

Description

When hot-deploying publishers, the contents of DAR files must be extracted to disk. Check for write permissions to the deployment directory and that there is sufficient free disk space.

PUSH-000264

Exception caught in publisher '{}' in systemStarted method.

Description

Publishers declared in etc/Publishers.xml can be informed that Diffusion is ready by overriding the systemStarted() method. This message is emitted if an exception is thrown by the publisher's systemStarted() method.

PUSH-000266

This DAR file is for Diffusion version {} or greater. Not deploying on Diffusion version {}.

Description

The META-INF/MANIFEST.MF of the DAR file contains the "Diffusion-Version" attribute that specifies with which versions of Diffusion it is compatible. The DAR is marked as incompatible with this version of Diffusion and will not be deployed.

PUSH-000274

DeploymentMonitor: The DAR file '{}' has not been fully undeployed. The publisher(s) {} have not been undeployed. The DAR file will be ignored from now on.

Description

An error occurred during an attempt to undeploy a publisher, which had been deployed using the "hot deploy" feature. This can happen if a DAR contains multiple publishers, but not all of them return "true" from the isStoppable() method.

PUSH-000275

Publisher '{}' received notification of non-acknowledgment of message '{}' by {} clients.

Description

A publisher has received a notification that one or more clients have not acknowledged a message requiring acknowledgment, but the publisher has not implemented the messageNotAcknowledged method to handle it.

PUSH-000289

Stopping Diffusion server due to stop-server-if-not-loaded flag for publisher '{}'.

Description

Diffusion failed to start a publisher which has the "stop-server-if-not-loaded" configuration value set to "true" in Publishers.xml. Diffusion will now be stopped.

PUSH-000293

Publisher '{}' unable to connect to server '{}' - will retry every {} milliseconds.

Description

A publisher server connection cannot be established. The recovery policy indicates that the connection be retried and so an automatic retry will occur at the interval specified.

PUSH-000295

Publisher '{}' not currently deployed, cannot undeploy.

Description

An attempt was made to undeploy a publisher which is not deployed. Either check that this is the case, or that you have the correct spelling of the publisher's name.

PUSH-000296

DeploymentMonitor: One or more of the publishers in '{}' cannot be stopped. Not undeploying file. The DAR file will be ignored from now on.

Description

An attempt was made to undeploy a hot-deployed publisher, but that publisher does not return "true" from its isStoppable() method.

PUSH-000300

Message of size {} is too large for {} which has a limit of {}.

Description

An attempt has been made to send a message to a client that is larger than it is possible to transmit to that client, possibly because of buffer limitations.

PUSH-000332

Thread pool {} queue full - task running in current thread.

Description

Specified thread pool queue has become full and the rejection policy is to run the task in the current thread, which might be inefficient. Consider increasing the pool maximum size.

PUSH-000351

{}: Connection rejected as request was missing the HTTP header field '{}'.

Description

This connection was rejected as it was missing the given HTTP header. The connection is likely not from a Diffusion client, or an intermediary (firewall/load-balancer) has removed the header.

PUSH-000354

{}: cors-origin not defined or invalid. Aborting request.

Description

CORS (Cross Origin Resource Sharing) request has been received by the web server client service but no "cors-origin" has been configured or the configured value was invalid. The request has been aborted.

PUSH-000359

Poll request for client {} from '{}' failed because no matching client session can be found. The client session might have been closed previously. Poll request will be ignored.

Description

The server has received a poll request for an unknown client session. This might be because the client has been closed by the server, or indicate an incorrectly configured load balancer routing an HTTP connection to a server that was not hosting the session. Consider enabling session-stickiness for HTTP clients.

PUSH-000360

FileService [{}]: not adding virtual hosts '{}' mapping to '{}' as it is not a directory.

Description

Failed to add a virtual host to the web server's file service because the configured mapping does not point to a directory.

PUSH-000368

{}: websocket-origin not defined or invalid. Aborting request.

Description

Web Server Client Service has received a Web Socket request but "websocket-origin" has not been configured or is invalid. The request has been aborted.

PUSH-000391

Server connection '{}' for Publisher '{}' loaded SSL keystore '{}'.

Description

A publisher has created a server connection that has loaded a keystore to establish the SSL context. The keystore is used to securely store key, certificate, and trust information.

PUSH-000394

Publisher '{}' has lost connection to server '{}' - will retry every {} milliseconds.

Description

A publisher has lost connection to a server and the recovery policy is to retry therefore a retry will occur at the specified interval.

PUSH-000397

Deploying publishers in DAR file '{}'.

Description

Deploying the publishers in a single DAR file. There can be multiple publishers in a single DAR file. The publishers will be extracted from the DAR file and the additional configuration files loaded.

PUSH-000399

Directory '{}' does not exist or is not a directory. Using '{}' as a log directory.

Description

The directory of a log definition or the default log directory does not exist or it is not a directory. In this case the temporary file directory is used instead. This is specified by 'java.io.tmpdir'. If the intended directory does exist the problem might be that the relative path is incorrect because the working directory is not what you expect. The simplest way to resolve this is to use absolute file paths to reference log directories. This message might be shown when the log is created and when checking if it needs to be rotated.

PUSH-000404

'{}': No poll has been opened by client within poll timeout.

Description

HTTP-based connections require an open polling connection to receive messages. If the client has no open polling connection for a fixed period, the client will be closed as unresponsive.

PUSH-000408

A response was received from a peer for a finished or unknown conversation and ignored. [cid={} response={}].

Description

A response with an unknown conversation ID has been received from a peer. Typically this indicates the conversation has timed out or an exception was thrown earlier in the conversation. It can also for a session using an earlier client library that does not support reliable reconnection if it sends or receives a response from the server that was queued before reconnection.

PUSH-000411

Multiplexer undefined. The PublisherServerConnection '{}' might not be connected.

Description

The publisher server connection attempted to send with a null multiplexer. This might be due to the PublisherServerConnection not being connected.

PUSH-000417

Fetch operation {} for {} was aborted due to missing responses for the following topics: {}.

Description

A fetch operation failed, possibly because of an issue at the publisher or state providing client. Look for earlier messages in the server log.

PUSH-000422

Received request from client {} to set conflation for client {} to '{}'. The client session does not exist.

Description

The server has received a request from a client to change the conflation setting for an unknown client session.

PUSH-000424

Received request from client {} to throttle message queue for client {} using the {} policy, limit={}. The client session does not exist.

Description

The server has received a request from a client to change the throttling policy of an unknown client session.

PUSH-000428

'{}': Has rejected an attempt to connect from a Unified API client. Unified API clients are not supported by this connector.

Description

The connector has been configured to accept connections only of certain client types. An attempt was made to connect by a client of an unsupported type. Either the connector is configured for the wrong type, the client should have connected to a different connector, or an attempt was made to connect a client that has greater functionality than you allow on this connector.

PUSH-000429

'{}': Has rejected an attempt to connect from a Classic API client. Classic API clients are not supported by this connector.

Description

The connector has been configured to accept connections only of certain client types. An attempt was made to connect by a client of an unsupported type. Either the connector is configured for the wrong type or the client should have connected to a different connector.

PUSH-000436

Unable to create file handler for logger '{}'. Log messages will still appear in the console.

Description

A file handler was unable to be created for the requested logger. Messages will continue to be logged to the console, but will not be recorded to their own file.

PUSH-000437

A message has been received with an unknown topic alias '{}'. It cannot be parsed.

Description

When topic aliasing is enabled a short alias is used to replace topic names. This reduces the size of messages sent. A client still needs to know the topic name so the topic name and alias are sent together in the topic load. If a client does not receive a topic load it is unable to handle the deltas with only the alias. Diffusion assumes that a client will receive a topic load message if a load message is created for that topic. If the message is not sent, this error message will be logged.

PUSH-000443

Publisher '{}' returned null for fetch of topic '{}', indicating an asynchronous response. This is not supported by the client {}. The fetch response (if any) will be discarded.

Description

The client does not support asynchronous fetch responses from a publisher.

PUSH-000445

Discarding WhoIs request for {} due to backlog. There are currently {} pending requests.

Description

A WhoIs request has been discarded because there is currently a large number of pending requests. The WhoIsListener will be notified with basic locale information based on the caller's IP.

PUSH-000465

Connector '{}' has pings disabled. Unresponsive HTTP clients will not be detected.

Description

The server relies on pinging in order to detect unresponsive HTTP clients. Unresponsive clients might go unnoticed if the ping frequency is not set.

PUSH-000477

Configurations that specify only control authentication handlers are invalid.

Description

If a control authentication handler is configured, you must also configure a local authentication handler (such as the system authentication handler) to allow a client that registers a control authentication handler to connect.

PUSH-000479

Recovery of {} after a write error failed - store must be manually recovered from backup.

Description

Writing of a store file failed and automatic recovery from backup was attempted but also failed. In this event the store has been disabled and must be recovered manually from the backup file.

PUSH-000480

Recovery of "{}" required as backup "{}" exists.

Description

A store backup file has been found which suggests that recovery of the named store might be required. Inspect the store file and replace it with the backup if necessary, and then delete the backup.

PUSH-000484

Failure to forward message from {} to {} for topic {}.

Description

The server failed to forward a message from a client to a client that handles messages for the given topic path. The message might have been delivered. See the log for further information.

PUSH-000498

Connector '{}' has received data on {} that has not come from a proxy.

Description

The connector has been configured to require all connections use a proxy protocol but a connection has been made that has not provided proxy information.

PUSH-000525

Routing-property {} absent from message.

Description

To relay a message to an individual Diffusion client a "server-name/sessionId" expression must be retrieved from a JMS header or property. The configured header/property is absent from this message.

PUSH-000531

Topic.publishMessage() methods should not be used for topics with topic data, but topic '{}' is of type '{}'. This operation will fail in a future release. This message is logged for the first occurrence only.

Description

Topics with topic data should be updated using the PublishingTopicData API because Topic.publishMessage() does not update the topic data. Calling Topic.publishMessage() for a topic with topic data will not be supported in future releases.

PUSH-000534

Routing subscription for client {} to routing topic '{}' failed because no topic exists with resolved topic path '{}'.

Description

A routing topic failed to subscribe a client to a topic because the handler returned an unknown topic path.

PUSH-000538

Fan-out connection will attempt to connect to '{}' again every {} milliseconds.

Description

A fan-out connection to a primary server could not be established or has been lost and will now try to connect again at the specified interval.

PUSH-000545

Fan-out link '{}' can not replicate topic '{}' as it is of type '{}' which is not supported.

Description

A topic has been encountered within the specific link of a fan-out connection which cannot be replicated as it is of a type that is not supported for fan out. The topic will be ignored and will not be created locally.

PUSH-000550

Both rotate-daily element and rotation-period attribute are defined. Only the rotation-period will be used.

Description

Both rotate-daily element and rotation-period attribute are defined in the Log.xml. The rotation-period attribute overrides the daily-rotate element.

PUSH-000553

Multiplexer blocked because it has a maximum-sized batch of {} notifications to deliver to the publisher(s) {}.

Description

A multiplexer has encountered a severe backlog dispatching publisher notifications. The notifications will be delayed. This message indicates the publishers cannot keep up with the rate of notifications. The server may be overloaded or the publisher may be blocked.

PUSH-000554

Delayed dispatch of {} notifications because the notification queue for publisher '{}' is full.

Description

A publisher is failing to keep up with the rate of multiplexer notifications. The server may be overloaded or the publisher may be blocked.

PUSH-000555

Outbound message queue for '{}' is full. Queue details: {}.

Description

The number of messages in the outbound queue for a session has reached the configured limit. The session will be closed. This can indicate problems with the network performance or the receiving process.

PUSH-000561

PublishingTopicData.publishMessage() methods called without an update block for topic '{}' of type '{}'. This operation will fail in a future release. This message is logged for the first occurrence only.

Description

PublishingTopicData.publishMessage() should be combined with an update to the topic data. Calling this method outside an update block will not be supported in future releases.

PUSH-000562

Multiplexer configuration using deprecated method. Define multiplexer using <multiplexer> instead of <multiplexers>.

Description

The <multiplexers> element in Server.xml is deprecated. Use <multiplexer> to configure your multiplexer.

PUSH-000563

A message could not be sent to client as it is not subscribed to the topic {}.

Description

A classic client can only receive messages on a topic to which it is subscribed. Either the publisher aborted the subscription, or the topic or client has been deleted.

PUSH-000567

Memory to calculate delta message exceeds limit of {} bytes - the full message will be used.

Description

A binary difference calculation failed because insufficient memory was available. This is a rare condition that only occurs when there are many differences between two huge messages.

PUSH-000569

Unable to apply the message of type '{}' received from the data grid to topic '{}'.

Description

The server received data from the data grid that it was able to process as a topic message but the message could not be published on its topic. A stack trace describing the problem with publication is provided.

PUSH-000570

Unable to process data received as a message of type {}.

Description

The server received data from the data grid that it is unable to process as a Diffusion topic message. Either there was a problem with the data sent or a message of the wrong type was sent.

PUSH-000573

Fan-out client {} registration for paged topic update registrations has failed : {}.

Description

A fan-out client has been unable to register for paged topic update notifications and therefore no updates to paged topics can be applied.

PUSH-000587

The value of {} ms configured for '{}' is excessive and has been limited to {} ms.

Description

The maximum value of the connect and write timeouts has been limited. A future version of Diffusion will enforce the new limits by failing to accept configurations with excessive values.

PUSH-000588

The connection activity monitor has detected that the connection '{}' has been idle and it has been closed, attempting to recover.

Description

Clients can use a connection activity monitor to listen for the system ping sent by the server. If the expected system pings are not received the connection will be closed and the client will enter a recovery state.

PUSH-000591

Both file-append and a rotation setting have been configured for the log files. File-append will be used.

Description

Both file-append and a rotation setting (either rotate-daily element and rotation-period attribute) have been configured in the Logs.xml configuration file. The logs will be appended, i.e. only one log file will be output.

PUSH-000597

Unable to recover the session {} from the data grid.

Description

During session fail over Diffusion updates the data grid and recovers information from it. This update or recovery did not succeed both the data grid and the session may have stale information. See the exception for more information on the cause of the failure.

PUSH-000598

Unable to remove sessions from the data grid.

Description

A server failed and the sessions did not fail over within the timeout. The sessions were not removed from the data grid. They will continue to take up memory in the data grid. See the exception for more information on the cause of the failure.

PUSH-000599

Unable to remove session {} from the data grid.

Description

The session has been closed but not removed from the data grid. It will continue to take up memory in the data grid. See the exception for more information on the cause of the failure.

PUSH-000601

Failed to replicate change to session {}.

Description

An attempt to update the data grid with changes to a principal, properties or subscription level of a session failed. The data grid may have stale information. See the exception for more information on the cause of the failure.

PUSH-000602

Unable to replicate change to session principal, properties or subscription level for session {}. The session could not be found.

Description

An attempt was made to update the data grid with changes to the principal, properties or subscription level of a session but the session was unknown.

PUSH-000603

Unable to replicate change to topic selections for session {}.

Description

An attempt to update the data grid with topic selections for a session failed. The data grid may have state information. See the exception for more information on the cause of the failure.

PUSH-000614

Failed to register topic update source for path {} by session {} because of an unchecked exception.

Description

While registering an update source with the distributed update source registry an unchecked exception was thrown. This may have happened on a different member of the cluster.

PUSH-000616

Failed to remove update source {} from distributed update source registry.

Description

While removing an update source from the distributed update source registry an unchecked exception was thrown. This may have happened on a different member of the cluster.

PUSH-000618

Input queue for inbound thread '{}' of size {} overflowed due to large number of connections. Risk of deadlock.

Description

The queue of work for an inbound thread overflowed. To avoid the risk of deadlock, reconfigure the inbound pool to have a queue at least as large as the number of concurrent connections.

PUSH-000622

Unsupported service {} requested by peer {}.

Description

The peer has requested an unsupported internal service. This can be due to a version mismatch between client and server. Some services are not unsupported for deprecated network protocols.

PUSH-000625

Session {} has received a message for path '{}', but has registered no streams that match that path.

Description

A session has received a message from the server that cannot be delivered because the application has not registered any matching streams.

PUSH-000626

Session {} has received a message for path '{}' but is not using the Messaging feature so has no registered streams that match that path.

Description

A session has received a message from the server that cannot be delivered because the application is not using the Messaging feature.

PUSH-000627

Failed to redeliver missing topic notification for subscription or fetch to selector '{}' by session '{}' after {} attempts.

Description

Redelivery of a missing topic notification has been canceled after retrying a number of times.

PUSH-000628

Handler {} callback method threw an exception.

Description

A handler callback raised an exception when called. If the handler was open it has been closed with the CALLBACK_EXCEPTION ErrorReason. See the log for more information.

PUSH-000631

Failed to propagate missing topic notification for subscription or fetch to selector '{}' by session '{}' because there is no connection to primary server '{}'.

Description

Fan-out propagation of a missing topic notification failed because the primary server is disconnected.

PUSH-000633

Failed to redeliver missing topic notification for subscription or fetch to selector '{}' by session '{}' because there is no longer a suitable registered handler.

Description

Redelivery of a missing topic notification has been canceled by the server because there is no longer a registered handler.

PUSH-000642

Allocating larger buffer to accommodate a message larger than the default configured input buffer size. Consider increasing the input buffer size for channel {}.

Description

Client has sent a message larger than the input buffer size.