bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

JMS File Store --> Configuration

Tasks Additional Documentation Attributes

Overview

This tab defines general configuration attributes for a JMS file store. A JMS file store consists of a file that is used for persistent messaging.

Tasks

Create a JMS File Store

Clone a JMS File Store

Delete a JMS File Store

Additional Documentation

(Requires an Internet connection.)

"Managing JMS"in the Administration Guide

"WebLogic JMS Fundamentals" in Programming WebLogic JMS

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Name | The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. MBean: weblogic.management. configuration. JMSFileStoreMBean Attribute: Name | Configurable: yes Readable: yes Writable: yes
SynchronousWritePolicy | A user-defined policy that determines how the JMS file store writes data to disk. This policy also affects the JMS file store's performance, scalability, and reliability. The valid policy options are: Disabled - Transactions are complete as soon as their writes are cached in memory, instead of waiting for the writes to successfully reach the disk. This policy is the fastest, but the least reliable (that is, transactionally safe). It can be more than 100 times faster than the other policies, but power outages or operating system failures can cause lost and/or duplicate messages. Cache-Flush - Transactions cannot complete until all of their writes have been flushed down to disk. This policy is reliable and scales well as the number of simultaneous users increases. Direct-Write - File store writes are written directly to disk. This policy is supported on Solaris and Windows. If this policy is set on an unsupported platform, the file store automatically uses the Cache-Flush policy instead. With on-disk caching enabled, the Direct-Write policy can be 2-5 times faster than the Cache-Flush policy, except in highly scalable cases where it may be slightly slower. With on-disk caching disabled, the Direct-Write policy is faster than the Cache-Flush policy in one-to-many cases, but is much slower otherwise. The Direct-Write policy scales well with on-disk caching enabled, but does not scale with it disabled. (Solaris does not allowing enabling the on-disk cache for direct writes). | Default: weblogic.management.configuration.JMSConstants.SYNCWRITE_CACHEFLUSH Valid values: weblogic.management.configuration.JMSConstants.SYNCWRITE_DISABLED weblogic.management.configuration.JMSConstants.SYNCWRITE_CACHEFLUSH weblogic.management.configuration.JMSConstants.SYNCWRITE_DIRECTWRITE Configurable: yes Dynamic: yes Readable: yes Writable: yes
SynchronousWritePolicy (continued) | Warning! Although the use of the Direct-Write policy is transactionally reliable on Solaris systems, Windows systems may leave transaction data in the on-disk cache without writing it to disk immediately. This is not considered to be transactionally reliable, since a power failure can cause loss of on-disk cache data-- possibly resulting in lost and/or duplicate messages. For reliable writes using Direct-Write on Windows, either disable all write caching for the disk (enabled by default), or use a disk with a battery-backed cache. Some file systems, however, do not allow this value to be changed (for example, a RAID system that has a reliable cache). Note: If the JMS file store is used exclusively for paging non-persistent messages to disk, the Synchronous Write Policy is ignored. MBean: weblogic.management. configuration. JMSFileStoreMBean Attribute: SynchronousWritePolicy |
Directory | The directory where the file-based persistent store exists. This attribute is not dynamically configurable. MBean: weblogic.management. configuration. JMSFileStoreMBean Attribute: Directory | Configurable: yes Readable: yes Writable: yes