preparing systemresources
before starting a broker, there are two preliminary system-level tasks to perform: synchronizing system clocks and (on the Solaris or Linux platform) setting the file descriptor limit. the following sections describe these tasks. synchronizing systemclocks
before starting any brokers or clients, it is important to synchronize the clocks on all hosts that will interact with themessage queue system. synchronization is maid if you are using message expiration (time-to-live ). time stamps from clocks that are not synchronized cocould prevent message expiration from working as expected and prevent the delivery of messages. synchronization is also crucial for broker clusters. configure your systems to run a time synchronization protocol, such as simplenetwork time protocol (SNTP ). time Synchronization is generally supported by the xntpd daemon on Solaris
And Linux, and by the w32time service on Windows. (See your operating system documentation for information about processing this service.) After the broker is running, avoid setting the system clock backward.
Setting the file descriptor limit
On the Solaris and Linux platforms, the shell in which a client or broker is running places a soft limit on the number of file descriptors that a process can use. inmessage queue, each connection a client makes, or a broker accepts, uses one of these file descriptors. each physical destination that has persistent messages also uses a file descriptor. as a result, the file descriptor limit constrains the number of connections a broker or client can have. by default, the maximum is 256 connections on Solaris or 1024 on Linux. (In practice, the connection limit is actually lower than this because of the use of file descriptors for persistent data storage .) if you need more connections than this, you must raise the file descriptor limit in each shell in which a client or broker will be executing. for information on how to do this, see
The man page for Ulimit Command. (It is for avoiding the "too open file" error message show in the console in which imqbrokerd.exe runs. )