Messages are not sent

There are several common reasons why messages might not be sent.

Can the application connect to Eclipse Amlen?

If messages are not being sent, the cause might be that the application cannot connect to Eclipse Amlen.

Check the logs for error messages that indicate that the application cannot connect. For more information about troubleshooting applications that fail to connect to the Eclipse Amlen, see The application fails to connect.

Is the topic string valid?

If an invalid topic string is specified, messages are not published. There are a number of ways in which the topic string can be invalid. For more information about valid topic strings, see Table 1.

Does the messaging policy allow the message to be sent?

When you create a messaging policy, you can restrict whether an application can publish or subscribe to a topic string, or it can send, receive, or browse a queue. The restriction can be based on one or more of the following values: IP address, client ID, messaging user ID, messaging group, or the client certificate used. If messages are not being sent, the cause might be that the messaging policy does not allow the application to publish to the topic string, or send to the queue.

Check the logs for messages that indicate the messaging policy does not allow the message to be published or sent. To resolve the problem, connect the application to an endpoint with messaging policies that allow the message to be published or sent. Alternatively, change the messaging policy to allow the application to publish or send.

Has the max message count been reached?

In the messaging policies, a maximum message count is defined if the destination type is topic. If a backlog of messages builds up on Eclipse Amlen, the maximum message count might be reached. When the maximum message count is reached, messages cannot be published until the backlog is reduced.

Check the imaserver-default.log log file for messages that indicate that the maximum message count is reached.

Has the max message size been exceeded?

When you define an endpoint, you can set a maximum size for messages 1 - 262,144 KB. If you attempt to publish a message that is larger than the maximum message size defined in the endpoint, the message is not published.

Check the imaserver-default.log log file for messages that indicate that the maximum message size is exceeded. To resolve the problem, you can connect the application to an endpoint that allows messages of that size. Alternatively, you can increase the maximum message size that is allowed on the endpoint, or you can reduce the size of the message.

Has the maximum topic depth been exceeded?

Eclipse Amlen has a maximum topic depth of 32 levels. If you attempt to publish a message to a topic string that exceeds this depth, the message is not published.

To resolve the problem, you must reduce the depth of the topic string.