Using the stored Utility (Sun Java System Messaging Server 6 2005Q4 Administration Guide)

Sun Java System Messaging Server 6 2005Q4 Administration Guide

Using the stored Utility

The stored utility performs the following monitoring and maintenance tasks for the server:

Background and daily messaging tasks.
Deadlock detection and rollback of deadlocked database transactions.
Cleanup of temporary files on startup.
Implementation of aging policies.
Periodic monitoring of server state, disk space, service response times, and so on (see stored).
Issuing of alarms if necessary.
Database recovery as necessary (see Message Store Startup and Recovery

The stored utility automatically performs cleanup and expiration operations once a day at 11 PM. You can choose to run additional cleanup and expiration operations.

Table 18–12 lists some of the stored options. Some common usage examples follow the table. For detailed syntax and usage requirements, see the Sun Java System Messaging Server 6 2005Q4 Administration Reference.

Table 18–12 stored Options


Option	Description
`-d`	OBSOLETE. Use `start-msg store` to start up stored which will run as daemon, performing system checks and activating alarms, deadlock detection, and database repair.
`-t`	Checks the status of `stored.` The return code of this command indicates the status.
`-v`	Verbose output.
`-v -v`	More verbose output.

To print the status, enter:

stored -t -v

If you want to change the time of the automatic cleanup and expiration operations, use the configutil utility as follows:

configutil -o store.expirestart -v 21

Occasionally, you might need to restart the stored utility; for example, if the mailbox list database becomes corrupted. To restart stored on UNIX, use the following commands at the command line:

msg_svr_base/sbin/stop-msg store
msg_svr_base/sbin/start-msg store

If any server daemon crashes, you must stop all daemons and restart all daemons including stored.