Sun Java System Messaging Server 6.3 Administration Guide

27.7 Monitoring the Message Store

Messages are stored in a database. The distribution of users on disks, the size of their mailbox, and disk requirements affect the store performance. These are described in the following subsections:

27.7.1 Monitoring stored

stored performs a variety of important tasks such as deadlock and transaction operations of the message database, enforcing aging policies, and expunging and erasing messages stored on disk. If stored stops running, the messaging server will eventually run into problems. If stored doesn’t start when start-msg is run, no other processes will start. For more information about stored see stored in Sun Java System Messaging Server 6.3 Administration Reference. Symptoms of stored Problems

There are no outward symptoms. To Monitor stored

27.7.2 Monitoring the State of Message Store Database Locks

The state of database-locks is held by different server processes. These database locks can affect the performance of the message store. In case of deadlocks, messages will not be getting inserted into the store at reasonable speeds and the ims-ms channel queue will grow larger as a result. There are legitimate reasons for a queue to back up, so it is useful to have a history of the queue length in order to diagnose problems. Symptoms of Message Store Database Lock Problems

Number of transactions are accumulating and not resolving. To Monitor Message Store Database Locks

Use the command imcheck -s (used to be counterutil -o db_lock)