Best practices for coding  Queue and topic settings

Chapter 8: Message Service Tuning

Global message service settings

These settings can be configured by running the Message Service Configuration wizard in EAServer Manager or by editing the MessageServiceConfig.props file in the EAServer Repository/Components/CtsComponents subdirectory. For more information, see Chapter 8, “Setting up the Message Service,” in the EAServer System Administration Guide.

Database and connection cache

You can specify the connection cache used by the message service in the configuration wizard. Tune the cache settings as described in “Connection cache settings”. To support development use, the default message service configuration connects to the Adaptive Server Anywhere database server runtime that is included with EAServer. For large scale production use, Sybase recommends that you use an enterprise-grade database server such as Sybase Adaptive Server Enterprise.


For best performance, make sure tracing is disabled. Set the properties listed in Table 8-1 to false; these properties are set in the MessageServiceConfig.props file.

Table 8-1: Message service tracing properties




General tracing


Session level tracing

Network level tracing

Other global settings

You can modify these settings by editing the MessageServiceConfig.props file.


This global property configures a maximum limit for persistent messages stored in the <system> queue and user defined queues with the queue maximum property set to 0 or a negative number (see “Queue size”). To set the global property, specify the message limit, for example:


The default is 100. This setting restricts in-memory caching of persistent messages; you can change it to tune the memory used to hold persistent messages in the <system> queue and user defined queues where the maximum property is 0 or a negative value.

This setting also determines how many persistent messages EAServer reads into memory during message service initialization. A large default size can delay server startup when there is a large backlog of unprocessed messages, since the message service reads this many messages into memory when initializing.

The setting does not restrict the number of transient messages in the system queue or in user defined queues where the maximum property is 0 or a negative value.


This property specifies the default timeout for temporary message queues for which you have not set an explicit timeout. Specify the timeout in seconds. The default is 60. The minimum value is 5; values less than this have the same effect as setting the timeout to 5 seconds.

Copyright © 2005. Sybase Inc. All rights reserved. Queue and topic settings