Log messages
The Diffusion™ server outputs log messages. Each log message contains an ID, a message, and a description.
PUSH-000001
Attempt #{} to reconnect to JMS Server.
Description
The JMS adapter is currently disconnected from a JMS server and has just failed another attempt to reconnect.
PUSH-000002
Cannot stop the JMSAdapter.
Description
Something went wrong during initialization of the JMS adapter, and there was an error when trying to clean up and stop the adapter.
PUSH-000003
Couldn't find JMSReplyTo destination: '{}'.
Description
An attempt has been made to send a message with a JMSReplyTo destination, but the JMS adapter cannot create the ReplyTo destination on the JMS server.
PUSH-000004
Discarding non-TextMessage from JMS: '{}'.
Description
The JMS adapter only supports TextMessage types but it received another message type.
PUSH-000005
Exception from JMS provider '{}'.
Description
The JMS adapter received notification of an exception from the JMS server. Typically, this happens when the connection between the adapter and the server has been terminated.
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-000008
Failed to generate delta message '{}'.
Description
A message has been received from the JMS server and a delta message needs to be sent, but the update or publish of the topic data associated with the Diffusion topic failed.
PUSH-000009
Failed to generate ITL message '{}'.
Description
An error occurred while generating an ITL message for a client after a message has been received from a JMS queue.
PUSH-000010
Failed to get message content of message to JMS, topic is '{}'.
Description
Failed to read/parse the content of a Diffusion message while translating it to a JMS message for sending.
PUSH-000011
Failed to send message to JMS destination '{}'.
Description
An error occurred while sending a message from the JMS adapter to the JMS server.
PUSH-000012
Failed to start JMS Adapter.
Description
The JMS adapter was unable to start.
PUSH-000013
Maximum number '{}' of reconnection attempts reached, JMSAdapter disconnected.
Description
The adapter has exhausted the maximum number of configured connection attempts with the JMS server and has given up.
PUSH-000014
Received TextMessage for unknown destination: '{}'.
Description
A message was received by the JMS adapter from the JMS server, but the adapter was unable to determine which Diffusion topic to map the message to.
PUSH-000015
JMS Server disconnect detected, attempting reconnection.
Description
The JMS server has been disconnected from the JMS adapter and the adapter is attempting to reconnect.
PUSH-000016
JMS Server reconnected after '{}' attempts.
Description
The JMS adapter has managed to (re)connect to the JMS server.
PUSH-000017
Unable to create a subscription to '{}', exception is {}.
Description
The JMS adapter failed to create a subscription to the JMS destination associated with the given topic name.
PUSH-000018
Unable to create new topic '{}'.
Description
The JMS adapter has received a message from the JMS server and needs to create a corresponding Diffusion topic, but was unable to.
PUSH-000019
Unable to extract headers from JMS message: '{}'.
Description
Something went wrong while attempting to convert JMS message headers to Diffusion message headers.
PUSH-000020
Unable to get payload from JMS message '{}'.
Description
The JMS adapter has received a message from the JMS server, but is unable to read the content.
PUSH-000021
Unable to restart JMS Server connection.
Description
After an exception from the JMS server, the JMS adapter attempted to reconnect but was unable to.
PUSH-000022
Exception has been thrown by the ServerAckListener.messageNotAcknowledged method of {}.
Description
The specified listener methods has thrown an exception which has been logged but otherwise ignored.
PUSH-000023
Client Auto Failover failed.
Description
A connection to a server has failed, and the auto failover process has encountered an error.
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-000025
Connection attempt failed with {} - trying next server.
Description
An attempt to connect to a server has failed but more than one possible server has been specified and so the next is being tried.
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-000028
An exception has been thrown by the {} method in {}.
Description
An exception has been thrown by an implementation of the specified listener interface. The exception is logged but has no further impact.
PUSH-000035
Unable to send fetch reply to Client {}.
Description
An error occurred while sending a fetch reply message back to a client.
PUSH-000036
Failure fetching state from '{}' of '{}'.
Description
While handling a fetch request for a topic with topic data, an error occurred while generating a topic load message.
PUSH-000037
Subscription Handler '{}' specified for Routing Topic '{}' - ignored.
Description
A subscription handler has been specified for a routing topic which is not allowed therefore the handler has been ignored.
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-000039
Exception caught from TopicTreeListener '{}' {} method.
Description
An exception has been thrown from a call to a TopicTreeListener method. The exception has been logged but has no other effect.
PUSH-000040
WhoIs connection failure limit exceeded - not resolving.
Description
Five attempts to connect to the WhoIs have failed. There will be no WhoIs service.
PUSH-000041
Failure to connect to WhoIs provider at {}:{} - will retry 5 times.
Description
Unable to connect to the WhoIs provider indicated. The connection will be attempted up to five times before giving up.
PUSH-000042
Failed to enumerate files in usr.lib directory '{}'.
Description
An error has occurred while traversing the files within the given directory.
PUSH-000043
Attempted to load duplicate jar file '{}'.
Description
An attempt was made to load the given file more than once.
PUSH-000044
Entry '{}' in server configuration is not a directory.
Description
The given file system name must identify a directory.
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-000046
Client {} closing - {}. {}.
Description
A client session was closed.
PUSH-000047
Client {} closing - {}. {}.
Description
The given client is closing due to an exception.
PUSH-000049
Error subscribing client {} to topic '{}', publisher '{}'.
Description
An error has occurred while trying to subscribe the specified client to the specified topic.
PUSH-000050
Client {} sent command message to topic '{}' which does not have command-based topic data. Message is '{}'.
Description
Command messages can only be processed by topics with related command-based topic data.
PUSH-000051
Failed to apply client change event : '{}'.
Description
An error occurred while applying a change to the given client.
PUSH-000052
Exception in ACK listener '{}' messageNotAcknowledged method.
Description
An error occurred while informing a listener that a dispatched message has not been acknowledged.
PUSH-000054
Client {} tried to fetch invalid topic selector '{}'.
Description
The topic selector expression supplied by a client for a fetch request was invalid.
PUSH-000055
Client group "'{}'" failed to send message to '{}'.
Description
In sending a message to a client group, transmission to the given individual client encountered an error.
PUSH-000056
User licence limit breached, connection rejected.
Description
The maximum number of licensed connections has been exceeded.
PUSH-000057
Server is not licensed to accept distributed connections.
Description
This Diffusion server is not licensed to accept connection from other Diffusion servers.
PUSH-000058
Server is not licensed to accept mobile connections.
Description
The licence does not allow for Diffusion Mobile-to-Server connections.
PUSH-000061
Failed to subscribe client {} to topic(s) '{}' - Invalid topic name or selector.
Description
The client sent an invalid topic selector pattern for subscription.
PUSH-000062
Failed to schedule future close of client session {}.
Description
It was not possible to schedule the future close of a client session that is awaiting reconnection.
PUSH-000064
Failed to unsubscribe Client {} from '{}' - Invalid Topic name or selector.
Description
The client sent an invalid topic selector pattern for unsubscription.
PUSH-000065
Failure processing message from server.
Description
An error has occurred at the client end of a connection to a server while processing a message from the server.
PUSH-000070
Invalid connection from '{}'.
Description
An invalid connection has been attempted from the given address.
PUSH-000072
Connector '{}' created for connections of type {}, listening on {}.
Description
The given connector was created to support the given types of connection.
PUSH-000074
Connector '{}' received an HTTP connection but does not support HTTP.
Description
Connector has received an HTTP connection attempt but does not support HTTP connections. The connector does not define a valid web server.
PUSH-000075
Unable to start Connector '{}'.
Description
An error occurred while trying to start a connector.
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-000077
HTTP Method '{}' is not supported in request from '{}'. Request: '{}'.
Description
An HTTP client has requested a method that is not supported by Diffusion.
PUSH-000078
HTTP Processing error, request from '{}'.
Description
An error occurred in the processing of an HTTP request from the given client.
PUSH-000079
Connector '{}' received a Policy File request which is not supported.
Description
Connector has received a policy file request but does not support such requests. The connector does not have a policy file configured.
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-000081
Connector '{}': no connection - SSL handshake error.
Description
A secure (SSL) connection was attempted but the SSL handshake failed.
PUSH-000082
SSL connection attempted but connector '{}' does not support SSL.
Description
An attempt has been made to make a secure (SSL) connection via a connector that does not support SSL. The connector does not define a keystore.
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-000089
Failed to update Child List Topic Data for Topic '{}'.
Description
An unforeseen error occurred while updating this ChildListTopicData.
PUSH-000090
An exception has been thrown from CustomTopicDataHandler.{} method.
Description
The custom TopicData implementation threw an exception in the given method.
PUSH-000091
Client {} sent invalid topic selector pattern '{}' to Topic Notify Topic.
Description
A client has sent an invalid topic name or selector pattern to a topic notify topic selection.
PUSH-000092
An exception has been thrown from TopicNotifyTopicListener.{} method in '{}'.
Description
The topic notify topic listener threw an exception in the given method.
PUSH-000093
Topic Notify Select Request Mode '{}' from Client {} is invalid.
Description
Client has sent an invalid select request mode to a topic notify topic.
PUSH-000094
{} was unable to notify Client {} of Topic '{}' notification event - Client closing.
Description
A failure has occurred notifying a client of a topic addition, removal or update - the client will be closed.
PUSH-000095
Unrecognised notification type '{}'.
Description
The notification request holds unexpected content.
PUSH-000097
Paged topic '{}' Unable to process command '{}' from client {}.
Description
A paged topic was unable to process a command from a client.
PUSH-000098
Failure sending a paged topic status message to client {}.
Description
A failure occurred while sending a paged topic status message to the specified client.
PUSH-000099
Failure sending a paged topic update message to client {}.
Description
A failure occurred while sending a paged topic update message to the specified client.
PUSH-000100
Command topic data '{}': received invalid command message '{}'.
Description
A client has sent an invalid command message to command topic.
PUSH-000142
Error removing routing data {} from {}.
Description
A failure occurred while trying to remove a topic from a routing topic.
PUSH-000144
Routing topic failed to subscribe client {} to routing topic '{}' with target topic '{}'.
Description
A routing topic failed to subscribe a client to a topic.
PUSH-000145
An exception has been thrown from ServiceTopicListener.{} method in '{}'.
Description
The service topic listener threw an exception in the given method.
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-000150
Message '{}' received from '{}' by '{}' has not been handled.
Description
A command topic that does not handle messages from clients has received a message from a client and ignored it.
PUSH-000151
Unable to get JMX MBean attribute.
Description
It was not possible to retrieve an attribute from a JMX MBean.
PUSH-000152
Unable to load shutdown hook class '{}': {}.
Description
An error occurred loading the given third party class.
PUSH-000153
Unable to load startup hook class '{}': {}.
Description
An error occurred loading the given third party class.
PUSH-000154
Caught JVM shutdown.
Description
The JVM shut down unexpectedly.
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-000156
No multiplexer configuration. Creating default configuration.
Description
No multiplexer configuration has been found therefore a default multiplexer configuration will be assumed.
PUSH-000157
No queue definitions configured. Creating DefaultQueue.
Description
No queues have been configured therefore a default queue definition has been assumed.
PUSH-000158
No thread pools configured. Created new pool definition called '{}'.
Description
No thread pools were configured therefore a default one has been added.
PUSH-000159
The maximum message size is {} bytes.
Description
The maximum message size has been established.
PUSH-000160
No inbound pool has been configured - using '{}'.
Description
No inbound thread pool has been configured therefore the first configured thread pool has been assumed to define the inbound pool.
PUSH-000161
Diffusion - removing publishers.
Description
The server is exiting, and all publishers within are being unloaded.
PUSH-000162
Running shutdown hook '{}'.
Description
The given third party class is being executed at server shutdown.
PUSH-000163
Running startup hook '{}'.
Description
The given third party class is being executed at server startup.
PUSH-000164
Diffusion server not started.
Description
Diffusion server failed to start.
PUSH-000165
Diffusion server started.
Description
Diffusion started successfully.
PUSH-000166
Diffusion server '{}' starting.
Description
The Diffusion server is starting.
PUSH-000167
Diffusion stopped.
Description
The Diffusion server has been stopped.
PUSH-000168
Diffusion stopping, reason='{}' by administrator='{}'.
Description
Diffusion is processing a shutdown request.
PUSH-000169
Diffusion - stopping connectors.
Description
Connectors are being stopped during a shutdown of Diffusion.
PUSH-000173
Exception notifying '{}' of '{}'.
Description
An exception occurred while processing an internal asynchronous event.
PUSH-000174
Unable to submit event '{}' to '{}' for execution.
Description
A failure has occurred while submitting a notification event for execution.
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-000177
Received invalid message '{}' from '{}': {}.
Description
The server module dealing with Introspector clients has received an invalid message.
PUSH-000178
Exception publishing message on topic '{}'.
Description
The server module dealing with Introspector clients caught an exception sending a message to the given client.
PUSH-000180
Topic '{}' might not be removed by Introspector for client {}.
Description
The given client has attempted to remove a topic that cannot be removed.
PUSH-000181
Topic '{}' not removed for client {}: {}.
Description
The given topic was not removed for the given client and reason.
PUSH-000182
Topic '{}' removed by Introspector client {}.
Description
The given topic was removed for the given client.
PUSH-000183
Message channel '{}' closed - {}.
Description
A communication error has occurred on a message channel.
PUSH-000185
Failed to accept connection on connector '{}'.
Description
This can occur when a socket connection has been made to Diffusion, but a failure occurred while initializing it.
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-000188
Shutting down selector '{}' due to fatal error.
Description
An error has occurred in a selector thread and the selector will be shutdown.
PUSH-000190
SSL read error.
Description
An error occurred while decoding SSL-wrapped data.
PUSH-000191
Connector '{}:' - Unable to accept connection: {}.
Description
An exception occurred while attempting to accept a socket connection.
PUSH-000193
SSL Keystore loaded from '{}'.
Description
SSL keystore has been loaded from the specified location.
PUSH-000194
JMX cannot expose '{}' as a topic as dimensions exceed {}.
Description
A limited number of dimensions to an arrays can be mirrored to a topic.
PUSH-000195
JMX: Cannot register object '{}' at MBean ObjectName '{}'.
Description
An error occurred registering the given object with the given JMX ObjectName with the JMX server.
PUSH-000196
'{}:' failed to update Diffusion license.
Description
An error occurred while attempting to update the license file.
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-000198
Licence is invalid.
Description
The license is invalid.
PUSH-000199
License is not valid for this version of Diffusion (license='{}' vs '{}').
Description
The license file does not match this version of Diffusion.
PUSH-000200
Product '{}' not licensed for this address scheme.".
Description
A product is not licensed for either IP address or MAC addressing schemes.
PUSH-000201
Soft user limit ({}) for {} exceeded. Hard limit at {}.
Description
Once the number of connections for a product reaches its soft limit, a warning is emitted. The product might cease to function if this number reaches the hard limit.
PUSH-000202
Product license expires in {} day(s).
Description
The installed license file is nearing expiration. A new license will be required soon for Diffusion to continue running.
PUSH-000203
License has expired.
Description
The Diffusion license has expired.
PUSH-000204
License hard user limit ({}) for {} exceeded.
Description
Once the number of client connections has reached or exceeded a the hard limit, the product might be disabled.
PUSH-000205
Licence for Introspector has expired.
Description
Licence for Introspector has expired.
PUSH-000206
Licensor stopping Diffusion. Invalid license.
Description
The Diffusion license is invalid.
PUSH-000207
License check failed : Unable to check server-side addressing for product [IP] '{}'.
Description
During the license check, Diffusion attempts to check the server's IP addresses but it was unable to do so.
PUSH-000208
License check failed : Unable to check server-side addressing for product [MAC] '{}'.
Description
Diffusion is licensed to run on a server with a specific MAC address, but an error occurred while looking for MAC addresses on the server.
PUSH-000209
License check failed : Unable to match MAC address for ['{}'].
Description
The product is licensed for a particular MAC address, but the server does not have this MAC.
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-000211
License version is empty, this is not allowed.
Description
License version is empty, this is not allowed. Contact Push Technology for a replacement license file.
PUSH-000212
Log level set to '{} for '{}'.
Description
The logging level of the specified log file has been changed as indicated.
PUSH-000214
Invalid JMX credentials.
Description
The supplied JMX credentials are incorrect.
PUSH-000215
Remote JMX management service is disabled.
Description
The remote JMX service is configured not to start.
PUSH-000216
Remote JMX management service has started. Listening to {}.
Description
The remote JMX service has started.
PUSH-000226
Multiplexer error while processing client {}.
Description
A multiplexer tried to send messages for a client, but failed.
PUSH-000227
Multiplexer event is delayed as the queue current size is beyond threshold '{}', capacity = '{}'.
Description
A multiplexer cannot queue an event because the queue is full, but is continuing to try to do so.
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-000229
Error while handling a multiplexer event.
Description
Error while handling a multiplexer event.
PUSH-000230
Failed to schedule event.
Description
A multiplexer tried to schedule an event for some time in the future, but was not able 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-000232
No multiplexers configured.
Description
No multiplexer definitions have been configured so a default has been assumed.
PUSH-000233
Multiplexer '{}' started.
Description
A multiplexer has started.
PUSH-000234
Properties loaded: '{}'.
Description
The specified properties file has been loaded.
PUSH-000235
Properties reloaded: '{}'.
Description
The specified properties file has been reloaded.
PUSH-000236
Cannot establish JMX attribute '{}' for MBean '{}'.
Description
The given MBean/Attribute pair is not supported by Diffusion.
PUSH-000239
Cannot create topic for MBean {}.
Description
It was not possible to create a topic to mirror the content of the given JMX MBean.
PUSH-000241
Cannot remove topic for MBean {}.
Description
It was not possible to remove a topic that mirrors the content of the given JMX MBean.
PUSH-000242
JMX configuring property '{}'={}.
Description
The JMX Adapter configuration is being applied.
PUSH-000244
JMX exception interacting with MBean '{}'.
Description
An error occurred creating the tree of topics to represent a JMX MBean.
PUSH-000245
JMX exception while updating topic '{}'.
Description
An error occurred while polling an MBean attribute that the given topic reflects.
PUSH-000246
Caught exception removing notification listener from JMX '{}'.
Description
Diffusion is no longer listening to notification from the given MBean, and this has caused a problem.
PUSH-000247
Cannot find MBean '{}' to listen for notifications.
Description
Diffusion is attempting to add a notification to the given MBean, and this has caused a problem.
PUSH-000249
Cannot send message given notification object {}.
Description
A JMX notification was detected and serialized as a message, but it was not possible to send the message.
PUSH-000250
Unexpected notification object '{}'.
Description
A JMX notification of an unexpected type was detected.
PUSH-000251
Unexpected notification type '{}'.
Description
MBeanServerNotification received that was neither about an MBean registering or deregistering.
PUSH-000252
Unable to construct topics for DiffusionPublisher Log Handler.
Description
The Diffusion publisher log handler encountered an error trying to create its topics.
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-000254
Authorization manager started with authorization handler class '{}'.
Description
Authorization manager has been started with the specified handler class.
PUSH-000255
Publisher {} connected to server {} as {}.
Description
A publisher has successfully connected to another Diffusion server as a client.
PUSH-000256
Deploying publishers compiled for Diffusion version '{}'.
Description
Publishers compiled for the specified version of Diffusion are being deployed.
PUSH-000257
Publisher '{}' did not handle message from server '{}'.
Description
A publisher has received a message from a server but has not provided an implementation for the messageFromServer method.
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-000260
Diffusion-Version not present in manifest file, not deploying.
Description
The publisher will not be deployed because Diffusion-Version is not present its DAR manifest file.
PUSH-000261
Error deploying publisher from file '{}'.
Description
An exception has occurred while trying to deploy a publisher from a DAR file.
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-000263
Exception caught in publisher '{}' in method '{}'.
Description
A publisher implementation has thrown an exception in the given method. The exception has been logged but otherwise ignored.
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-000265
Failed to load publisher '{}'.
Description
Diffusion was unable to load a publisher, probably because of a problem with the publisher's configuration files.
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-000267
Introspector publisher defined, but not licensed.
Description
Diffusion is attempting to start the publisher which is required for the Introspector, but the license file does not allow the Introspector to be run.
PUSH-000268
Publisher '{}' is not stoppable, not undeploying.
Description
An attempt has been to undeploy a publisher, but its isStoppable() method returns false. The publisher will not be undeployed.
PUSH-000269
JMX adapter threw exception while starting.
Description
An unexpected exception prevented the JMX adapter from starting.
PUSH-000270
Configured not to poll MBeans.
Description
The JMX adapter is configured not to poll those JMX MBean attributes with a matching topic subscription.
PUSH-000272
Polling MBeans every {} milliseconds.
Description
The JMX adapter is configured to configured to poll required MBean attributes for the given frequency.
PUSH-000273
JMX adapter starting.
Description
The JMX adapter has begun construction.
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-000282
Removed publisher '{}'.
Description
The given publisher has been removed from the server.
PUSH-000283
Publisher to server connection '{}' closing due to send failure: {} {}.
Description
A connection between a publisher and a Diffusion server is being closed due to a failure while sending messages to the server.
PUSH-000284
Publisher '{}' unable to connect to server '{}' - no recovery policy specified.
Description
A publisher server connection has failed to connect and no recovery policy has been specified.
PUSH-000285
Started publisher '{}'.
Description
A publisher has been started.
PUSH-000286
Starting publisher '{}'.
Description
A publisher is starting.
PUSH-000287
Failed to start statistics handler for publisher '{}'.
Description
A failure has occurred while trying to start the statistics handler for the specified publisher.
PUSH-000288
Stopped publisher '{}'.
Description
The given publisher has been stopped, and can be restarted.
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-000290
Failure fetching state of {} from publisher {}.
Description
While handling a fetch request for a topic with no topic data, an error occurred while generating a topic load message.
PUSH-000292
Publisher server connection {} encountered an unexpected error while sending - closing.
Description
A publisher server connection encountered an unexpected error while sending and will be closed.
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-000294
Failed to read DAR file '{}'.
Description
Diffusion tried to deploy a publisher from a DAR file, but the DAR was unreadable. Check file permissions and for corruption with the "jar" tool.
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-000298
No queue definitions configured : Adding DefaultQueue.
Description
No queue definitions have been configured therefore a default queue configuration is being assumed.
PUSH-000299
A conflation merge error has occurred in '{}'.
Description
An instance of MessageMerger has thrown an exception from its merge method. The exception is logged and no conflation occurs.
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-000301
Default queue definition {} does not exist. '{}' used.
Description
There is no configured queue definition with the name as specified as the default queue therefore the first configured queue is assumed to be the default.
PUSH-000302
Default queue definition not configured. '{}' used.
Description
No default queue definition has been specified in the configuration therefore the first configured queue definition has been assumed to be the default.
PUSH-000303
Queue definition '{}' not known - using default.
Description
The specified queue definition is not known within the configuration therefore the default queue definition has been assumed.
PUSH-000306
Deployment service failed to process HTTP request.
Description
The publisher deployment service failed to return an HTTP response to the deploying client.
PUSH-000309
REST Failed to process service request.
Description
REST service failed to process a request.
PUSH-000310
Method '{}' from Diffusion servlet called, not being processed.
Description
The Diffusion servlet's implementation of the given method does nothing.
PUSH-000311
Diffusion servlet: {}.
Description
Indicates the startup status of the Diffusion servlet.
PUSH-000312
Client statistics log name '{}' is not configured.
Description
The log named in the client statistics configuration does not exist in the logs configuration.
PUSH-000313
Client statistics enabled but no log name supplied.
Description
No log name has been specified in the client statistics configuration.
PUSH-000316
Failed to update statistics file '{}'.
Description
It was not possible to write the given statistics file.
PUSH-000317
Statistics manager failure.
Description
An unexpected error occurred while starting the statistics manager.
PUSH-000318
Registering statistics reporter '{}'.
Description
A configured statistics reporter of the given name is about to be registered.
PUSH-000319
Failed to register statistics reporter '{}'.
Description
An attempt to register the named configured statistics reporter has failed - the reporter has therefore been ignored.
PUSH-000320
Started statistics reporter '{}'.
Description
The named statistics reporter task has started.
PUSH-000321
Statistics service failed to load statistics reporter '{}'.
Description
A failure has occurred while attempting to load a configured statistics reporter.
PUSH-000322
Error starting statistics service.
Description
An error has occurred while starting the statistics service.
PUSH-000323
Background thread pool caught exception executing '{}'.
Description
A task being executed by the background thread pool has thrown an exception.
PUSH-000324
Thread pool '{}' could not create new thread.
Description
A thread pool encountered an error while attempting to create a new thread.
PUSH-000326
Thread pool {} execution of {} failed.
Description
Failure executing a task in the specified thread pool.
PUSH-000327
Thread pool {} lower limit notification failed.
Description
The specified thread pool was unable to schedule the notification of the lower threshold limit being reached.
PUSH-000328
Thread pool {} notification of {} to {} failed.
Description
The execution of a notification to a ThreadPoolNotificationHandler failed.
PUSH-000331
Thread pool '{}' queue full - aborting execution of '{}'.
Description
Specified thread pool queue has become full and the rejection policy is to abort the task. Consider increasing the pool maximum size.
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-000333
Thread pool {} was unable to schedule the execution of notification of rejected execution.
Description
The specified thread pool failed to schedule the notification of a rejected task.
PUSH-000334
Thread Pool {} upper threshold notification failed.
Description
The specified thread pool failed to schedule notification of upper threshold reached.
PUSH-000335
Uncaught exception in thread '{}'.
Description
An uncaught exception has been thrown from a specified thread and logged.
PUSH-000336
Algorithm '{}' not found.
Description
The given cryptographic module could not be found.
PUSH-000337
File service: [{}] adding virtual hosts {} and mapping to {}.
Description
A virtual host has been added to the web server's file service.
PUSH-000338
Unable to process alias entry in file '{}': {}.
Description
Diffusion tried to add a new alias to the web server, but failed.
PUSH-000339
HTMLTopicDataSegment: unable to process topic data for {}.
Description
The web server tried to include the contents of a topic's TopicData into the response, but a failure occurred.
PUSH-000340
HTMLIncludeSegment: unable to populate buffer [{}].
Description
The web server tried to include the contents of another file in the response, but a failure occurred writing to a buffer.
PUSH-000341
Missing attribute '{}' from DiffusionTag {} [{}].
Description
The given DiffusionTag incorrect omits the given attribute.
PUSH-000342
Topic '{}' has '{}' TopicData instead of single value TopicData. DiffusionTag (TopicData) [{}].
Description
The given topic lacks SingleValueTopicData, making it impossible to insert here.
PUSH-000343
Topic {} does not have topic data. DiffusionTag (TopicData) [{}].
Description
The given topic lacks TopicData and therefore any state, making it impossible to insert here.
PUSH-000344
Cannot find file attribute in DiffusionTag [{}].
Description
The given DiffusionTag incorrectly omits the 'file' attribute.
PUSH-000345
Cannot load include file '{}' from DiffusionInclude '{}'.
Description
An error occurred loading the given file.
PUSH-000346
Cannot read specified file for DiffusionTag '{}' [{}].
Description
An error occurred loading the given file specified in the DiffusionTag.
PUSH-000347
Unknown publisher in DiffusionTag {} [{}].
Description
The publisher named in this DiffusionTag is not loaded, or does not exist.
PUSH-000348
Unknown topic for DiffusionTag (TopicData) {} [{}].
Description
The topic named in this DiffusionTag does not exist.
PUSH-000349
Unknown type attribute '{}' for DiffusionTag [{}].
Description
The type attribute of this DiffusionTag holds an unexpected value.
PUSH-000350
Web server service cannot process HTML tag '{}' for the publisher '{}'.
Description
An error occurred while processing an HTML embedded tag.
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-000352
{}: connection rejected as [{}] did not match '{}'.
Description
The connection from an untrusted host was rejected, in accordance with CORS configuration.
PUSH-000353
{}: Connection rejected as [{}] did not match {}.
Description
The connection was rejected because its WebSocket origin did not match the regular expression stored in the configuration.
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-000355
{} unable to process HTTP Request '{}'.
Description
Web server file service was unable to process the given HTTP request.
PUSH-000356
Client service {}: HTTP processing error on connector '{}'.
Description
An error occurred handling an HTTP request.
PUSH-000357
{}: Invalid regular expression '{}' for CORS origin '{}' - feature disabled.
Description
An invalid regular expression was given for the CORS origin configuration.
PUSH-000358
{}: Invalid regular expression '{}' for WebSocket origin '{}' - feature disabled.
Description
An invalid regular expression was given for the WebSocket origin configuration.
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-000361
Unable to service HTTP request for service '{}'.
Description
An HTTP service was invoked, but it failed to process the incoming request.
PUSH-000362
Started HTTP service for '{}'.
Description
An HTTP service was successfully started.
PUSH-000363
{} Unable to create log.
Description
An HTTP service has its own log file defined, but Diffusion was unable to create the logger.
PUSH-000364
Web server {} failed to instantiate HTTP service '{}' : {}.
Description
A web server failed to instantiate the named configured HTTP service.
PUSH-000365
Web server failed to start cache service for virtual host '{}'.
Description
An error occurred while starting the cache service for the given virtual host.
PUSH-000366
Virtual host HTTP request {} is invalid.
Description
An HTTP request being handled by a virtual host is trying to break out of the virtual root.
PUSH-000367
Virtual Host HTTP request {} - unable to read file {}.
Description
A failure has occurred trying to read the specified HTML file.
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-000369
Failed to schedule a periodic tidy of the WhoIs cache.
Description
A failure has occurred while trying to schedule a periodic tidy of the WhoIs cache.
PUSH-000370
WhoIs Provider class instantiation failure calling '{}'.
Description
Unable to instantiate the configured WhoIs provider. Will use the default WhoIs provider.
PUSH-000372
Unable to load GeoIP Database '{}'.
Description
An error occurred while loading or initializing the GeoIP database.
PUSH-000373
WhoIs Service failed to lookup address '{}'.
Description
A failure has occurred in the WhoIs service when trying to look up the given address.
PUSH-000374
WhoIs service starting with {} thread(s).
Description
The WhoIs service is starting.
PUSH-000375
Deprecated connector type RTMP found in Connectors.xml and will be ignored.
Description
Deprecated connector type RTMP found in Connectors.xml and will be ignored.
PUSH-000376
Deprecated element '{}' found in {}.xml.
Description
A deprecated element has been found in specified properties file and should be removed.
PUSH-000377
Failed to load XML properties '{}'.
Description
Failed to load XML properties.
PUSH-000378
Failed to load publisher '{}' configuration from XML properties.
Description
Diffusion was unable to load the configuration for the named publisher from an XML properties file.
PUSH-000379
Failed to load subscription validation policy '{}' from file '{}' : {}.
Description
A failure has occurred loading an XML subscription validation policy file.
PUSH-000380
Failed to parse {} at line {}, column {}: {}.
Description
An XML validation event has occurred while validating an XML property file.
PUSH-000381
Loaded XML {} properties from '{}'.
Description
The specified XML properties have been loaded from the file indicated.
PUSH-000382
Unable to load publisher configuration file {}.
Description
Attempted to load a publisher's configuration file (Publishers.xml), but it cannot be found or is unreadable.
PUSH-000383
Unable to check server-side addressing for product {} [{}] : {}.
Description
An error occurred while attempting to check server-side addressing in the licence file.
PUSH-000384
'{}': Failed to decode licence key '{}'.
Description
Unable to decode licence key.
PUSH-000385
Failed to load subscription validation topic mapping for publisher {} topic {} from file {} : {}.
Description
A failure has occurred loading a publisher topic mapping for a subscription validation policy.
PUSH-000386
Failed to load connection validation policy {} from {}.
Description
A failure has occurred loading XML connection validation policy from the specified file.
PUSH-000387
License check failed to match MAC address for '{}'.
Description
Unable to match a MAC address for the specified product.
PUSH-000388
Failed to save XML properties '{}'.
Description
A failure has occurred while saving XML properties.
PUSH-000389
Server connection '{}' has been added for publisher '{}'.
Description
A configured server connection has been successfully added for a publisher.
PUSH-000390
Failed to add server connection '{}' for publisher '{}'.
Description
SSL keystore file has successfully been loaded for a publisher to server connection.
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-000392
Publisher '{}' has lost connection to server '{}' - publisher closing.
Description
A publisher has lost connection to a server and the recovery policy indicates that the publisher must be closed.
PUSH-000393
Publisher '{}' has lost connection to server '{}' - no recovery policy specified.
Description
A publisher has lost connection to a server and no recovery policy has been specified.
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-000395
Publisher '{}' unable to schedule retry connection to '{}' - publisher stopping.
Description
A failure has occurred attempting to schedule a connection retry between a publisher and a server. The publisher will be closed.
PUSH-000396
Unable to perform substitution within property value '{}' due to syntax error.
Description
A syntax error has been detected while trying to perform environment variable substitution on a configuration property.
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-000400
Unable to add listener when reconnecting to {}.
Description
While reconnecting, the JMS adapter was unable to add a listener for a JMS destination.
PUSH-000401
Unable to create consumer when reconnecting to {}.
Description
While reconnecting, the JMS adapter was unable to recreate a JMS consumer.
PUSH-000402
Unable to create session when reconnecting to {}.
Description
While reconnecting and re-establishing the existing JMS consumers, the JMS adapter failed to create a JMS session.
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-000406
Application handler threw exception {}. [cid={}].
Description
An application handler threw an exception when called.
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-000409
Unable to close socket channel '{}'.
Description
The socket channel failed to close.
PUSH-000410
Failed to queue background close of the publisher server connection '{}'.
Description
An attempt to queue the close of the publisher server connection failed, therefore the connection has been closed in the current thread.
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-000412
Executor {}: task finished abnormally.
Description
A background task has thrown an exception. See the log for more information.
PUSH-000413
Received request from client {} for the details of client session {}.
Description
The server has received a client request for details of a client session.
PUSH-000414
Received request from client {} for the details of client session {}. The client session does not exist.
Description
The server has received a client request for details of an unknown client session.
PUSH-000415
Received request from client {} to close client {}.
Description
The server has received a request from a client to close a client session.
PUSH-000416
Received request from client {} to close client {}. The client session does not exist.
Description
The server has received a request from a client to close an unknown client session.
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-000420
One or more clients have registered to handle queue events, but none was available for a {} event for client {}.
Description
No client was available to handle the queue event, or one was chosen and failed while processing.
PUSH-000421
Received request from client {} to set conflation for client {} to '{}'.
Description
The server has received a request from a client to change the conflation setting for a client queue.
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-000423
Received request from client {} to throttle message queue for client {} using the {} policy, limit={}.
Description
The server has received a request from a client to change the throttling policy of a 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-000426
{}: command service call failed, reporting error to {}: {}.
Description
An internal service call has failed. An error will be reported to the client session listener.
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-000430
There are currently no controllers for {}.
Description
A control binding has been established, but there are no available controllers.
PUSH-000431
Rejected attempt by client {} to bind a control handler: {}.
Description
This might indicate that another control group has established a binding, or that the client already has a binding.
PUSH-000432
Attempt by client {} to register or unregister from an unknown control point: {}.
Description
This is unexpected and possibly indicates the server and client versions are incompatible.
PUSH-000433
Application handler threw exception {} when called with a response. [cid={} response={}].
Description
An application handler threw an exception when called.
PUSH-000434
Diffusion finished deploying {} components.
Description
Diffusion deployments completed.
PUSH-000435
Task failure in selector thread '{}'.
Description
A task failed to be executed in a selector thread.
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-000439
The authentication manager failed to start because an authentication handler of class {} could not be created.
Description
An instance of a configured authentication handler could not be created.
PUSH-000440
Authentication handler {} threw an exception, denying authentication to {}.
Description
A configured authentication handler failed to process an authentication request.
PUSH-000441
The authorization manager failed to start because an authorization handler of class {} cannot be created.
Description
An instance of a configured authorization handler cannot be created.
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-000444
Unable to read aliases file '{}'.
Description
The configured aliases file could not be read.
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-000446
Unable to read subscription polices from '{}'.
Description
The configured subscription policy file could not be read.
PUSH-000447
Failed to load publisher '{}'.
Description
Diffusion was unable to register a publisher, probably because of a problem with the publisher's definition.
PUSH-000448
An error occurred registering a handler with parameters '{}': {}.
Description
An internal error occurred registering a handler.
PUSH-000450
An error occurred unregistering a handler with parameters '{}': {}.
Description
An internal error occurred unregistering a handler.
PUSH-000452
A topic update failed because no updater could be found.
Description
A topic update failed because the client has unregistered the updater.
PUSH-000453
A topic update failed unexpectedly: {}.
Description
A topic update failed. See the log message for further information.
PUSH-000456
Notifying session {} of error '{}'.
Description
A session error has occurred. The session error handler will be called.
PUSH-000457
More multiplexers configured than available CPU cores ({} vs {}).
Description
Assigning more multiplexers than there are available CPU cores might lead to degraded performance.
PUSH-000458
Application classpath entry '{}' in is not a directory. Check user libraries in the server configuration.
Description
The names in the user library configuration must identify directories.
PUSH-000459
The configured auto-deployment directory '{}' does not exist.
Description
The configured auto-deployment directory '{}' does not exist.
PUSH-000460
Class loader failed to enumerate files in directory '{}'.
Description
An error occurred reading the files within the given directory.
PUSH-000461
Unable to add file '{}' to the class loader.
Description
A server class loader failed to load the given file.
PUSH-000462
Multiplexer '{}' overflowed before start up - event discarded.
Description
A multiplexer queue overflowed before the multiplexer was started.
PUSH-000464
Update failed for topic '{}'.
Description
An error was encountered while attempting to update a topic.
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-000466
Message stream '{}' threw exception.
Description
A message stream callback raised an exception when called.
PUSH-000467
Unable to establish a tunnel through the proxy at {}:{}.
Description
There was a problem in establishing a tunnel through the specified proxy. There might be an issue in reading from or writing to the proxy.
PUSH-000468
Topic stream '{}' threw exception.
Description
A topic stream callback raised an exception when called.
PUSH-000469
Failure to forward message from {} to client {} for topic '{}'.
Description
The server failed to forward a message from a client to another client. The message might have been delivered. See the log for further detail.
PUSH-000470
The server failed to forward a message from {} to unknown client {} for topic '{}'.
Description
The server failed to forward a message as the target client session does not exist.
PUSH-000472
Service call to server from session {} failed: {}.
Description
The server rejected a service call due to an error. See the log message for further details.
PUSH-000473
Service call to client {} failed: {}.
Description
The client rejected a service call due to an error. See the log message for further details.
PUSH-000474
Failed to deliver missing topic notification for subscription or fetch to selector '{}' by session '{}'.
Description
A request made by the server to a missing topic handler resulted in an error.
PUSH-000475
The '{}' secret key encryption algorithm is not available.
Description
The specified password encryption algorithm is not available which means that a less secure default mode of password encryption will be used.
PUSH-000476
No authentication handlers are configured. All sessions will be anonymous.
Description
No authentication handlers are configured. All sessions will be anonymous.
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-000478
"{}" at line {} column {}.
Description
An error occurred while parsing security store language commands at the indicated line and column number.
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-000481
Errors detected while parsing persistent store file "{}".
Description
Errors were detected while parsing the specified persistent store file - a detailed list of the errors will follow in the log.
PUSH-000482
Error reading persistent store file "{}".
Description
A read error has occurred on a security persistence file.
PUSH-000483
Failure writing to the {} persistence store.
Description
An error has occurred while writing to the named persistence store. The store file could be corrupt and might need to be recovered from a 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-000485
{}: backlog during initialization - {} queued events sent so far, {} remain on queue.
Description
A session details dispatcher is taking a while to deliver the backlog of pending events to the control client session.
PUSH-000486
{}: closed.
Description
A session details dispatcher was closed.
PUSH-000487
{}: draining queued updates.
Description
A session details dispatcher is starting. It is about to process a backlog of pending events.
PUSH-000488
{}: initialized.
Description
A session details dispatcher has completed initialization.
PUSH-000489
{}: initialising. Sending {} initial client notifications.
Description
A session details dispatcher is starting.
PUSH-000490
Session error handler {} threw an exception.
Description
An application session error handler threw an exception when called.
PUSH-000491
Session listener {} threw an exception.
Description
An application session listener threw an exception when called.
PUSH-000492
Failed to register topic update source for path {} by session {}.
Description
The server rejected a request to register an update source.
PUSH-000493
WhoIs Service failed unexpectedly.
Description
The WhoIs Service failed.
PUSH-000494
Failed to execute will {} for session {} because of insufficient permissions.
Description
A client session will to remove a topic could not be executed because the session lacks the required permissions.
PUSH-000495
Failed to execute will {} for session {} as the topic does not exist.
Description
A client session will to remove a topic cannot be executed because the topic does not exist.
PUSH-000496
Unexpected error while sending message.
Description
An error occurred when trying to send a message.
PUSH-000497
Connector '{}' does not support clients.
Description
A connector has received an attempted connection which indicates that it is a Diffusion client but the connector does not support client connections.
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-000500
Introspector client {} has insufficient permissions for '{}' request.
Description
The specified Introspector client does not have sufficient permissions to perform the request.
PUSH-000501
Diffusion publisher failed to publish a log message to internal topics, disabling handler.
Description
The Diffusion publisher failed to publish a log message. The log handler has been disabled.
PUSH-000503
A blocking operation failed because the multiplexers failed to process it within {} milliseconds.
Description
This indicates that the server is severely overloaded or deadlocked.
PUSH-000504
No control handler found for routing topic '{}', subscription for client {} will be deferred until one is available.
Description
A routing handler must be registered for routing subscriptions to complete.
PUSH-000506
Flow control pressure {}%.
Description
Flow control back pressure has reached this value.
PUSH-000507
Flow control off.
Description
Back pressure has reduced, flow control is no longer being applied.
PUSH-000508
Client {} sent message to unknown topic '{}'.
Description
Classic API clients can only can send messages to existing topics.
PUSH-000510
Unable to rotate metrics file '{}'.
Description
The internal FileMetricsWriter was unable to rotate out the specified file.
PUSH-000511
Unable to write metrics to file '{}'.
Description
The internal FileMetricsWriter was unable to write to the specified file.
PUSH-000512
Session property {} not allowed.
Description
An attempt has been made to define a session property with a name that is not allowed.
PUSH-000513
{} - failed to create load message.
Description
An error was encountered while updating topic data.
PUSH-000514
Cannot parse "server-name/sessionId" expression required for delivery to Diffusion client: {}.
Description
The nominated routing property lacks a valid "server-name/sessionId" expression.
PUSH-000515
Cannot place JMS session to provider {}.
Description
An error occurred when trying to place a JMS session to the given provider.
PUSH-000516
Cannot publish message to topic {}.
Description
An error occurred while publishing a Diffusion topic update.
PUSH-000518
Connected to JMS provider '{}'.
Description
The JMS adapter has connected to the JMS provider with the given name.
PUSH-000519
Connection attempt to '{}' failed.
Description
It was not possible to connect to the given JMS provider.
PUSH-000520
Exception closing JMS Connection to {}.
Description
An error occurred while the JMS connection was being closed.
PUSH-000521
Failed to deliver message to client {}.
Description
An error occurred during an attempt to deliver a message to a Diffusion client.
PUSH-000523
Retrying delivery of message to {}: {}.
Description
Following a failed delivery the delivery re-attempted once.
PUSH-000524
Returning message '{}' to origin: {}.
Description
A message received from a client could not be delivered to a JMS destination, and is being returned to the sender.
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-000527
Cannot establish publication to destination {}: {}.
Description
It was not possible to build a MessageProducer for the given JMS destination.
PUSH-000528
Connected to JMS provider {} v{}, JMS {}.
Description
Recording JMS provider and version, and JMS API version in use.
PUSH-000529
Failed to generate snapshot for topic {}.
Description
The attempt to generate a snapshot for distribution through replication failed. See the stacktrace for more information on why the snapshot could not be generated.
PUSH-000530
A subscription failed to complete within the {} millisecond timeout.
Description
A publisher API subscription operation failed to complete. This indicates the server is heavily loaded.
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-000532
Failed to initialize Diffusion client.
Description
Fatal error initializing the Diffusion client.
PUSH-000533
Request to remote routing subscription handler for client {} / routing topic '{}' failed.
Description
A request to a remote routing subscription handler failed.
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-000535
Fan-out connection to primary server at '{}' closed.
Description
A fan-out connection to a primary server has been closed.
PUSH-000536
Fan-out connection to primary server at '{}' has failed ({}).
Description
A fan-out connection has failed to connect to the primary server.
PUSH-000537
Fan-out connection to primary server at '{}' has been lost.
Description
A fan-out connection to a primary server has been lost.
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-000539
Unexpected session error in fan-out client {} : '{}'.
Description
A fan-out connection has received an unexpected session error.
PUSH-000541
Fan-out link '{}' closed.
Description
A fan-out link replicated from a primary server has been closed.
PUSH-000542
Fan-out link '{}' started.
Description
A fan-out link replicated from a primary server has been started.
PUSH-000543
Fan-out started.
Description
Fan-out processing has been started.
PUSH-000544
Fan-out link '{}' failed to create replicated topic '{}'.
Description
A failure has occurred creating a replicated topic for a specified fan-out link.
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-000546
Fan-out update of topic '{}' by '{}' has failed.
Description
A failure has occurred whilst updating a fan-out secondary topic.
PUSH-000547
Failed to close selector '{}'.
Description
An error occurred closing a selector.
PUSH-000548
Failed to interrupt thread for selector '{}'.
Description
A selector thread could not be stopped cleanly.
PUSH-000549
Stopping selector thread '{}'.
Description
A selector thread is being stopped.
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-000551
rotate-daily is deprecated. Use the log attribute rotation-period instead.
Description
Warning message that the rotate-daily element has been deprecated and that the rotation-period attribute should be used.
PUSH-000552
Remote JMX management service could not be started.
Description
The remote JMX management service was not started correctly. The rmiConnectorServer is not active.
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-000557
{}: closed.
Description
A session properties dispatcher was closed.
PUSH-000558
{}: draining queued updates.
Description
A session properties dispatcher is starting. It is about to process a backlog of pending events.
PUSH-000559
{}: initialised.
Description
A session properties dispatcher has completed initialisation.
PUSH-000560
{}: initialising. Sending {} initial client notifications.
Description
A session properties dispatcher is starting.
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-000564
Established fan-out connection '{}' to primary server '{}'.
Description
A fan-out connection to the primary server has been established.
PUSH-000565
Failed to register topic event listener for path {} by session {}.
Description
The server rejected a request to register a topic event listener.
PUSH-000566
Daily statistics have been written in the ConnectionCount file.
Description
The server is shutting down - the daily statistics registered so far have been written in the ConnectionCount file.
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-000571
Failed to start required connector, '{}'.
Description
A required connector, in Connectors.xml, has not been started.
PUSH-000572
Fan-out connection '{}' is removing topics '{}'.
Description
A fan-out connection is removing a set of replicated topics.
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-000574
Fan-out client {} update of paged topic '{}' has failed - no more updates will be applied to this topic.
Description
A fan-out update of a paged topic has failed - no more updates will be applied to the topic.
PUSH-000575
HTTP poll rejected - Invalid message channel '{}' cannot be cast to HTTPMessageChannel.
Description
HTTP poll attempted on transport that does not support polling.
PUSH-000576
The Diffusion SLF4J logger is not configured. Log configuration will be ignored.
Description
The Diffusion classpath has been modified to use a third-party SLF4J logging library.
PUSH-000577
No server log has been configured.
Description
The log configuration does not specify a server log. Messages will only be logged to the console (stderr).
PUSH-000578
{}, {}, {} {}.
Description
Diffusion and Java product versions information.
PUSH-000579
Failed to register paged notification listener for path {} by session {}.
Description
The server rejected a request to register a paged notification listener.
PUSH-000581
Client service {}: unrecognized HTTP request received on connector '{}'.
Description
The server failed to understand an HTTP request failed.
PUSH-000582
JMS adapter cannot apply configuration update from {}.
Description
Configuration changes loaded from the JMS configuration file cannot be applied.
PUSH-000583
JMS adapter configuration file {} cannot be loaded.
Description
The JMS adapter configuration file cannot be loaded.
PUSH-000584
JMS adapter cannot roll back the configuration change from {}, step {}.
Description
Following a failed configuration change a roll back was attempted which also failed. Behavior of the JMS adapter here on is unknown.
PUSH-000585
The JMS adapter has reloaded its configuration from {}.
Description
The JMS adapter has reloaded its configuration file.
PUSH-000586
JMS adapter configuration file {} has been removed.
Description
The JMS adapter configuration file has been removed.
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-000589
SSL channel {} was closed with data still pending.
Description
SSL connection was closed with data still pending.
PUSH-000590
Host JVM/JDK failed to provide an expected feature {}.
Description
The JVM/JDK failed to behave as expected at runtime. Please check the platform is supported.
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-000592
Sending {} message(s) of {} bytes to {} was delayed by {} ms.
Description
The message took an unreasonably long time to be sent. This could be caused by network backpressure, flow-control or application delays.
PUSH-000593
Cannot get value attribute {} on MBean {}.
Description
An exception was thrown retrieving an attribute from a given JMX MBean.
PUSH-000594
JMX adapter stopping.
Description
The JMX adapter is stopping and removing its topics.
PUSH-000595
Unable to look up session {} in the data grid.
Description
A protocol 4 reconnection was attempted. A new identity will be issued to the client. See the exception for more information on the cause of the failure.
PUSH-000596
Unable to look up session by token in the data grid.
Description
A protocol 5 or above reconnection was attempted and has failed. See the exception for more information on the cause of the failure.
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-000600
Unable to store session {} in the data grid.
Description
An attempt to store a new session in the data grid failed. The session is known to a single server. 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-000604
Suppressed {} further {} messages.
Description
Repeated log messages have been suppressed.
PUSH-000605
An error occurred while stopping the remote JMX management service.
Description
The remote JMX management service was not stopped correctly.
PUSH-000607
Authentication failed for connection {}.
Description
An AuthorisationManager rejected a connection attempt.
PUSH-000608
Validation failed for connection {}.
Description
An connector validator rejected a connection attempt.
PUSH-000609
Reconnection aborted because server did not receive {} messages from {}.
Description
Reconnection aborted because messages sent from a client session were not recoverable.
PUSH-000610
Reconnection aborted because {} messages sent by the server were not received by {}.
Description
Reconnection aborted because messages sent to a client session were not recoverable.
PUSH-000611
Unable to complete reconnection, recovery failed for unknown session {}.
Description
A session could not be reconnected because it was unknown.
PUSH-000612
Reconnection aborted because {} messages sent to the server were not received by {}.
Description
Reconnection aborted because messages sent to the server were not recoverable.
PUSH-000613
{} reconnected, but messages may have been lost.
Description
A session has re-establish communication with a server, but messages may have been lost. This can happen when reconnecting to another server in an HA cluster.
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-000615
Failed to send a checkpoint to a new member of the cluster.
Description
A new node attempted to join the cluster but the cluster failed to send the current state of the distributed update source registry to it.
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-000617
Connection '{}' was closed due to timeout.
Description
A network connection was timed out due to inactivity on the channel.
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-000619
Thread pool {} queue full - blocking calling thread.
Description
The calling thread is blocked until the specified thread pool can accept a new task. Consider increasing the pool maximum size.
PUSH-000620
Cannot retrieve session properties for {}: {}.
Description
The JMS adapter cannot retrieve the session properties for the given session.
PUSH-000621
Client {} closing - {} - {}. {}.
Description
A client session was closed.
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-000623
Fan-out connection '{}' lost - attempting reconnection.
Description
A fan-out connection has been lost and is now attempting to reconnect.
PUSH-000624
Connection '{}' closed - {}.
Description
A network communication error occurred. The connection has been closed.
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-000629
Created {} of {} topics.
Description
Logged every 5s by the JMS Adapter if creating all configured topics exceeds that threshold.
PUSH-000630
Removed {} of {} topics.
Description
Logged every 5s by the JMS Adapter if removing previously configured topics exceeds that threshold.
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-000632
Failed to propagate missing topic notification for subscription or fetch to selector '{}' by session '{}' to primary server '{}'.
Description
Fan-out propagation of a missing topic notification failed.
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-000634
'{}': reconnect attempt failed.
Description
An attempt to reconnect has failed. Further attempts to reconnect may be made depending on the reconnection strategy.
PUSH-000635
'{}': reconnection rejected by server.
Description
The server has rejected the reconnection attempt. No further attempts to reconnect will be made - the session will be closed.
PUSH-000636
'{}': reconnection failed due to timeout.
Description
The timeout to successfully reconnect has been reached. The session will be closed.
PUSH-000637
The Security.store file cannot be found.
Description
The Security.store file was not found, a default security store has been created.
PUSH-000638
The '{}' file cannot be found.
Description
The store file was not found. A default store has been created.
PUSH-000640
Started the JMS adapter with configuration {}.
Description
The JMS adapter was started with the given configuration file.
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.
PUSH-000644
Completed diagnostic report to {}.
Description
A multiplexer diagnostic report has completed.
PUSH-000645
Failed to write diagnostic report to {}.
Description
A multiplexer diagnostic report could not be produced.
PUSH-000646
Starting diagnostic report to {}.
Description
A multiplexer diagnostic report has started.